linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
* [RFC]Development of the AEST(Arm Error Source Table) driver
@ 2021-11-05  7:38 ishii.shuuichir
  0 siblings, 0 replies; 2+ messages in thread
From: ishii.shuuichir @ 2021-11-05  7:38 UTC (permalink / raw)
  To: 'rafael@kernel.org', 'lenb@kernel.org',
	'linux-acpi@vger.kernel.org',
	'linux-kernel@vger.kernel.org',
	'guohanjun@huawei.com',
	'lorenzo.pieralisi@arm.com',
	'sudeep.holla@arm.com',
	'linux-arm-kernel@lists.infradead.org'
  Cc: ishii.shuuichir

# 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,

^ permalink raw reply	[flat|nested] 2+ messages in thread

* [RFC]Development of the AEST(Arm Error Source Table) driver
@ 2021-11-05  7:27 ishii.shuuichir
  0 siblings, 0 replies; 2+ messages in thread
From: ishii.shuuichir @ 2021-11-05  7:27 UTC (permalink / raw)
  To: 'rafael@kernel.org', 'lenb@kernel.org',
	'inux-acpi@vger.kernel.org',
	'linux-kernel@vger.kernel.org',
	'orenzo.pieralisi@arm.com',
	'guohanjun@huawei.com', 'sudeep.holla@arm.com',
	'inux-arm-kernel@lists.infradead.org'
  Cc: ishii.shuuichir

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,
Shuuichirou.

^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2021-11-05  7:39 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2021-11-05  7:38 [RFC]Development of the AEST(Arm Error Source Table) driver ishii.shuuichir
  -- strict thread matches above, loose matches on Subject: below --
2021-11-05  7:27 ishii.shuuichir

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).