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 0/5] Add support for a TEE agnostic Inline Crypto Engine service
Date: Tue, 27 Oct 2026 12:03:55 +0530 [thread overview]
Message-ID: <236471c7-cf05-4019-a590-b803fc471484@oss.qualcomm.com> (raw)
In-Reply-To: <20261025171903.GA2212@quark>
On 25-10-2026 10:49 pm, Eric Biggers wrote:
> On Sun, Oct 25, 2026 at 10:16:49PM +0530, Harshal Dev wrote:
>> By moving the TEE call re-direction to a separate middleware we are ensuring
>> that we only touch the 9-10 lines in the driver which depend on the TEE firmware.
>> Merging this functionality in the ICE driver would substantially increases
>> the total file size.
>
> Again, it would be simpler to handle it directly in the existing
> qcom_ice module. Yes, there will then be more code in that module, but
> then the new single-user middleware module wouldn't be needed.
>
Sure Eric, I don't have any deep preferences here. I will move the middleware
to the ICE driver itself.
Ack.
Regards,
Harshal
> - Eric
prev parent reply other threads:[~2026-10-27 6:34 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-21 15:43 Harshal Dev
2026-10-21 15:43 ` [PATCH 1/5] firmware: qcom: Add a generic ICE service Harshal Dev
2026-10-22 7:45 ` Konrad Dybcio
2026-10-24 13:46 ` Harshal Dev
2026-10-26 14:11 ` Konrad Dybcio
2026-10-21 15:43 ` [PATCH 2/5] firmware: qcom_scm: Transition to the " Harshal Dev
2026-10-23 7:21 ` Abel Vesa
2026-10-21 15:43 ` [PATCH 3/5] firmware: qcom: Add an TEE bus based ICE back-end Harshal Dev
2026-10-22 7:47 ` Konrad Dybcio
2026-10-24 13:46 ` Harshal Dev
2026-10-22 7:51 ` Konrad Dybcio
2026-10-24 13:46 ` Harshal Dev
2026-10-25 16:21 ` Harshal Dev
2026-10-22 7:52 ` Konrad Dybcio
2026-10-24 13:47 ` Harshal Dev
2026-10-21 15:43 ` [PATCH 4/5] soc: qcom: ice: Migrate to the generic ICE service Harshal Dev
2026-10-23 7:15 ` Abel Vesa
2026-10-21 15:43 ` [PATCH 5/5] firmware: qcom: scm: Drop exported ICE wrapper functions Harshal Dev
2026-10-23 7:16 ` Abel Vesa
2026-10-24 18:56 ` [PATCH 0/5] Add support for a TEE agnostic Inline Crypto Engine service Eric Biggers
2026-10-25 16:46 ` Harshal Dev
2026-10-25 17:19 ` Eric Biggers
2026-10-27 6:33 ` Harshal Dev [this message]
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=236471c7-cf05-4019-a590-b803fc471484@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®