From: "ishii.shuuichir@fujitsu.com" <ishii.shuuichir@fujitsu.com>
To: "'rafael@kernel.org'" <rafael@kernel.org>,
"'lenb@kernel.org'" <lenb@kernel.org>,
"'linux-acpi@vger.kernel.org'" <linux-acpi@vger.kernel.org>,
"'linux-kernel@vger.kernel.org'" <linux-kernel@vger.kernel.org>,
"'guohanjun@huawei.com'" <guohanjun@huawei.com>,
"'lorenzo.pieralisi@arm.com'" <lorenzo.pieralisi@arm.com>,
"'sudeep.holla@arm.com'" <sudeep.holla@arm.com>,
"'linux-arm-kernel@lists.infradead.org'"
<linux-arm-kernel@lists.infradead.org>
Cc: "ishii.shuuichir@fujitsu.com" <ishii.shuuichir@fujitsu.com>
Subject: [RFC]Development of the AEST(Arm Error Source Table) driver
Date: Fri, 5 Nov 2021 07:38:59 +0000 [thread overview]
Message-ID: <TYCPR01MB6160251FF2C341948BD0FA37E98E9@TYCPR01MB6160.jpnprd01.prod.outlook.com> (raw)
# Sorry, email address was wrong, will resend it.
Hello,
to all concerned with ACPI (arm64) processing implementation,
We are considering to develop an AEST driver.
Currently, the following has been posted as an RFC patch [1] for the AEST driver.
[1] https://lore.kernel.org/linux-acpi/1562086280-5351-1-git-send-email-baicar@os.amperecomputing.com/
We sent an email to the developer of this patch to check the current status of the AEST driver.
Unfortunately, there was no response, so we would like to make the necessary feature updates.
We have two questions.
Question 1: About the update features.
Since [1] is implemented based on the ACPI for the Arm8 RAS Extensions 1.0 specification, we are thinking of updating it based on the latest specification.
Any comments would be appreciated.
(a) ACPI for the Arm8 RAS Extensions v.1.1[2] support
(b) Register addition and its dumping process to comply with ARMv8.4 RAS Extensions
(c) Addition of processing for each missing error type.
[2] https://developer.arm.com/documentation/den0085/latest
Question 2: About the directory to be placed AEST will be ARM specification.Is there any problem that the directory to store the main source (aest.c) is under drivers/acpi/arm64/?
If you have any comments, please let me know.
Best regards,
next reply other threads:[~2021-11-05 7:39 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-05 7:38 ishii.shuuichir [this message]
-- strict thread matches above, loose matches on Subject: below --
2021-11-05 7:27 [RFC]Development of the AEST(Arm Error Source Table) driver ishii.shuuichir
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=TYCPR01MB6160251FF2C341948BD0FA37E98E9@TYCPR01MB6160.jpnprd01.prod.outlook.com \
--to=ishii.shuuichir@fujitsu.com \
--cc=guohanjun@huawei.com \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lorenzo.pieralisi@arm.com \
--cc=rafael@kernel.org \
--cc=sudeep.holla@arm.com \
/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;
as well as URLs for NNTP newsgroup(s).