public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "Jeff Brasen" <jbrasen@nvidia.com>
To: Pierre Gondois <pierre.gondois@arm.com>,
	"devel@edk2.groups.io" <devel@edk2.groups.io>
Cc: "Sami.Mujawar@arm.com" <Sami.Mujawar@arm.com>,
	"Alexei.Fedorov@arm.com" <Alexei.Fedorov@arm.com>
Subject: Re: [PATCH 2/4] DynamicTablesPkg: AcpiSsdtPcieLibArm: Allow use of segment number as UID
Date: Fri, 8 Jul 2022 15:24:23 +0000	[thread overview]
Message-ID: <DS7PR12MB5789D17D7F390E0035AE38CECB829@DS7PR12MB5789.namprd12.prod.outlook.com> (raw)
In-Reply-To: <a2f7e306-3daa-491a-f65f-1cfbe7969987@arm.com>

So to detail the use case we have an embedded device on a known controller (we know the segment number) by forcing the autogeneration to the segment number we could in another SSDT create the subdevice node right. With just \SB\PCI9\D0x as the scope right? If we had a callback I suppose we don't need that. I think we could handle that with the proposed change you had in [4/4] if we just chain the implementation of GeneratePciDeviceInfo to our second place we would implement this. I think we can drop this patch and do it that way. Will move additional thoughts to the other patch.

Thanks,
Jeff


