From: Sumit Garg <sumit.garg@kernel.org>
To: Bjorn Andersson <andersson@kernel.org>,
Konrad Dybcio <konradybcio@kernel.org>,
Vikash Garodia <vikash.garodia@oss.qualcomm.com>,
Dikshita Agarwal <dikshita.agarwal@oss.qualcomm.com>,
Abhinav Kumar <abhinav.kumar@linux.dev>,
Bryan O'Donoghue <bod@kernel.org>,
Mauro Carvalho Chehab <mchehab@kernel.org>
Cc: linux-arm-msm@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-media@vger.kernel.org,
Sumit Garg <sumit.garg@oss.qualcomm.com>,
Jorge Ramirez-Ortiz <jorge.ramirez@oss.qualcomm.com>,
Jorge Ramirez-Ortiz <jorge.ramirez.ortiz@gmail.com>
Subject: [PATCH 0/3] media: qcom: Skip SCM secure memory protection with OP-TEE PAS backend
Date: Fri, 11 Sep 2026 18:08:54 +0530 [thread overview]
Message-ID: <20260911-video-optee-pas-v1-v1-0-7bbddaaac5ba@kernel.org> (raw)
The Qualcomm peripheral authentication service (PAS) can be serviced by
either the SCM (TrustZone) backend or, on OP-TEE based platforms, by the
OP-TEE backend. qcom_scm_mem_protect_video_var() is only implemented by
the SCM backend; with OP-TEE the TEE itself owns secure memory
protection and does not service this call. Issuing it unconditionally on
an OP-TEE backend fails firmware bring-up for the venus and iris video
codecs.
To let consumers make this distinction, patch 1 exposes the name of the
active PAS backend via a new qcom_pas_get_backend() helper and adds
QCOM_PAS_BACKEND_SCM/QCOM_PAS_BACKEND_TEE identifiers for them to match
against.
Patches 2 and 3 use this helper in the iris and venus drivers to skip
the SCM-only qcom_scm_mem_protect_video_var() call when a non-SCM
backend (e.g. OP-TEE) is active, leaving the SCM path unchanged.
No functional change is intended for the SCM backend.
Signed-off-by: Sumit Garg <sumit.garg@oss.qualcomm.com>
---
Jorge Ramirez-Ortiz (2):
firmware: qcom: pas: Expose the active PAS backend name
media: iris: Skip SCM call for non-SCM PAS backend
Sumit Garg (1):
media: venus: Skip SCM call for non-SCM PAS backend
drivers/firmware/qcom/qcom_pas.c | 8 ++++++++
drivers/firmware/qcom/qcom_pas_tee.c | 2 +-
drivers/firmware/qcom/qcom_scm.c | 2 +-
drivers/media/platform/qcom/iris/iris_firmware.c | 11 +++++++++++
drivers/media/platform/qcom/venus/firmware.c | 10 ++++++++++
include/linux/firmware/qcom/qcom_pas.h | 5 +++++
6 files changed, 36 insertions(+), 2 deletions(-)
---
base-commit: 08df884136f1c1197bab2a27814404fd329d9aac
change-id: 20260911-video-optee-pas-v1-c69298e840ca
Best regards,
--
Sumit Garg <sumit.garg@kernel.org>
next reply other threads:[~2026-09-11 12:39 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-11 12:38 Sumit Garg [this message]
2026-09-11 12:38 ` [PATCH 1/3] firmware: qcom: pas: Expose the active PAS backend name Sumit Garg
2026-09-11 12:38 ` [PATCH 2/3] media: iris: Skip SCM call for non-SCM PAS backend Sumit Garg
2026-09-11 14:24 ` Konrad Dybcio
2026-09-14 6:14 ` Sumit Garg
2026-09-17 11:41 ` Vikash Garodia
2026-09-18 11:10 ` Sumit Garg
2026-09-11 12:38 ` [PATCH 3/3] media: venus: " Sumit Garg
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=20260911-video-optee-pas-v1-v1-0-7bbddaaac5ba@kernel.org \
--to=sumit.garg@kernel.org \
--cc=abhinav.kumar@linux.dev \
--cc=andersson@kernel.org \
--cc=bod@kernel.org \
--cc=dikshita.agarwal@oss.qualcomm.com \
--cc=jorge.ramirez.ortiz@gmail.com \
--cc=jorge.ramirez@oss.qualcomm.com \
--cc=konradybcio@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@kernel.org \
--cc=sumit.garg@oss.qualcomm.com \
--cc=vikash.garodia@oss.qualcomm.com \
/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®