From: "Sami Mujawar" <sami.mujawar@arm.com>
To: Jeff Brasen <jbrasen@nvidia.com>, devel@edk2.groups.io
Cc: quic_llindhol@quicinc.com, ardb+tianocore@kernel.org,
Alexei.Fedorov@arm.com, pierre.gondois@arm.com,
"nd@arm.com" <nd@arm.com>
Subject: Re: [PATCH] DynamicTablesPkg: SSDT _LPI revision is incorrect
Date: Wed, 14 Dec 2022 15:24:05 +0000 [thread overview]
Message-ID: <74339b0d-8faa-328f-663b-182c42145b7d@arm.com> (raw)
In-Reply-To: <a1cae5eb965e34986aa81339d130b5dd62671bca.1668535182.git.jbrasen@nvidia.com>
Hi Jeff,
Apologies for the delay and thank you for this fix.
This change looks good to me.
Reviewed-by: Sami Mujawar <sami.mujawar@arm.com>
Regards,
Sami Mujawar
On 15/11/2022 06:01 pm, Jeff Brasen wrote:
> _LPI Revision should be 0 per the ACPI 6.5 specification.
> "The revision number of the _LPI object. Current revision is 0."
>
> Signed-off-by: Jeff Brasen <jbrasen@nvidia.com>
> ---
> .../Arm/AcpiSsdtCpuTopologyLibArm/SsdtCpuTopologyGenerator.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/DynamicTablesPkg/Library/Acpi/Arm/AcpiSsdtCpuTopologyLibArm/SsdtCpuTopologyGenerator.c b/DynamicTablesPkg/Library/Acpi/Arm/AcpiSsdtCpuTopologyLibArm/SsdtCpuTopologyGenerator.c
> index d06c7615fb..91199c4af2 100644
> --- a/DynamicTablesPkg/Library/Acpi/Arm/AcpiSsdtCpuTopologyLibArm/SsdtCpuTopologyGenerator.c
> +++ b/DynamicTablesPkg/Library/Acpi/Arm/AcpiSsdtCpuTopologyLibArm/SsdtCpuTopologyGenerator.c
> @@ -482,7 +482,7 @@ GenerateLpiStates (
> }
>
> // We do not support the LevelId field for now, let it to 0.
> - Status = AmlCreateLpiNode (AslName, 1, 0, ScopeNode, &LpiNode);
> + Status = AmlCreateLpiNode (AslName, 0, 0, ScopeNode, &LpiNode);
> if (EFI_ERROR (Status)) {
> ASSERT (0);
> return Status;
next prev parent reply other threads:[~2022-12-14 15:24 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-15 18:01 [PATCH] DynamicTablesPkg: SSDT _LPI revision is incorrect Jeff Brasen
2022-11-18 8:12 ` PierreGondois
2022-12-14 15:24 ` Sami Mujawar [this message]
2022-12-14 15:55 ` [edk2-devel] " 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=74339b0d-8faa-328f-663b-182c42145b7d@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