From: Harshal Dev <harshal.dev@oss.qualcomm.com>
To: Amirreza Zarrabi <amirreza.zarrabi@oss.qualcomm.com>
Cc: Kuldeep Singh <kuldeep.singh@oss.qualcomm.com>,
Basant Kumar <basantk@qti.qualcomm.com>,
Apurupa Pattapu <apurupa@qti.qualcomm.com>,
Arun Kumar Neelakantam <aneelaka@qti.qualcomm.com>,
op-tee@lists.trustedfirmware.org, linux-kernel@vger.kernel.org,
linux-arm-msm@vger.kernel.org,
Jens Wiklander <jens.wiklander@oss.qualcomm.com>,
Sumit Garg <sumit.garg@kernel.org>,
Bjorn Andersson <andersson@kernel.org>,
Konrad Dybcio <konradybcio@kernel.org>,
Dmitry Baryshkov <dmitry.baryshkov@oss.qualcomm.com>,
Krzysztof Kozlowski <krzk@kernel.org>
Subject: Re: [PATCH v5 5/7] tee: qcomtee: Add support for registering QTEE services on TEE bus
Date: Mon, 2 Nov 2026 19:14:32 +0530 [thread overview]
Message-ID: <395a146a-5c60-486c-869b-d3706f5e85cc@oss.qualcomm.com> (raw)
In-Reply-To: <b27834b1-4ed3-4eb1-a8e3-a1239f20ad43@oss.qualcomm.com>
Hi Amir,
On 26-10-2026 09:21 am, Amirreza Zarrabi wrote:
> Hi Harshal,
>
> On 10/15/2026 10:39 PM, Harshal Dev wrote:
>> QTEE exposes certain secure services implemented either within the QTEE
>> kernel or via pre-loaded Trusted Applications (TAs). Such always-available
>> services can be readily accessed by TEE client drivers via QTEE's
>> object-IPC protocol if the service is registered as a device on the TEE
>> bus.
>>
>> One such service is the EFI-variables service, implemented by the
>> uefisecapp TA which enables kernel clients to access EFI variables at
>> runtime.
>>
>> Maintain a static list of such always-available secure services and add
>> support for the QCOMTEE driver to register these services as devices on
>> the TEE bus during probe.
>>
>> Signed-off-by: Harshal Dev <harshal.dev@oss.qualcomm.com>
>> ---
>> drivers/tee/qcomtee/call.c | 160 ++++++++++++++++++++++++++++++++++-
>> drivers/tee/qcomtee/core.c | 9 +-
>> drivers/tee/qcomtee/qcomtee.h | 10 +++
>> drivers/tee/qcomtee/qcomtee_msg.h | 1 +
>> drivers/tee/qcomtee/qcomtee_object.h | 3 +-
>> 5 files changed, 176 insertions(+), 7 deletions(-)
>>
[...]
>> diff --git a/drivers/tee/qcomtee/core.c b/drivers/tee/qcomtee/core.c
>> index 60fe3b5776e3..4a523a95bf0e 100644
>> --- a/drivers/tee/qcomtee/core.c
>> +++ b/drivers/tee/qcomtee/core.c
>> @@ -898,19 +898,20 @@ qcomtee_object_get_client_env(struct qcomtee_object_invoke_ctx *oic)
>>
>> struct qcomtee_object *
>> qcomtee_object_get_service(struct qcomtee_object_invoke_ctx *oic,
>> - struct qcomtee_object *client_env, u32 uid)
>> + struct qcomtee_object *client_env, u32 uid,
>> + int *result)
>> {
>> struct qcomtee_arg u[3] = { 0 };
>> - int ret, result;
>> + int ret;
>>
>
> Please initialize *result, otherwise for instance, on mem allocation failure,
> qcomtee_object_do_invoke returns with errno. The caller checks the return value + result
> and may print garbage.
>
Ack, will initialize here and omit in the caller.
Regards,
Harshal
> - Amir
next prev parent reply other threads:[~2026-11-02 13:44 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-15 11:39 [PATCH v5 0/7] Add TEE based client driver for UEFI Secure Application Harshal Dev
2026-10-15 11:39 ` [PATCH v5 1/7] tee: qcomtee: Track the object invocation context Harshal Dev
2026-10-16 12:53 ` Kuldeep Singh
2026-10-15 11:39 ` [PATCH v5 2/7] tee: Add kernel client object invoke helper Harshal Dev
2026-10-16 12:54 ` Kuldeep Singh
2026-10-26 3:09 ` Amirreza Zarrabi
2026-11-02 13:40 ` Harshal Dev
2026-10-15 11:39 ` [PATCH v5 3/7] tee: qcomtee: Allow object invokes from kernel clients Harshal Dev
2026-10-16 12:55 ` Kuldeep Singh
2026-10-26 3:15 ` Amirreza Zarrabi
2026-11-02 13:41 ` Harshal Dev
2026-10-15 11:39 ` [PATCH v5 4/7] tee: Export uuidv5 generation for TEE backends Harshal Dev
2026-10-16 12:55 ` Kuldeep Singh
2026-10-15 11:39 ` [PATCH v5 5/7] tee: qcomtee: Add support for registering QTEE services on TEE bus Harshal Dev
2026-10-16 12:56 ` Kuldeep Singh
2026-10-26 3:51 ` Amirreza Zarrabi
2026-11-02 13:44 ` Harshal Dev [this message]
2026-10-15 11:39 ` [PATCH v5 6/7] firmware: qcom: Add support for TEE based EFI-var client driver Harshal Dev
2026-10-26 4:44 ` Amirreza Zarrabi
2026-10-15 11:39 ` [PATCH v5 7/7] arm64: defconfig: Enable UefiSecApp TEE client driver for Qualcomm SoCs 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=395a146a-5c60-486c-869b-d3706f5e85cc@oss.qualcomm.com \
--to=harshal.dev@oss.qualcomm.com \
--cc=amirreza.zarrabi@oss.qualcomm.com \
--cc=andersson@kernel.org \
--cc=aneelaka@qti.qualcomm.com \
--cc=apurupa@qti.qualcomm.com \
--cc=basantk@qti.qualcomm.com \
--cc=dmitry.baryshkov@oss.qualcomm.com \
--cc=jens.wiklander@oss.qualcomm.com \
--cc=konradybcio@kernel.org \
--cc=krzk@kernel.org \
--cc=kuldeep.singh@oss.qualcomm.com \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=op-tee@lists.trustedfirmware.org \
--cc=sumit.garg@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®