[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <174670772284.646111.7927928404698891686.b4-ty@kernel.org>
Date: Thu, 8 May 2025 14:02:35 +0100
From: Will Deacon <will@...nel.org>
To: rafael@...nel.org,
lenb@...nel.org,
james.morse@....com,
tony.luck@...el.com,
bp@...en8.de,
Huang Yiwei <quic_hyiwei@...cinc.com>
Cc: catalin.marinas@....com,
kernel-team@...roid.com,
Will Deacon <will@...nel.org>,
xueshuai@...ux.alibaba.com,
quic_aiquny@...cinc.com,
quic_satyap@...cinc.com,
linux-acpi@...r.kernel.org,
linux-kernel@...r.kernel.org,
linux-arm-kernel@...ts.infradead.org,
kernel@...cinc.com,
kernel@....qualcomm.com
Subject: Re: [PATCH v2] firmware: SDEI: Allow sdei initialization without ACPI_APEI_GHES
On Wed, 07 May 2025 12:57:57 +0800, 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.
>
> [...]
Applied to arm64 (for-next/acpi), thanks!
[1/1] firmware: SDEI: Allow sdei initialization without ACPI_APEI_GHES
https://git.kernel.org/arm64/c/59529bbe642d
Cheers,
--
Will
https://fixes.arm64.dev
https://next.arm64.dev
https://will.arm64.dev
Powered by blists - more mailing lists