linux-kernel - Re: [PATCH 1/4] firmware: qcom: scm: Allow QSEECOM on PURWA-IOT-EVK

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <fb576893-aa2a-4e7c-9c3a-1bda7e849412@oss.qualcomm.com>
Date: Tue, 23 Dec 2025 09:48:55 +0800
From: Yijie Yang <yijie.yang@....qualcomm.com>
To: Krzysztof Kozlowski <krzk@...nel.org>
Cc: andersson@...nel.org, konradybcio@...nel.org, robh@...nel.org,
        krzk+dt@...nel.org, conor+dt@...nel.org, linux-arm-msm@...r.kernel.org,
        linux-kernel@...r.kernel.org, devicetree@...r.kernel.org
Subject: Re: [PATCH 1/4] firmware: qcom: scm: Allow QSEECOM on PURWA-IOT-EVK



On 12/22/2025 5:11 PM, Krzysztof Kozlowski wrote:
> On Mon, Dec 22, 2025 at 02:03:26PM +0800, YijieYang wrote:
>> From: Yijie Yang <yijie.yang@....qualcomm.com>
>>
>> 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@....qualcomm.com>
>> ---
>>   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?

I’ll reorder the patch sequence.

> 
> Best regards,
> Krzysztof
> 

-- 
Best Regards,
Yijie