From: "PierreGondois" <pierre.gondois@arm.com>
To: Sami Mujawar <sami.mujawar@arm.com>, devel@edk2.groups.io
Cc: Ard Biesheuvel <ardb+tianocore@kernel.org>, nd@arm.com
Subject: Re: [PATCH edk2-platforms v1 1/3] Platform/ARM: Juno: Generate ASL description of CPU topology
Date: Mon, 18 Jul 2022 15:30:43 +0200 [thread overview]
Message-ID: <38013f32-0646-6405-9dfd-6e3fb4508803@arm.com> (raw)
In-Reply-To: <3c56d998-8b61-a0e2-a32a-f8bcdd01efe8@arm.com>
Hi Sami,
On 7/18/22 15:25, Sami Mujawar wrote:
> Hi Pierre,
>
> Thank you for this patch.
>
> Please find my response inline marked [SAMI].
>
> Other than the comment below, these changes looks good to me.
>
> Reviewed-by: Sami Mujawar <sami.mujawar@arm.com>
>
> Regards,
>
> Sami Mujawar
>
> On 27/04/2022 03:59 pm, Pierre.Gondois@arm.com wrote:
>> From: Pierre Gondois <Pierre.Gondois@arm.com>
>>
>> The Dynamic Tables Framework has been updated to add support for
>> generating an ASL description of a CPU topology and its _LPI states.
>> This patch:
>> - Describes the _LPI states in the Configuration Manager of the Juno
>> - Add the generation of a new SSDT table describing the CPU topology
>> and its _LPI states
>> - Removes the CPU topology description of the DSDT table
>>
>> Signed-off-by: Pierre Gondois <Pierre.Gondois@arm.com>
>> ---
>> .../AslTables/Dsdt.asl | 198 ------------------
>> .../ConfigurationManager.c | 196 ++++++++++++++++-
>> .../ConfigurationManager.h | 20 +-
>> 3 files changed, 206 insertions(+), 208 deletions(-)
>>
[snip]
>>
>> @@ -549,6 +575,84 @@ EDKII_PLATFORM_REPOSITORY_INFO ArmJunoPlatformRepositoryInfo = {
>> {
>> { REFERENCE_TOKEN (CacheInfo[4]) }, // -> 'LITTLE' core's L1 I-cache
>> { REFERENCE_TOKEN (CacheInfo[5]) } // -> 'LITTLE' core's L1 D-cache
>> + },
>> +
>> + // Low Power Idle state information (LPI) for all cores/clusters
>> + {
>> + { // LpiInfo[0] -> Clusters CluPwrDn
>> + 2500, // MinResidency
>> + 1150, // WorstCaseWakeLatency
>> + 1, // Flags
>> + 1, // ArchFlags
>> + 100, // ResCntFreq
>> + 0, // EnableParentState
>> + 1, // IsInteger
>
> [SAMI] IsInteger field is of type BOOLEAN. Therefore, the value here
> should be TRUE. Similar changes are requires at other places in this file.
>
> If you agree, I will make the nessary changes locally before pushing the
> patch.
>
> [/SAMI]
>
Thanks for catching this. Yes if you can make this change it would be awesome,
Regards,
Pierre
next prev parent reply other threads:[~2022-07-18 13:31 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-27 14:59 [PATCH edk2-platforms v1 0/3] Enable PCI/CPU topology generation for Juno PierreGondois
2022-04-27 14:59 ` [PATCH edk2-platforms v1 1/3] Platform/ARM: Juno: Generate ASL description of CPU topology PierreGondois
2022-07-18 13:25 ` Sami Mujawar
2022-07-18 13:30 ` PierreGondois [this message]
2022-04-27 14:59 ` [PATCH edk2-platforms v1 2/3] Platform/ARM: Juno: Print debug values in right order PierreGondois
2022-07-18 13:26 ` Sami Mujawar
2022-04-27 14:59 ` [PATCH edk2-platforms v1 3/3] Platform/ARM: Juno: Generate ASL description of a PCIe bus PierreGondois
2022-07-18 14:02 ` Sami Mujawar
2022-04-29 13:35 ` [edk2-devel] [PATCH edk2-platforms v1 0/3] Enable PCI/CPU topology generation for Juno Ard Biesheuvel
2022-04-29 13:39 ` PierreGondois
2022-04-29 13:42 ` Ard Biesheuvel
2022-07-18 16:25 ` Sami Mujawar
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=38013f32-0646-6405-9dfd-6e3fb4508803@arm.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