<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40"> <head> <meta http-equiv="Content-Type" content="text/html; charset=us-ascii"> <meta name="Generator" content="Microsoft Word 15 (filtered medium)"> <style></style> </head> <body lang="EN-IN" link="blue" vlink="purple" style="word-wrap:break-word"> <div class="WordSection1"> Sunny, Apologies for late response. (Not keeping well these days) <o:p></o:p> Ok, PSB my remarks.<o:p></o:p> <o:p> </o:p> #1. True, if an entity is independently getting build must be prefixed with Pkg. In my previous discussion with Leif (<a href="https://edk2.groups.io/g/devel/message/70090">https://edk2.groups.io/g/devel/message/70090</a>) Leif requested a reason of this kind of setup. <o:p></o:p> So basically Here the ConfigurationManager is postfixed with “Pkg” because it has its own .dec and the reason being having this .dec is like CM exposes few headers which are OEM/platform specific (generic in nature consumed by platforms, not by CM itself). In case when platform try to expose its own OEM specific generators these headers cannot come from DynamicTablePkg(edk2) and even platforms are nearly clueless about these headers. So kept these headers as part of CM and exposed them using CM’s .dec in platforms inf files as and when needed. Not sure if this type of setup is acceptable, but seems that Lief was OK, plz check with leif and let me know if at all any correction needed.<o:p></o:p> I will check and plan modifications accordingly.<o:p></o:p> <o:p> </o:p> #2. Good to hear that.<o:p></o:p> #3. Got to hear that.<o:p></o:p> <o:p> </o:p> #4. Sunny renaming to directory structure and changes as such are inevitable. In my opinion we must choose what represents our software best. For instance plz check these 2 repo instance, they are already out of sync from LSDK.<o:p></o:p> LSDK specific à <a href="https://github.com/ossdev07/edk2-platforms/tree/UEFI_ACPI_EAR1-PS-Devel/Silicon/NXP/LX2160A/Library"> https://github.com/ossdev07/edk2-platforms/tree/UEFI_ACPI_EAR1-PS-Devel/Silicon/NXP/LX2160A/Library</a><o:p></o:p> Tianocore à <a href="https://github.com/tianocore/edk2-platforms/tree/master/Silicon/NXP/LX2160A/Library"> https://github.com/tianocore/edk2-platforms/tree/master/Silicon/NXP/LX2160A/Library</a><o:p></o:p> <o:p> </o:p> Now, referring the “SocFixupLib” as you mentioned, I would suggest pushing changes as and when needed makes more sense.<o:p></o:p> No point of pushing something which is not needed or is not being used by someone currently.<o:p></o:p> However I’m ok if you conclude it to be pushed in advance but still there is nothing called as “SocFixupLib” in current tianocore repos.<o:p></o:p> <o:p> </o:p> Let me know if I can help further.<o:p></o:p> <o:p> </o:p> Regards,<o:p></o:p> Vikas Singh<o:p></o:p> <o:p> </o:p> <div> <div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0cm 0cm 0cm"> From: Sunny Wang <Sunny.Wang@arm.com> Sent: 04 August 2021 14:17 To: Vikas Singh <vikas.singh@puresoftware.com>; devel@edk2.groups.io; Meenakshi Aggarwal (meenakshi.aggarwal@nxp.com) <meenakshi.aggarwal@nxp.com>; leif@nuviainc.com Cc: Sami Mujawar <Sami.Mujawar@arm.com>; Samer El-Haj-Mahmoud <Samer.El-Haj-Mahmoud@arm.com>; V Sethi (v.sethi@nxp.com) <v.sethi@nxp.com>; Arokia Samy <arokia.samy@puresoftware.com>; Kuldip Dwivedi <kuldip.dwivedi@puresoftware.com>; Ard Biesheuvel <Ard.Biesheuvel@arm.com>; vikas.singh@nxp.com; White Weng <white.weng@nxp.com>; Ran Wang <ran.wang_1@nxp.com>; Joe Byrne <joseph.byrne@nxp.com>; Sunny Wang <Sunny.Wang@arm.com> Subject: RE: [PATCH V2 0/4] Enable Dynamic ACPI for LS1046AFRWY<o:p></o:p> </div> </div> <o:p> </o:p> Hi Vikas, <o:p></o:p> <o:p> </o:p> Sorry for the delay and thanks for clarifying. Added my further rcomments below: <o:p></o:p> <ol style="margin-top:0cm" start="1" type="1"> <li class="MsoListParagraph" style="color:#203864;margin-left:0cm;mso-list:l1 level1 lfo3"> For your previous discussion with Leif, do you mean this one <a href="https://edk2.groups.io/g/devel/message/70090">https://edk2.groups.io/g/devel/message/70090</a>? If my understanding of your previous discussion is correct, the reason why you needed to rename ConfigurationManager to ConfigurationManagerPkg is that you created ConfigurationManagerPkg.dec file. However, I don’t see a need to create ConfigurationManagerPkg.dec. At least, the current NXP LSDK can work without it. Did you have any plan to use ConfigurationManagerPkg.dec? Moreover, for putting common files for all platforms to consume, it doesn't have to be an XXXXPkg folder and doesn't need a .dec file. In your previous discussion with Leif (<a href="https://edk2.groups.io/g/devel/message/70090">https://edk2.groups.io/g/devel/message/70090</a>), It looks like Leif was also asking to remove ConfigurationManagerPkg.dec if the purpose of adding the .dec file is just for all platforms to include common header files in this folder. Actually, I thought we would only name the folder with the postfix string “Pkg” when the folder needs to be separately built. If my thought is correct, I think we don’t need to separately build ConfigurationManager. <o:p></o:p></li><li class="MsoListParagraph" style="color:#203864;margin-left:0cm;mso-list:l1 level1 lfo3"> After thinking this over, I think \Platform\NXP\LX2160aRdbPkg\Include\ is a better place for putting LX2160aRdbPkg’s Platform.h, so this change looks good to me.<o:p></o:p></li><div> <li class="MsoListParagraph" style="color:#203864;margin-left:0cm;mso-list:l1 level1 lfo3"> After thinking this over, I think \Platform\NXP\ LS1046aFrwyPkg\Include\ is a better place for putting LS1046aFrwyPkg’s Platform.h, so this change looks good to me.<o:p></o:p></li><li class="MsoListParagraph" style="color:#203864;margin-left:0cm;mso-list:l1 level1 lfo3"> Could you give me more information about why you don’t want to put extra effort at this moment? It looks worth doing this because we will need to add the whole Silicon\NXP\LS1046A\Library\SocFixupLib\ from NXP LSDK later and adding it now can avoid confusion caused by the mismatch between edk2 and NXP LSDK. Why don’t we add it now? <o:p></o:p></li></div> </ol> Best Regards,<o:p></o:p> Sunny Wang<o:p></o:p> <div> <div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0cm 0cm 0cm"> From: Vikas Singh <<a href="mailto:vikas.singh@puresoftware.com">vikas.singh@puresoftware.com</a>> Sent: Monday, July 26, 2021 9:04 PM To: Sunny Wang <<a href="mailto:Sunny.Wang@arm.com">Sunny.Wang@arm.com</a>>; <a href="mailto:devel@edk2.groups.io">devel@edk2.groups.io</a>; Meenakshi Aggarwal (<a href="mailto:meenakshi.aggarwal@nxp.com">meenakshi.aggarwal@nxp.com</a>) <<a href="mailto:meenakshi.aggarwal@nxp.com">meenakshi.aggarwal@nxp.com</a>>; <a href="mailto:leif@nuviainc.com">leif@nuviainc.com</a> Cc: Sami Mujawar <<a href="mailto:Sami.Mujawar@arm.com">Sami.Mujawar@arm.com</a>>; Samer El-Haj-Mahmoud <<a href="mailto:Samer.El-Haj-Mahmoud@arm.com">Samer.El-Haj-Mahmoud@arm.com</a>>; V Sethi (<a href="mailto:v.sethi@nxp.com">v.sethi@nxp.com</a>) <<a href="mailto:v.sethi@nxp.com">v.sethi@nxp.com</a>>; Arokia Samy <<a href="mailto:arokia.samy@puresoftware.com">arokia.samy@puresoftware.com</a>>; Kuldip Dwivedi <<a href="mailto:kuldip.dwivedi@puresoftware.com">kuldip.dwivedi@puresoftware.com</a>>; Ard Biesheuvel <<a href="mailto:Ard.Biesheuvel@arm.com">Ard.Biesheuvel@arm.com</a>>; <a href="mailto:vikas.singh@nxp.com">vikas.singh@nxp.com</a>; White Weng <<a href="mailto:white.weng@nxp.com">white.weng@nxp.com</a>>; Ran Wang <<a href="mailto:ran.wang_1@nxp.com">ran.wang_1@nxp.com</a>>; Joe Byrne <<a href="mailto:joseph.byrne@nxp.com">joseph.byrne@nxp.com</a>> Subject: Re: [PATCH V2 0/4] Enable Dynamic ACPI for LS1046AFRWY<o:p></o:p> </div> </div> <o:p> </o:p> <div> Sunny, thanks for your review and PSB my remarks.<o:p></o:p> </div> <div> <o:p> </o:p> </div> <div class="MsoNormal" align="center" style="text-align:center"> <hr size="2" width="98%" align="center"> </div> <div id="divRplyFwdMsg"> From: Sunny Wang <<a href="mailto:Sunny.Wang@arm.com">Sunny.Wang@arm.com</a>> Sent: Monday, July 12, 2021 4:03 PM To: Vikas Singh <<a href="mailto:vikas.singh@puresoftware.com">vikas.singh@puresoftware.com</a>>; <a href="mailto:devel@edk2.groups.io">devel@edk2.groups.io</a> <<a href="mailto:devel@edk2.groups.io">devel@edk2.groups.io</a>>; Meenakshi Aggarwal (<a href="mailto:meenakshi.aggarwal@nxp.com">meenakshi.aggarwal@nxp.com</a>) <<a href="mailto:meenakshi.aggarwal@nxp.com">meenakshi.aggarwal@nxp.com</a>>; <a href="mailto:leif@nuviainc.com">leif@nuviainc.com</a> <<a href="mailto:leif@nuviainc.com">leif@nuviainc.com</a>> Cc: Sami Mujawar <<a href="mailto:Sami.Mujawar@arm.com">Sami.Mujawar@arm.com</a>>; <a href="mailto:leif@nuviainc.com">leif@nuviainc.com</a> <<a href="mailto:leif@nuviainc.com">leif@nuviainc.com</a>>; Samer El-Haj-Mahmoud <<a href="mailto:Samer.El-Haj-Mahmoud@arm.com">Samer.El-Haj-Mahmoud@arm.com</a>>; V Sethi (<a href="mailto:v.sethi@nxp.com">v.sethi@nxp.com</a>) <<a href="mailto:v.sethi@nxp.com">v.sethi@nxp.com</a>>; Arokia Samy <<a href="mailto:arokia.samy@puresoftware.com">arokia.samy@puresoftware.com</a>>; Kuldip Dwivedi <<a href="mailto:kuldip.dwivedi@puresoftware.com">kuldip.dwivedi@puresoftware.com</a>>; Ard Biesheuvel <<a href="mailto:Ard.Biesheuvel@arm.com">Ard.Biesheuvel@arm.com</a>>; <a href="mailto:vikas.singh@nxp.com">vikas.singh@nxp.com</a> <<a href="mailto:vikas.singh@nxp.com">vikas.singh@nxp.com</a>>; White Weng <<a href="mailto:white.weng@nxp.com">white.weng@nxp.com</a>>; Ran Wang <<a href="mailto:ran.wang_1@nxp.com">ran.wang_1@nxp.com</a>>; Sunny Wang <<a href="mailto:Sunny.Wang@arm.com">Sunny.Wang@arm.com</a>>; Joe Byrne <<a href="mailto:joseph.byrne@nxp.com">joseph.byrne@nxp.com</a>> Subject: RE: [PATCH V2 0/4] Enable Dynamic ACPI for LS1046AFRWY <o:p></o:p> <div> <o:p></o:p> </div> </div> <div> <div> Hi Vikas, Thanks for working on this. As our offline discussion with NXP, our goal is to make the Tiano edk2-platform and NXP LSDK opensource <a href="https://source.codeaurora.org/external/qoriq/qoriq-components/edk2-platforms"> https://source.codeaurora.org/external/qoriq/qoriq-components/edk2-platforms</a> in sync. Now the main problem is that some folders' names and locations have been changed to be different from NXP LSDK opensource in previous commits, which causes difficulty in doing synchronization between Tiano edk2-platform and NXP LSDK opensource and also causes LSDK user's confusion. I'm fine with keeping some changes that are needed for cleanup purposes or fixing build issues. However, I think we can still avoid some folder-renaming or folder-moving changes. For avoiding them, could you check my questions/comments below? 1. Why do we need to have ConfigurationManagerPkg.dec? Can we remove this? After removing it, we can rename the ConfigurationManagerPkg folder back to ConfigurationManager to be consistent with other platforms (JunoPkg).<o:p></o:p> </div> <div> [[Vikas]] ConfigurationManagerPkg folder should not be renamed back to ConfigurationManager because of the hierarchy and placement of this folder as a common generic for all the platform pkgs.<o:p></o:p> </div> <div> This is already been discussed with leif and moreover in case of JunoPkg the CM is private to JunoPkg not visible to other ARM platform pkgs. Here in our case CM serves all the NXP platforms.<o:p></o:p> </div> <div> 2. Can we move \Platform\NXP\LX2160aRdbPkg\Include\Platform.h to the same location as LSDK (\Platform\NXP\LX2160aRdbPkg\AcpiTables\)?<o:p></o:p> </div> <div> [[Vikas]] This involves extra effort/rework.<o:p></o:p> </div> <div> 3. Can we move \Platform\NXP\LS1046aFrwyPkg\Include\Platform.h t h to the same location as LSDK (\Platform\NXP\ LS1046aFrwyPkg\AcpiTables\)?<o:p></o:p> </div> <div> [[Vikas]] This involves extra effort/rework.<o:p></o:p> </div> <div> 4. Can we add \Silicon\NXP\LS1046A\Library\SocFixupLib\ for patch 2/4 (adding SocGetSvr() function)? Furthermore, can we just add the whole Silicon\NXP\LS1046A\Library\SocFixupLib\ from NXP LSDK? [[Vikas]] This involves extra effort/rework.<o:p></o:p> </div> <div> Add few more NXP guys. Hi Leif and Meenakshi, Can we just push the latest LSDK to the Tiano edk2-platform in one patch set? Then, If there is anything that needs to be cleaned up like the Coding style issue, we can create an issue in Bugzilla for it. What do you guys think? Best Regards, Sunny Wang -----Original Message----- From: Vikas Singh <<a href="mailto:vikas.singh@puresoftware.com">vikas.singh@puresoftware.com</a>> Sent: Friday, June 18, 2021 11:28 PM To: <a href="mailto:devel@edk2.groups.io">devel@edk2.groups.io</a> Cc: Sami Mujawar <<a href="mailto:Sami.Mujawar@arm.com">Sami.Mujawar@arm.com</a>>; <a href="mailto:leif@nuviainc.com">leif@nuviainc.com</a>; Meenakshi Aggarwal (<a href="mailto:meenakshi.aggarwal@nxp.com">meenakshi.aggarwal@nxp.com</a>) <<a href="mailto:meenakshi.aggarwal@nxp.com">meenakshi.aggarwal@nxp.com</a>>; Samer El-Haj-Mahmoud <<a href="mailto:Samer.El-Haj-Mahmoud@arm.com">Samer.El-Haj-Mahmoud@arm.com</a>>; V Sethi (<a href="mailto:v.sethi@nxp.com">v.sethi@nxp.com</a>) <<a href="mailto:v.sethi@nxp.com">v.sethi@nxp.com</a>>; arokia.samy <<a href="mailto:arokia.samy@puresoftware.com">arokia.samy@puresoftware.com</a>>; <a href="mailto:kuldip.dwivedi@puresoftware.com">kuldip.dwivedi@puresoftware.com</a>; Ard Biesheuvel <<a href="mailto:Ard.Biesheuvel@arm.com">Ard.Biesheuvel@arm.com</a>>; <a href="mailto:vikas.singh@nxp.com">vikas.singh@nxp.com</a>; Sunny Wang <<a href="mailto:Sunny.Wang@arm.com">Sunny.Wang@arm.com</a>> Subject: [PATCH V2 0/4] Enable Dynamic ACPI for LS1046AFRWY This patch series basically aims to extend the Dynamic ACPI framework towards NXP's LS1046AFRWY platform. In continuation to <a href="https://edk2.groups.io/g/devel/message/71709">https://edk2.groups.io/g/devel/message/71709</a> The change set in the series is in below order - (1)Introducing a new platform specific macro "PLAT_SOC_NAME" This macro will be consumed by Configuration Manager(CM). Platforms who extends CM services for themselves must notify their SoC details to CM using this macro only. Additionally also update the lx2160ardb platform header with PLAT_SOC_NAME, this will be consumed by CM. (2)Introduced a function to get SoC's System Version Register(SVR) This function will fetch SVR details for LS1046A SoC based platforms. In current patch series, this function will be used by LS1046aFrwyPkg. (3)Extending Configuration Manager (CM) and its services to leverage the Dynamic ACPI support for NXP's LS1046aFrwy platform. (4)Introduced an OEM specific firmware acpi table generator Also add Dsdt.asl as a place holder having only platform's clock related dsdt properties for now and will accommodate other IP specific dsdt tables(acpi properties) for LS1046AFRWY in future patch series. Vikas Singh (4): Platform/NXP: Make SoC version log in ConfigurationManager generic Silicon/NXP: Add support of SVR handling for LS1046A SoC NXP/LS1046aFrwyPkg: Enable ConfigurationManager on LS1046AFRWY Platform/NXP/LS1046aFrwyPkg: Add OEM specific DSDT generator Platform/NXP/ConfigurationManagerPkg/ConfigurationManagerDxe/ConfigurationManager.c | 11 +- Platform/NXP/LS1046aFrwyPkg/AcpiTablesInclude/Dsdt/Clk.asl | 60 ++++++++ Platform/NXP/LS1046aFrwyPkg/AcpiTablesInclude/Dsdt/Dsdt.asl | 15 ++ Platform/NXP/LS1046aFrwyPkg/AcpiTablesInclude/PlatformAcpiDsdtLib.inf | 39 +++++ Platform/NXP/LS1046aFrwyPkg/AcpiTablesInclude/PlatformAcpiDsdtLib/RawDsdtGenerator.c | 138 +++++++++++++++++ Platform/NXP/LS1046aFrwyPkg/AcpiTablesInclude/PlatformAcpiLib.h | 23 +++ Platform/NXP/LS1046aFrwyPkg/Include/Platform.h | 156 ++++++++++++++++++++ Platform/NXP/LS1046aFrwyPkg/LS1046aFrwyPkg.dsc | 29 ++++ Platform/NXP/LS1046aFrwyPkg/LS1046aFrwyPkg.fdf | 13 ++ Platform/NXP/LX2160aRdbPkg/Include/Platform.h | 8 +- Silicon/NXP/LS1046A/LS1046A.dsc.inc | 11 ++ Silicon/NXP/LS1046A/Library/SocLib/SocLib.c | 16 ++ Silicon/NXP/LX2160A/LX2160A.dsc.inc | 3 +- 13 files changed, 508 insertions(+), 14 deletions(-) create mode 100644 Platform/NXP/LS1046aFrwyPkg/AcpiTablesInclude/Dsdt/Clk.asl create mode 100644 Platform/NXP/LS1046aFrwyPkg/AcpiTablesInclude/Dsdt/Dsdt.asl create mode 100644 Platform/NXP/LS1046aFrwyPkg/AcpiTablesInclude/PlatformAcpiDsdtLib.inf create mode 100644 Platform/NXP/LS1046aFrwyPkg/AcpiTablesInclude/PlatformAcpiDsdtLib/RawDsdtGenerator.c create mode 100644 Platform/NXP/LS1046aFrwyPkg/AcpiTablesInclude/PlatformAcpiLib.h create mode 100644 Platform/NXP/LS1046aFrwyPkg/Include/Platform.h -- 2.25.1 IMPORTANT NOTICE: The contents of this email and any attachments are confidential and may also be privileged. If you are not the intended recipient, please notify the sender immediately and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium. Thank you.<o:p></o:p> </div> </div> IMPORTANT NOTICE: The contents of this email and any attachments are confidential and may also be privileged. If you are not the intended recipient, please notify the sender immediately and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium. Thank you. <o:p></o:p> </div> </body> </html> <div width="1" style="color:white;clear:both">_._,_._,_</div> <hr> Groups.io Links: You receive all messages sent to this group. <a target="_blank" href="https://edk2.groups.io/g/devel/message/79266">View/Reply Online (#79266)</a> | | <a target="_blank" href="https://groups.io/mt/83630879/1813853">Mute This Topic</a> | <a href="https://edk2.groups.io/g/devel/post">New Topic</a> <a href="https://edk2.groups.io/g/devel/editsub/1813853">Your Subscription</a> | <a href="mailto:devel+owner@edk2.groups.io">Contact Group Owner</a> | <a href="https://edk2.groups.io/g/devel/unsub">Unsubscribe</a> [edk2-devel-archive@redhat.com] <div width="1" style="color:white;clear:both">_._,_._,_</div>