[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-Id: <20211203024311.49865-1-ilkka@os.amperecomputing.com>
Date: Thu, 2 Dec 2021 18:43:09 -0800
From: Ilkka Koskinen <ilkka@...amperecomputing.com>
To: lorenzo.pieralisi@....com, guohanjun@...wei.com,
sudeep.holla@....com
Cc: rafael@...nel.org, lenb@...nel.org, robert.moore@...el.com,
linux-acpi@...r.kernel.org, linux-arm-kernel@...ts.infradead.org,
linux-kernel@...r.kernel.org, devel@...ica.org,
patches@...erecomputing.com, scott@...amperecomputing.com,
darren@...amperecomputing.com
Subject: [PATCH 0/2] ACPI: Arm Generic Diagnostic Dump and Reset device
Arm Generic Diagnostic Dump and Reset device enables a maintainer to
request OS to perform a diagnostic dump and reset a system via SDEI
event or an interrupt. This patchset adds support for the SDEI path.
I do have a patch to enable the interrupt path as well but I'm holding
it back since AGDI table is missing interrupt configuration fields
(trigger type etc.).
The recently published specification is available at
https://developer.arm.com/documentation/den0093/latest
The patchset was tested on Ampere Altra/Mt. Jade.
The patchset applies on top of
git://git.kernel.org/pub/scm/linux/kernel/git/rafael/linux-pm master
git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-next/core
What's the process with new ACPI tables? Should I submit a patch to
ACPICA at first or is this fine?
Ilkka Koskinen (2):
ACPI: AGDI: Add AGDI tables to drivers/acpi
ACPI: AGDI: Add driver for Arm Generic Diagnostic Dump and Reset
device
drivers/acpi/arm64/Kconfig | 8 +++
drivers/acpi/arm64/Makefile | 1 +
drivers/acpi/arm64/agdi.c | 133 ++++++++++++++++++++++++++++++++++++
drivers/acpi/tables.c | 2 +-
include/acpi/actbl2.h | 20 ++++++
5 files changed, 163 insertions(+), 1 deletion(-)
create mode 100644 drivers/acpi/arm64/agdi.c
--
2.17.1
Powered by blists - more mailing lists