From: Kaipeng Zeng <kaipeng94@gmail.com>
To: devicetree@vger.kernel.org
Cc: linux-arm-msm@vger.kernel.org, conor+dt@kernel.org,
krzk+dt@kernel.org, robh@kernel.org, abelvesa@kernel.org,
konradybcio@kernel.org, andersson@kernel.org,
Kaipeng Zeng <kaipeng94@gmail.com>
Subject: [PATCH v6 3/3] firmware: qcom: scm: Allow QSEECOM on Acer Swift Go Pro AI
Date: Fri, 30 Oct 2026 14:41:49 +0800 [thread overview]
Message-ID: <20261030064149.14736-4-kaipeng94@gmail.com> (raw)
In-Reply-To: <20261030064149.14736-1-kaipeng94@gmail.com>
Add the Acer Swift Go Pro AI (SFA14-11) to the QSEECOM allowlist to
enable UEFI variable access through uefisecapp.
Signed-off-by: Kaipeng Zeng <kaipeng94@gmail.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 43e250faea75..4552da4284ef 100644
--- a/drivers/firmware/qcom/qcom_scm.c
+++ b/drivers/firmware/qcom/qcom_scm.c
@@ -2225,6 +2225,7 @@ EXPORT_SYMBOL_GPL(qcom_scm_qseecom_app_send);
+ any potential issues with this, only allow validated machines for now.
*/
static const struct of_device_id qcom_scm_qseecom_allowlist[] __maybe_unused = {
+ { .compatible = "acer,swift-go-sfa14-11" },
{ .compatible = "asus,vivobook-s15" },
{ .compatible = "asus,vivobook-s15-x1p4" },
{ .compatible = "asus,zenbook-a14-ux3407na" },
--
2.53.0
next prev parent reply other threads:[~2026-10-30 6:44 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-30 6:41 [PATCH v6 0/3] Add device tree for Acer Swift Go Pro AI (SFA14-11) Kaipeng Zeng
2026-10-30 6:41 ` [PATCH v6 1/3] dt-bindings: arm: qcom: Add " Kaipeng Zeng
2026-10-30 6:41 ` [PATCH v6 2/3] arm64: dts: qcom: Add support for " Kaipeng Zeng
2026-10-30 6:41 ` Kaipeng Zeng [this message]
2026-11-08 20:20 ` (subset) [PATCH v6 0/3] Add device tree " Bjorn Andersson
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=20261030064149.14736-4-kaipeng94@gmail.com \
--to=kaipeng94@gmail.com \
--cc=abelvesa@kernel.org \
--cc=andersson@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=konradybcio@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-msm@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