From: Harshal Dev <harshal.dev@oss.qualcomm.com>
To: Eric Biggers <ebiggers@kernel.org>
Cc: Bjorn Andersson <andersson@kernel.org>,
Konrad Dybcio <konradybcio@kernel.org>,
Abel Vesa <abelvesa@kernel.org>,
Kuldeep Singh <kuldeep.singh@oss.qualcomm.com>,
Neeraj Soni <neeraj.soni@oss.qualcomm.com>,
Manivannan Sadhasivam <manivannan.sadhasivam@oss.qualcomm.com>,
Sumit Garg <sumit.garg@oss.qualcomm.com>,
Selvam Sathappan Periakaruppan
<selvam.periakaruppan@oss.qualcomm.com>,
Basant Kumar <basantk@qti.qualcomm.com>,
linux-kernel@vger.kernel.org, linux-arm-msm@vger.kernel.org,
linux-crypto@vger.kernel.org
Subject: Re: [PATCH v2 2/6] firmware: qcom_scm: Transition to ICE TZ agnostic operations
Date: Mon, 16 Nov 2026 16:48:47 +0530 [thread overview]
Message-ID: <691c3ec9-b21a-4e66-8c4a-de14c8987705@oss.qualcomm.com> (raw)
In-Reply-To: <20261113213403.GA35210@quark>
Hi Eric,
On 14-11-2026 03:04 am, Eric Biggers wrote:
> On Wed, Nov 11, 2026 at 07:47:02PM +0530, Harshal Dev wrote:
>> Transition the ICE related SCM calls to the generic ICE TZ operations by
>> registering them with the ICE driver and wrapping them in exported APIs
>> with the same signature.
>>
>> This prepares the ICE driver for eventual migration to the TZ agnostic
>> secure programming interfaces once the TEE bus based back-end becomes
>> available.
>>
>> Signed-off-by: Harshal Dev <harshal.dev@oss.qualcomm.com>
>> ---
>> drivers/firmware/qcom/qcom_scm.c | 131 +++++++++++++++++++++++++++++++--------
>> 1 file changed, 106 insertions(+), 25 deletions(-)
>
> Wouldn't it make more sense to leave qcom_scm alone, and have qcom_ice
> decide whether it should call qcom_scm_ice_*() or the OP-TEE backend?
> That would avoid the circular dependency between qcom_scm and qcom_ice
> which this patch introduces, and eliminate the need for patches 2 and 6.
>
I agree actually. The QCOM_SCM and QCOM_PAS already have a circular dependency
because of the function pointer registration approach. I guess it is much
easier the way you suggested. I'll try this approach.
Corresponding to qcom_scm_is_available() and qcom_scm_ice_is_available() we
should have corresponding APIs from the OPTEE back-end; qcom_tee_is_available()
and qcom_tee_ice_is_available(). The qcom_ice_tz_ops_(un)register() can be dropped.
Ack.
Regards,
Harshal
> - Eric
next prev parent reply other threads:[~2026-11-16 11:18 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-11 14:17 [PATCH v2 0/6] Add support for a TEE agnostic Inline Crypto Engine service Harshal Dev
2026-11-11 14:17 ` [PATCH v2 1/6] soc: qcom: ice: Add TZ agnostic re-direction functions Harshal Dev
2026-11-11 14:17 ` [PATCH v2 2/6] firmware: qcom_scm: Transition to ICE TZ agnostic operations Harshal Dev
2026-11-13 21:34 ` Eric Biggers
2026-11-16 11:18 ` Harshal Dev [this message]
2026-11-11 14:17 ` [PATCH v2 3/6] firmware: qcom: Add a TEE bus based ICE back-end Harshal Dev
2026-11-11 14:17 ` [PATCH v2 4/6] tee: optee: Register TEE devices on the platform bus Harshal Dev
2026-11-11 14:57 ` Harshal Dev
2026-11-13 20:45 ` Harshal Dev
2026-11-13 21:56 ` Eric Biggers
2026-11-16 11:38 ` Harshal Dev
2026-11-11 14:17 ` [PATCH v2 5/6] soc: qcom: ice: Migrate to the TZ agnostic ICE APIs Harshal Dev
2026-11-11 14:17 ` [PATCH v2 6/6] firmware: qcom: scm: Drop exported ICE wrapper functions Harshal Dev
2026-11-11 14:21 ` [PATCH v2 0/6] Add support for a TEE agnostic Inline Crypto Engine service Harshal Dev
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=691c3ec9-b21a-4e66-8c4a-de14c8987705@oss.qualcomm.com \
--to=harshal.dev@oss.qualcomm.com \
--cc=abelvesa@kernel.org \
--cc=andersson@kernel.org \
--cc=basantk@qti.qualcomm.com \
--cc=ebiggers@kernel.org \
--cc=konradybcio@kernel.org \
--cc=kuldeep.singh@oss.qualcomm.com \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=manivannan.sadhasivam@oss.qualcomm.com \
--cc=neeraj.soni@oss.qualcomm.com \
--cc=selvam.periakaruppan@oss.qualcomm.com \
--cc=sumit.garg@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®