From: Jens Wiklander <jens.wiklander@oss.qualcomm.com>
To: Jarkko Sakkinen <jarkko@kernel.org>,
Kuldeep Singh <kuldeep.singh@oss.qualcomm.com>
Cc: Jens Wiklander <jenswi@kernel.org>,
Amirreza Zarrabi <amirreza.zarrabi@oss.qualcomm.com>,
Sumit Garg <sumit.garg@kernel.org>,
Peter Huewe <peterhuewe@gmx.de>, Jason Gunthorpe <jgg@ziepe.ca>,
linux-arm-msm@vger.kernel.org, op-tee@lists.trustedfirmware.org,
linux-kernel@vger.kernel.org, linux-integrity@vger.kernel.org
Subject: Re: [PATCH v4 0/3] Add TPM support via Qualcomm TEE TPM TA
Date: Tue, 3 Nov 2026 17:33:18 +0100 [thread overview]
Message-ID: <2f6f80eb-57a4-406d-a041-8602805c7647@oss.qualcomm.com> (raw)
In-Reply-To: <athuhfkfGPZp_YXT@kernel.org>
Hi,
On 21/10/2026 09.49, Jarkko Sakkinen wrote:
> On Wed, Oct 21, 2026 at 11:21:33AM +0530, Kuldeep Singh wrote:
>>> Applying this pulls tons of TEE patches:
>>>
>>> Applying: tee: qcomtee: Track the object invocation context
>>> Applying: tee: Add kernel client object invoke helper
>>> Applying: tee: qcomtee: Allow object invokes from kernel clients
>>> Applying: tee: Export uuidv5 generation for TEE backends
>>> Applying: tee: qcomtee: Add support for registering QTEE services on TEE bus
>>> Applying: firmware: qcom: Add support for TEE based EFI-var client driver
>>> Applying: arm64: defconfig: Enable UefiSecApp TEE client driver for Qualcomm SoCs
>>> Applying: tee: qcomtee: Register qcom.tz.tpm service for discovery
>>> Applying: tpm: Introduce Qualcomm TPM driver
>>> Applying: MAINTAINERS: Add Qualcomm TPM driver entry
>>
>> Yes, first 5 are tee patches prerequisite for tpm series as mentioned in
>> cover letter too and this series can only be merged once Jens can pick
>> dependent series[1] in linux-next.
>>
>> Since, v7.4 merge window going to start soon so i doubt Jens can pick
>> for v7.4.
>>
>> Jens, Any plan/timeline you are aiming to pick series[1]?
>> I see it's mostly reviewed with no other relevant feedback to be addressed.
I'm sorry for the delay, I lost control over my inbox for a while.
Looking at [1] it appears some more is needed before it's ready.
>
> Maybe it is better to pick also TPM patches through your tree when
> you choose to so that this will go in-sync.
Yes, that makes sense.
>
>>
>> [1]
>> https://lore.kernel.org/lkml/20261015-qcom_uefisecapp_migrate_qcomtee-v5-0-1460691b35d3@oss.qualcomm.com/
>>
>> --
>> Regards
>> Kuldeep
>
> Br, Jarkko
Cheers,
Jens
prev parent reply other threads:[~2026-11-03 16:33 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-19 9:21 Kuldeep Singh
2026-10-19 9:21 ` [PATCH v4 1/3] tee: qcomtee: Register qcom.tz.tpm service for discovery Kuldeep Singh
2026-10-21 21:16 ` Amirreza Zarrabi
2026-10-19 9:21 ` [PATCH v4 2/3] tpm: Introduce Qualcomm TPM driver Kuldeep Singh
2026-10-19 13:00 ` Jarkko Sakkinen
2026-10-21 21:14 ` Amirreza Zarrabi
2026-10-19 9:21 ` [PATCH v4 3/3] MAINTAINERS: Add Qualcomm TPM driver entry Kuldeep Singh
2026-10-19 13:21 ` [PATCH v4 0/3] Add TPM support via Qualcomm TEE TPM TA Jarkko Sakkinen
2026-10-21 5:51 ` Kuldeep Singh
2026-10-21 7:49 ` Jarkko Sakkinen
2026-11-03 16:33 ` Jens Wiklander [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=2f6f80eb-57a4-406d-a041-8602805c7647@oss.qualcomm.com \
--to=jens.wiklander@oss.qualcomm.com \
--cc=amirreza.zarrabi@oss.qualcomm.com \
--cc=jarkko@kernel.org \
--cc=jenswi@kernel.org \
--cc=jgg@ziepe.ca \
--cc=kuldeep.singh@oss.qualcomm.com \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-integrity@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=op-tee@lists.trustedfirmware.org \
--cc=peterhuewe@gmx.de \
--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®