From: Schspa Shi <schspa@gmail.com>
To: lenb@kernel.org, james.morse@arm.com
Cc: rafael@kernel.org, xueshuai@linux.alibaba.com,
linux-acpi@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
Schspa Shi <schspa@gmail.com>
Subject: [PATCH] ARM: SDEI: allow sdei initialization even no APCI support
Date: Wed, 6 Sep 2023 21:09:00 +0800 [thread overview]
Message-ID: <20230906130900.12218-1-schspa@gmail.com> (raw)
The initialization of SDEI is forcibly bound by ACPI. This Patch allows to
continue to support the initialization of SDEI without starting ACPI.
Fixes: dc4e8c07e9e2 ("ACPI: APEI: explicit init of HEST and GHES in apci_init()")
Cc: Shuai Xue <xueshuai@linux.alibaba.com>
Signed-off-by: Schspa Shi <schspa@gmail.com>
---
drivers/acpi/bus.c | 1 +
drivers/firmware/arm_sdei.c | 4 ++++
2 files changed, 5 insertions(+)
diff --git a/drivers/acpi/bus.c b/drivers/acpi/bus.c
index 2fc2b43a4ed3..d78615080502 100644
--- a/drivers/acpi/bus.c
+++ b/drivers/acpi/bus.c
@@ -1368,6 +1368,7 @@ static int __init acpi_init(void)
int result;
if (acpi_disabled) {
+ acpi_ghes_init();
pr_info("Interpreter disabled.\n");
return -ENODEV;
}
diff --git a/drivers/firmware/arm_sdei.c b/drivers/firmware/arm_sdei.c
index f9040bd61081..5ab70107c8bf 100644
--- a/drivers/firmware/arm_sdei.c
+++ b/drivers/firmware/arm_sdei.c
@@ -1081,6 +1081,10 @@ void __init sdei_init(void)
}
}
+#ifndef CONFIG_ACPI
+subsys_initcall_sync(sdei_init);
+#endif
+
int sdei_event_handler(struct pt_regs *regs,
struct sdei_registered_event *arg)
{
--
2.39.2 (Apple Git-143)
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
reply other threads:[~2023-09-06 13:10 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20230906130900.12218-1-schspa@gmail.com \
--to=schspa@gmail.com \
--cc=james.morse@arm.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=rafael@kernel.org \
--cc=xueshuai@linux.alibaba.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).