> -----Original Message-----
> From: Pierre Gondois <pierre.gondois@arm.com>
> Sent: Monday, July 4, 2022 2:38 AM
> To: Jeff Brasen <jbrasen@nvidia.com>; devel@edk2.groups.io
> Cc: Sami.Mujawar@arm.com; Alexei.Fedorov@arm.com
> Subject: Re: [PATCH 2/4] DynamicTablesPkg: AcpiSsdtPcieLibArm: Allow use
> of segment number as UID
> 
> External email: Use caution opening links or attachments
> 
> 
> Hello Jeff,
> I understand that since the _UID value is generated, it is not possible for an
> external module to guess its value.
> However, the pcd (and the case you detailed) seem to be really specific.
> If you need an interface in the AmlLib to locate an AML node based on
> custom callback, we can help.
> Would this fit your need ?
> Also I don't understand how having a known _UID would ease locating the
> PCI device node.
> 
> Regards,
> Pierre
> 
> On 7/1/22 17:54, Jeff Brasen wrote:
> > I don't think there are any requirements that this should be mapped this
> way which is why I added this under a PCD to enable it. We have a use case
> where it would be helpful to know the ACPI path of the PCIe controllers
> externally and using the segment number for that would allow us to do this
> without having to have matching logic that calculates the PCIe UID from the
> CM object list again.
> >
> > Thanks,
> > Jeff
> >
> >
> >> -----Original Message-----
> >> From: Pierre Gondois <pierre.gondois@arm.com>
> >> Sent: Friday, July 1, 2022 6:42 AM
> >> To: Jeff Brasen <jbrasen@nvidia.com>; devel@edk2.groups.io
> >> Cc: Sami.Mujawar@arm.com; Alexei.Fedorov@arm.com
> >> Subject: Re: [PATCH 2/4] DynamicTablesPkg: AcpiSsdtPcieLibArm: Allow
> >> use of segment number as UID
> >>
> >> External email: Use caution opening links or attachments
> >>
> >>
> >> Hello Jeff,
> >>
> >>   From "PCI Firmware Specification Revision 3.3", s4.1.2.
> >> "MCFG Table Description", the "PCI Segment Group Number" field of the
> >> MCFG table must match the value returned by the _SEG object in the
> >> corresponding object.
> >>
> >> I didn't find any constraint about the _UID value. Would it be
> >> possible to know why this is required ?
> >>
> >> Regards,
> >> Pierre
> >>
> >> On 6/30/22 17:48, Jeff Brasen wrote:
> >>> Add support for selecting to use index or segment number as UID and
> >> name.
> >>> This allows the path of the nodes to be well known.
> >>>
> >>> Signed-off-by: Jeff Brasen <jbrasen@nvidia.com>
> >>> ---
> >>>    DynamicTablesPkg/DynamicTablesPkg.dec         |  3 +++
> >>>    .../AcpiSsdtPcieLibArm/SsdtPcieGenerator.c    | 19
> >> ++++++++++++++++++-
> >>>    .../Arm/AcpiSsdtPcieLibArm/SsdtPcieLibArm.inf |  3 +++
> >>>    3 files changed, 24 insertions(+), 1 deletion(-)
> >>>
> >>> diff --git a/DynamicTablesPkg/DynamicTablesPkg.dec
> >>> b/DynamicTablesPkg/DynamicTablesPkg.dec
> >>> index 9b74c5a671..a890a048be 100644
> >>> --- a/DynamicTablesPkg/DynamicTablesPkg.dec
> >>> +++ b/DynamicTablesPkg/DynamicTablesPkg.dec
> >>> @@ -57,5 +57,8 @@
> >>>      # Non BSA Compliant 16550 Serial HID
> >>>
> >>>
> >>
> gEdkiiDynamicTablesPkgTokenSpaceGuid.PcdNonBsaCompliant16550SerialHi
> >> d|
> >>> ""|VOID*|0x40000008
> >>>
> >>> +  # Use PCI segment numbers as UID
> >>> +
> >>> +
> >>
> gEdkiiDynamicTablesPkgTokenSpaceGuid.PcdPciUseSegmentAsUid|FALSE|B
> >> OO
> >>> + LEAN|0x40000009
> >>> +
> >>>    [Guids]
> >>>      gEdkiiDynamicTablesPkgTokenSpaceGuid = { 0xab226e66, 0x31d8,
> >>> 0x4613, { 0x87, 0x9d, 0xd2, 0xfa, 0xb6, 0x10, 0x26, 0x3c } } diff
> >>> --git
> >>>
> >>
> a/DynamicTablesPkg/Library/Acpi/Arm/AcpiSsdtPcieLibArm/SsdtPcieGenera
> >> t
> >>> or.c
> >>>
> >>
> b/DynamicTablesPkg/Library/Acpi/Arm/AcpiSsdtPcieLibArm/SsdtPcieGenera
> >> t
> >>> or.c
> >>> index f0d15f69a4..85782af380 100644
> >>> ---
> >>>
> >>
> a/DynamicTablesPkg/Library/Acpi/Arm/AcpiSsdtPcieLibArm/SsdtPcieGenera
> >> t
> >>> or.c
> >>> +++
> >> b/DynamicTablesPkg/Library/Acpi/Arm/AcpiSsdtPcieLibArm/SsdtPcieGen
> >>> +++ erator.c
> >>> @@ -996,6 +996,7 @@ BuildSsdtPciTableEx (
> >>>      UINTN                         Index;
> >>>      EFI_ACPI_DESCRIPTION_HEADER   **TableList;
> >>>      ACPI_PCI_GENERATOR            *Generator;
> >>> +  UINT32                        Uid;
> >>>
> >>>      ASSERT (This != NULL);
> >>>      ASSERT (AcpiTableInfo != NULL); @@ -1051,13 +1052,29 @@
> >>> BuildSsdtPciTableEx (
> >>>      *Table = TableList;
> >>>
> >>>      for (Index = 0; Index < PciCount; Index++) {
> >>> +    if (PcdGetBool (PcdPciUseSegmentAsUid)) {
> >>> +      Uid = PciInfo[Index].PciSegmentGroupNumber;
> >>> +      if (Uid > MAX_PCI_ROOT_COMPLEXES_SUPPORTED) {
> >>> +        DEBUG ((
> >>> +          DEBUG_ERROR,
> >>> +          "ERROR: SSDT-PCI: Pci root complexes segment number: %d."
> >>> +          " Greater than maximum number of Pci root complexes
> >>> + supported =
> >> %d.\n",
> >>> +          Uid,
> >>> +          MAX_PCI_ROOT_COMPLEXES_SUPPORTED
> >>> +          ));
> >>> +        return EFI_INVALID_PARAMETER;
> >>> +      }
> >>> +    } else {
> >>> +      Uid = Index;
> >>> +    }
> >>> +
> >>>        // Build a SSDT table describing the Pci devices.
> >>>        Status = BuildSsdtPciTable (
> >>>                   Generator,
> >>>                   CfgMgrProtocol,
> >>>                   AcpiTableInfo,
> >>>                   &PciInfo[Index],
> >>> -               Index,
> >>> +               Uid,
> >>>                   &TableList[Index]
> >>>                   );
> >>>        if (EFI_ERROR (Status)) {
> >>> diff --git
> >>>
> >>
> a/DynamicTablesPkg/Library/Acpi/Arm/AcpiSsdtPcieLibArm/SsdtPcieLibArm.
> >>> inf
> >>>
> >>
> b/DynamicTablesPkg/Library/Acpi/Arm/AcpiSsdtPcieLibArm/SsdtPcieLibArm.
> >>> inf
> >>> index 283b564801..431e32a777 100644
> >>> ---
> >>>
> >>
> a/DynamicTablesPkg/Library/Acpi/Arm/AcpiSsdtPcieLibArm/SsdtPcieLibArm.
> >>> inf
> >>> +++
> >> b/DynamicTablesPkg/Library/Acpi/Arm/AcpiSsdtPcieLibArm/SsdtPcieLib
> >>> +++ Arm.inf
> >>> @@ -30,3 +30,6 @@
> >>>      AcpiHelperLib
> >>>      AmlLib
> >>>      BaseLib
> >>> +
> >>> +[Pcd]
> >>> +  gEdkiiDynamicTablesPkgTokenSpaceGuid.PcdPciUseSegmentAsUid

  reply	other threads:[~2022-07-08 15:24 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-30 15:48 [PATCH 0/4] DynamicTablesPkg: Pcie generation updates Jeff Brasen
2022-06-30 15:48 ` [PATCH 1/4] DynamicTablesPkg: AcpiSsdtPcieLibArm: Correct translation value Jeff Brasen
2022-07-01 12:40   ` PierreGondois
2022-07-01 15:48     ` Jeff Brasen
2022-06-30 15:48 ` [PATCH 2/4] DynamicTablesPkg: AcpiSsdtPcieLibArm: Allow use of segment number as UID Jeff Brasen
2022-07-01 12:42   ` PierreGondois
2022-07-01 15:54     ` Jeff Brasen
2022-07-04  8:37       ` PierreGondois
2022-07-08 15:24         ` Jeff Brasen [this message]
2022-06-30 15:48 ` [PATCH 3/4] DynamicTablesPkg: AcpiSsdtPcieLibArm: Support UID > 0xF Jeff Brasen
2022-06-30 15:48 ` [PATCH 4/4] DynamicTablesPkg: AcpiSsdtPcieLibArm: Add support for override protocol Jeff Brasen
2022-07-01 12:39   ` PierreGondois
2022-07-01 15:52     ` Jeff Brasen
2022-07-04  8:47       ` PierreGondois
2022-07-08 15:36         ` Jeff Brasen
2022-07-11 15:01           ` PierreGondois
2022-07-11 15:32             ` Jeff Brasen
2022-07-11 17:14               ` PierreGondois
2022-07-11 17:56                 ` Jeff Brasen

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-list from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=DS7PR12MB5789D17D7F390E0035AE38CECB829@DS7PR12MB5789.namprd12.prod.outlook.com \
    --to=devel@edk2.groups.io \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox