From: Gavin Shan <gshan@redhat.com>
To: Huang Yiwei <quic_hyiwei@quicinc.com>,
will@kernel.org, rafael@kernel.org, lenb@kernel.org,
james.morse@arm.com, tony.luck@intel.com, bp@alien8.de
Cc: xueshuai@linux.alibaba.com, quic_aiquny@quicinc.com,
quic_satyap@quicinc.com, linux-acpi@vger.kernel.org,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, kernel@quicinc.com,
kernel@oss.qualcomm.com
Subject: Re: [PATCH v2] firmware: SDEI: Allow sdei initialization without ACPI_APEI_GHES
Date: Thu, 8 May 2025 10:24:42 +1000 [thread overview]
Message-ID: <5b8ea515-788e-44b8-b7d3-a85329b584dc@redhat.com> (raw)
In-Reply-To: <20250507045757.2658795-1-quic_hyiwei@quicinc.com>
On 5/7/25 2:57 PM, Huang Yiwei wrote:
> SDEI usually initialize with the ACPI table, but on platforms where
> ACPI is not used, the SDEI feature can still be used to handle
> specific firmware calls or other customized purposes. Therefore, it
> is not necessary for ARM_SDE_INTERFACE to depend on ACPI_APEI_GHES.
>
> In commit dc4e8c07e9e2 ("ACPI: APEI: explicit init of HEST and GHES
> in acpi_init()"), to make APEI ready earlier, sdei_init was moved
> into acpi_ghes_init instead of being a standalone initcall, adding
> ACPI_APEI_GHES dependency to ARM_SDE_INTERFACE. This restricts the
> flexibility and usability of SDEI.
>
> This patch corrects the dependency in Kconfig and splits sdei_init()
> into two separate functions: sdei_init() and acpi_sdei_init().
> sdei_init() will be called by arch_initcall and will only initialize
> the platform driver, while acpi_sdei_init() will initialize the
> device from acpi_ghes_init() when ACPI is ready. This allows the
> initialization of SDEI without ACPI_APEI_GHES enabled.
>
> Fixes: dc4e8c07e9e2 ("ACPI: APEI: explicit init of HEST and GHES in apci_init()")
> Cc: Shuai Xue <xueshuai@linux.alibaba.com>
> Signed-off-by: Huang Yiwei <quic_hyiwei@quicinc.com>
> ---
> drivers/acpi/apei/Kconfig | 1 +
> drivers/acpi/apei/ghes.c | 2 +-
> drivers/firmware/Kconfig | 1 -
> drivers/firmware/arm_sdei.c | 11 ++++++++---
> include/linux/arm_sdei.h | 4 ++--
> 5 files changed, 12 insertions(+), 7 deletions(-)
>
Reviewed-by: Gavin Shan <gshan@redhat.com>
next prev parent reply other threads:[~2025-05-08 0:24 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-07 4:57 Huang Yiwei
2025-05-07 11:21 ` Rafael J. Wysocki
2025-05-08 0:24 ` Gavin Shan [this message]
2025-05-08 1:11 ` Shuai Xue
2025-05-08 13:02 ` Will Deacon
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=5b8ea515-788e-44b8-b7d3-a85329b584dc@redhat.com \
--to=gshan@redhat.com \
--cc=bp@alien8.de \
--cc=james.morse@arm.com \
--cc=kernel@oss.qualcomm.com \
--cc=kernel@quicinc.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=quic_aiquny@quicinc.com \
--cc=quic_hyiwei@quicinc.com \
--cc=quic_satyap@quicinc.com \
--cc=rafael@kernel.org \
--cc=tony.luck@intel.com \
--cc=will@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
all inboxes | Powered by JetHome®