mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: YijieYang <yijie.yang@oss.qualcomm.com>
To: andersson@kernel.org, konradybcio@kernel.org, robh@kernel.org,
	krzk+dt@kernel.org, conor+dt@kernel.org
Cc: linux-arm-msm@vger.kernel.org, linux-kernel@vger.kernel.org,
	devicetree@vger.kernel.org, yijie.yang@oss.qualcomm.com,
	krzysztof.kozlowski@oss.qualcomm.com
Subject: [PATCH v2 2/4] firmware: qcom: scm: Allow QSEECOM on PURWA-IOT-EVK
Date: Fri,  9 Jan 2026 15:59:52 +0800	[thread overview]
Message-ID: <20260109080000.606603-2-yijie.yang@oss.qualcomm.com> (raw)
In-Reply-To: <20260109-purwa-v2-0-f39ee10684cb@oss.qualcomm.com>

From: Yijie Yang <yijie.yang@oss.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@oss.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 1ced6022c716..9a046b09275d 100644
--- a/drivers/firmware/qcom/qcom_scm.c
+++ b/drivers/firmware/qcom/qcom_scm.c
@@ -2022,6 +2022,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" },
 	{ .compatible = "qcom,sc8180x-primus" },
 	{ .compatible = "qcom,x1e001de-devkit" },
 	{ .compatible = "qcom,x1e80100-crd" },
-- 
2.34.1


  parent reply	other threads:[~2026-01-09  8:00 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-01-09  7:59 [PATCH v2 0/4] Initial patch set for PURWA-IOT-EVK YijieYang
2026-01-09  7:59 ` [PATCH v2 1/4] dt-bindings: arm: qcom: Document PURWA-IOT-EVK board YijieYang
2026-01-09  7:59 ` YijieYang [this message]
2026-01-09 12:48   ` [PATCH v2 2/4] firmware: qcom: scm: Allow QSEECOM on PURWA-IOT-EVK Dmitry Baryshkov
2026-01-09  7:59 ` [PATCH v2 3/4] arm64: dts: qcom: Add PURWA-IOT-SOM platform YijieYang
2026-01-09 12:10   ` Dmitry Baryshkov
2026-01-12  3:02     ` Yijie Yang
2026-01-09  7:59 ` [PATCH v2 4/4] arm64: dts: qcom: Add base PURWA-IOT-EVK board YijieYang
2026-01-09 11:29   ` Konrad Dybcio
2026-01-12  3:12     ` Yijie Yang
2026-01-12  5:00       ` Dmitry Baryshkov
2026-01-12  5:51         ` Yijie Yang
2026-01-12  6:01           ` Dmitry Baryshkov
2026-01-12 10:54             ` Konrad Dybcio
2026-01-13  1:45             ` Yijie Yang
2026-01-12  7:14           ` Krzysztof Kozlowski
2026-01-09  8:06 ` [PATCH v2 0/4] Initial patch set for PURWA-IOT-EVK Krzysztof Kozlowski
2026-01-09  8:26   ` Yijie Yang
2026-01-09  9:04     ` Krzysztof Kozlowski
2026-01-09  9:28     ` Konrad Dybcio
2026-01-12  3:13       ` Yijie Yang

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=20260109080000.606603-2-yijie.yang@oss.qualcomm.com \
    --to=yijie.yang@oss.qualcomm.com \
    --cc=andersson@kernel.org \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=konradybcio@kernel.org \
    --cc=krzk+dt@kernel.org \
    --cc=krzysztof.kozlowski@oss.qualcomm.com \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=robh@kernel.org \
    /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®