From: Amirreza Zarrabi <amirreza.zarrabi@oss.qualcomm.com>
To: Harshal Dev <harshal.dev@oss.qualcomm.com>,
Jens Wiklander <jens.wiklander@linaro.org>,
Sumit Garg <sumit.garg@kernel.org>,
Bjorn Andersson <andersson@kernel.org>,
Konrad Dybcio <konradybcio@kernel.org>
Cc: 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
Subject: Re: [PATCH 2/6] tee: Add kernel client object invoke helper
Date: Wed, 8 Jul 2026 16:29:40 +1000 [thread overview]
Message-ID: <651db8ad-ff57-4369-8401-f51bb7ea46f5@oss.qualcomm.com> (raw)
In-Reply-To: <20260707-qcom_uefisecapp_migrate_qcomtee-v1-2-f659cbd5d04c@oss.qualcomm.com>
Hi Harshal,
On 7/7/2026 4:11 PM, Harshal Dev wrote:
> From: Amirreza Zarrabi <amirreza.zarrabi@oss.qualcomm.com>
>
> Kernel clients can open a TEE context and invoke regular TA commands
> through tee_client_invoke_func(). However, there is currently no
> equivalent helper for invoking TEE objects.
>
> Add tee_client_object_invoke_func() as a kernel client API for issuing
> object invocation requests. The helper checks that the backend provides
> object_invoke_func() before setting the MSB of the object-id and forwarding
> the request. The MSB of the object-id informs the TEE backend that the
> object is invoked from a kernel context.
>
> This allows TEE backends that support privileged object-based calls from
> the kernel-space.
>
> Signed-off-by: Amirreza Zarrabi <amirreza.zarrabi@oss.qualcomm.com>
> Signed-off-by: Harshal Dev <harshal.dev@oss.qualcomm.com>
> ---
> drivers/tee/tee_core.c | 13 +++++++++++++
> include/linux/tee_drv.h | 13 +++++++++++++
> 2 files changed, 26 insertions(+)
>
> diff --git a/drivers/tee/tee_core.c b/drivers/tee/tee_core.c
> index 7f986d7fb47f..0783802fd010 100644
> --- a/drivers/tee/tee_core.c
> +++ b/drivers/tee/tee_core.c
> @@ -1413,6 +1413,19 @@ int tee_client_invoke_func(struct tee_context *ctx,
> }
> EXPORT_SYMBOL_GPL(tee_client_invoke_func);
>
> +int tee_client_object_invoke_func(struct tee_context *ctx,
> + struct tee_ioctl_object_invoke_arg *arg,
> + struct tee_param *param)
> +{
> + if (!ctx->teedev->desc->ops->object_invoke_func)
> + return -EINVAL;
> +
> + /* Indicate that this object is being invoked from a kernel context. */
> + arg->id = arg->id | BIT(63);
Setting this bit is a qcomtee backend requirement and should not be
exposed to the TEE subsystem.
Kernel users of qcomtee_object_invoke() should use the normal object ID
value. For example, access to the initial ROOT maybe represented as
TEE_OBJREF_NULL | BIT_ULL(63), but the upper bit must be managed by the
qcomtee backend for any return object, i.e. The backend should also set
BIT_ULL(63) automatically on each returned object ID.
Callers should treat the ID as opaque and must not manipulate the upper bit directly.
> + return ctx->teedev->desc->ops->object_invoke_func(ctx, arg, param);
> +}
> +EXPORT_SYMBOL_GPL(tee_client_object_invoke_func);
> +
> int tee_client_cancel_req(struct tee_context *ctx,
> struct tee_ioctl_cancel_arg *arg)
> {
> diff --git a/include/linux/tee_drv.h b/include/linux/tee_drv.h
> index e561a26f537a..ca99c6b747a8 100644
> --- a/include/linux/tee_drv.h
> +++ b/include/linux/tee_drv.h
> @@ -283,6 +283,19 @@ int tee_client_invoke_func(struct tee_context *ctx,
> struct tee_ioctl_invoke_arg *arg,
> struct tee_param *param);
>
> +/**
> + * tee_client_object_invoke_func() - Invoke a TEE object from kernel space
> + * @ctx: TEE Context
> + * @arg: Invoke arguments, see description of
> + * struct tee_ioctl_object_invoke_arg
> + * @param: Parameters for the object invocation
> + *
> + * Return: On success, returns 0; on failure, returns < 0.
> + */
> +int tee_client_object_invoke_func(struct tee_context *ctx,
> + struct tee_ioctl_object_invoke_arg *arg,
> + struct tee_param *param);
> +
> /**
> * tee_client_cancel_req() - Request cancellation of the previous open-session
> * or invoke-command operations in a Trusted Application
>
Regards,
Amir
next prev parent reply other threads:[~2026-07-08 6:29 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-07 6:11 [PATCH 0/6] Add TEE based client driver for UEFI Secure Application Harshal Dev
2026-07-07 6:11 ` [PATCH 1/6] tee: qcomtee: Track the object invocation context Harshal Dev
2026-07-08 6:01 ` Amirreza Zarrabi
2026-07-10 6:37 ` Harshal Dev
2026-07-14 23:47 ` Amirreza Zarrabi
2026-07-16 6:58 ` Harshal Dev
2026-07-17 8:26 ` Sumit Garg
2026-07-20 10:18 ` Harshal Dev
2026-07-07 6:11 ` [PATCH 2/6] tee: Add kernel client object invoke helper Harshal Dev
2026-07-08 6:29 ` Amirreza Zarrabi [this message]
2026-07-10 6:52 ` Harshal Dev
2026-07-07 6:11 ` [PATCH 3/6] tee: qcomtee: Allow object invokes from kernel clients Harshal Dev
2026-07-07 6:11 ` [PATCH 4/6] tee: Export uuidv5 generation for TEE clients Harshal Dev
2026-07-07 6:11 ` [PATCH 5/6] tee: qcomtee: Add support for registering QTEE services on TEE bus Harshal Dev
2026-07-07 6:11 ` [PATCH 6/6] firmware: qcom: Add support for TEE based EFI-var client driver 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=651db8ad-ff57-4369-8401-f51bb7ea46f5@oss.qualcomm.com \
--to=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=harshal.dev@oss.qualcomm.com \
--cc=jens.wiklander@linaro.org \
--cc=konradybcio@kernel.org \
--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