Re: [PATCH v2 5/6] tee: qcomtee: Add support for registering QTEE services on TEE bus

[Harshal Dev]

Hi Dmitry,

On 22-07-2026 01:59 pm, Dmitry Baryshkov wrote:
> On Wed, Jul 22, 2026 at 12:29:16PM +0530, 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.
> 
> Is it always available on all platforms supporting QTEE?

The uefisecapp service is very old. I know that it has existed since the oldest
SM8x50 chipset. Every upstream supported target currently has support for it, since
they all have UEFI somewhere in the boot chain to load the uefisecapp TA from
the storage partition.

But as we expand this list, it's possible that certain services might not be available
on older QTEE versions, in that case the service will never be registered on the
TEE bus and so the TEE client driver will not probe.

Regards,
Harshal

> 
>>
>> Signed-off-by: Harshal Dev <harshal.dev@xxxxxxxxxxxxxxxx>
>> ---
>>  drivers/tee/qcomtee/call.c           | 160 ++++++++++++++++++++++++++++++++++-
>>  drivers/tee/qcomtee/core.c           |   9 +-
>>  drivers/tee/qcomtee/qcomtee.h        |  12 +++
>>  drivers/tee/qcomtee/qcomtee_msg.h    |   1 +
>>  drivers/tee/qcomtee/qcomtee_object.h |   3 +-
>>  5 files changed, 177 insertions(+), 8 deletions(-)
>>
>