From: Hanjun Guo <guohanjun@huawei.com>
To: Robin Murphy <robin.murphy@arm.com>, Jose Marinho <jose.marinho@arm.com>
Cc: Catalin Marinas <catalin.marinas@arm.com>,
Jeremy Linton <Jeremy.Linton@arm.com>,
James Morse <James.Morse@arm.com>,
Rob Herring <Rob.Herring@arm.com>, Will Deacon <will@kernel.org>,
Jonathan Corbet <corbet@lwn.net>,
<linux-arm-kernel@lists.infradead.org>,
<linux-doc@vger.kernel.org>, <linux-acpi@vger.kernel.org>,
Samer El-Haj-Mahmoud <Samer.El-Haj-Mahmoud@arm.com>
Subject: Re: [PATCH 3/3] Documentation/arm64: Update ACPI tables from BBR
Date: Fri, 19 May 2023 15:10:06 +0800 [thread overview]
Message-ID: <dd0114f5-2e9c-40ea-8722-93fdf3f57b87@huawei.com> (raw)
In-Reply-To: <e9918d6e-ca5c-5a3a-6ff4-27acf7f73b30@arm.com>
On 2023/5/18 21:40, Robin Murphy wrote:
> On 2023-05-18 13:07, Hanjun Guo wrote:
>> Hi Jose,
>>
>> On 2023/5/18 18:52, Jose Marinho wrote:
>>> The BBR specification requires (or conditionally requires) a set of ACPI
>>> tables for a proper working system.
>>> This commit updates:
>>> - the list of ACPI tables to reflect the contents of
>>> BBR version 2.0 (see https://developer.arm.com/documentation/den0044/g).
>>> - the list of ACPI tables in acpi_object_usage. This last update ensures
>>> that both files remain coherent.
>>
>> Thanks for the update, some comments inline.
>>
>>>
>>> Signed-off-by: Jose Marinho <jose.marinho@arm.com>
>>> Reviewed-by: Samer El-Haj-Mahmoud <Samer.El-Haj-Mahmoud@arm.com>
>>> ---
>>> Documentation/arm64/acpi_object_usage.rst | 81 +++++++++++++++++++++--
>>> Documentation/arm64/arm-acpi.rst | 71 +++++++++++++++++---
>>> 2 files changed, 139 insertions(+), 13 deletions(-)
>>>
>>> diff --git a/Documentation/arm64/acpi_object_usage.rst
>>> b/Documentation/arm64/acpi_object_usage.rst
>>> index 484ef9676653..1da22200fdf8 100644
>>> --- a/Documentation/arm64/acpi_object_usage.rst
>>> +++ b/Documentation/arm64/acpi_object_usage.rst
>>> @@ -17,16 +17,37 @@ For ACPI on arm64, tables also fall into the
>>> following categories:
>>> - Recommended: BERT, EINJ, ERST, HEST, PCCT, SSDT
>>> - - Optional: BGRT, CPEP, CSRT, DBG2, DRTM, ECDT, FACS, FPDT,
>>> IBFT,
>>> - IORT, MCHI, MPST, MSCT, NFIT, PMTT, RASF, SBST, SLIT,
>>> SPMI, SRAT,
>>> - STAO, TCPA, TPM2, UEFI, XENV
>>> + - Optional: AGDI, BGRT, CEDT, CPEP, CSRT, DBG2, DRTM, ECDT,
>>> FACS, FPDT,
>>> + HMAT, IBFT, IORT, MCHI, MPAM, MPST, MSCT, NFIT, PMTT,
>>> PPTT, RASF, SBST,
>>> + SDEI, SLIT, SPMI, SRAT, STAO, TCPA, TPM2, UEFI, XENV
>>> - - Not supported: BOOT, DBGP, DMAR, ETDT, HPET, IVRS, LPIT,
>>> MSDM, OEMx,
>>> - PSDT, RSDT, SLIC, WAET, WDAT, WDRT, WPBT
>>> + - Not supported: AEST, APMT, BOOT, DBGP, DMAR, ETDT, HPET,
>>> IVRS, LPIT,
>>
>> AEST is ARM Error Source Table, and it can be used for ARM platforms, so
>> I thinsk AEST is not belong to "Not supportted", "Optional" instead.
>
> Can you point to the code in Linux which does anything with AEST,
> optionally or otherwise? ;)
>> and APMT is the same.
>>
>>> + MSDM, OEMx, PDTT, PSDT, RAS2, RSDT, SLIC, WAET, WDAT,
>>> WDRT, WPBT
>>
>> PDTT and RAS2 are now used for ARM too, please move it to Optional :)
>
> Ditto; as stated in arm-acpi.rst this is Linux documentation covering
> the interaction between Linux and ACPI. It is not some kind of generic
Hmm, let me see...
OK, I checked the arm-acpi.rst, it is saying:
"Detailed expectations for ACPI tables and object are listed in the file
Documentation/arm64/acpi_object_usage.rst."
So if I remember correctly, it is the guidance of ACPI tables and
methods usage on arm64, to align with the BBR.
> ACPI-on-Arm guidance whitepaper. If and when Linux actually supports
> these tables in the sense of meaningfully consuming them, that is when
> we can document such support.
If this is the case, we don't need categories of "Required",
"Recommmened" and etc.
Thanks
Hanjun
next prev parent reply other threads:[~2023-05-19 7:10 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-18 10:51 [PATCH 0/3] Update ACPI documentation for Arm systems Jose Marinho
2023-05-18 10:52 ` [PATCH 1/3] Documentation/arm64: Update ARM and arch reference Jose Marinho
2023-05-18 10:52 ` [PATCH 2/3] Documentation/arm64: Update references in arm-acpi Jose Marinho
2023-05-18 10:52 ` [PATCH 3/3] Documentation/arm64: Update ACPI tables from BBR Jose Marinho
2023-05-18 12:07 ` Hanjun Guo
2023-05-18 13:40 ` Robin Murphy
2023-05-19 7:10 ` Hanjun Guo [this message]
2023-05-19 10:50 ` Robin Murphy
2023-05-22 10:55 ` Jose Marinho
2023-05-25 11:43 ` Hanjun Guo
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-all 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=dd0114f5-2e9c-40ea-8722-93fdf3f57b87@huawei.com \
--to=guohanjun@huawei.com \
--cc=James.Morse@arm.com \
--cc=Jeremy.Linton@arm.com \
--cc=Rob.Herring@arm.com \
--cc=Samer.El-Haj-Mahmoud@arm.com \
--cc=catalin.marinas@arm.com \
--cc=corbet@lwn.net \
--cc=jose.marinho@arm.com \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-doc@vger.kernel.org \
--cc=robin.murphy@arm.com \
--cc=will@kernel.org \
/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