Re: [PATCH 1/4] firmware: qcom: scm: Allow QSEECOM on PURWA-IOT-EVK
From: Krzysztof Kozlowski
Date: Mon Dec 22 2025 - 04:11:05 EST
On Mon, Dec 22, 2025 at 02:03:26PM +0800, YijieYang wrote:
> From: Yijie Yang <yijie.yang@xxxxxxxxxxxxxxxx>
>
> Add the Purwa-IoT-EVK board to the list to enable access to EFI variables.
>
> Guarantee that subsystems relying on SCM services can access secure-world
> features. This change improves reliability and prevents missing functionality
> or boot-time issues by making service availability explicit.
>
> Signed-off-by: Yijie Yang <yijie.yang@xxxxxxxxxxxxxxxx>
> ---
> drivers/firmware/qcom/qcom_scm.c | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/drivers/firmware/qcom/qcom_scm.c b/drivers/firmware/qcom/qcom_scm.c
> index 1a6f85e463e0..1fed7a81bd29 100644
> --- a/drivers/firmware/qcom/qcom_scm.c
> +++ b/drivers/firmware/qcom/qcom_scm.c
> @@ -2010,6 +2010,7 @@ static const struct of_device_id qcom_scm_qseecom_allowlist[] __maybe_unused = {
> { .compatible = "microsoft,romulus13", },
> { .compatible = "microsoft,romulus15", },
> { .compatible = "qcom,hamoa-iot-evk" },
> + { .compatible = "qcom,purwa-iot-evk" },
Why are you using ABI before documenting the ABI?
Best regards,
Krzysztof