mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Kuldeep Singh <kuldeep.singh@oss.qualcomm.com>
To: Dmitry Baryshkov <dmitry.baryshkov@oss.qualcomm.com>,
	Xilin Wu <sophon@radxa.com>
Cc: zeroknots <zeroknots@protonmail.com>,
	amirreza.zarrabi@oss.qualcomm.com, jarkko@kernel.org,
	jenswi@kernel.org, jgg@ziepe.ca, linux-arm-msm@vger.kernel.org,
	linux-integrity@vger.kernel.org, linux-kernel@vger.kernel.org,
	op-tee@lists.trustedfirmware.org, peterhuewe@gmx.de,
	sumit.garg@kernel.org
Subject: Re: [PATCH v2 0/3] Add TPM support via Qualcomm TEE TPM TA
Date: Mon, 5 Oct 2026 17:30:20 +0530	[thread overview]
Message-ID: <e1ae7f91-0787-434d-9553-3ced487fac6f@oss.qualcomm.com> (raw)
In-Reply-To: <b2xdth3hkuypnvxlrgssnj4toffbceohhnh7w2ju46fzinflfd@qaq6ai5plolq>

>>> Two questions:
>>>
>>>  - Is service 81 expected to appear on retail firmware through an
>>>    update, or is it specific to the CRD firmware?
>>
>> Yes, there's spinor update(bootfw2.mbn) needed which is in progress to
>> publish as QTEE side changes were already merged long back.
>> Roughly it takes ~1month(ideal scenario) to get firmware changes
>> available but somehow it's taking more this time.
>>
>> I think i should have captured this dependency info in my series cover
>> letter to avoid any confusion.
>>
>> With the changes, service uid 81 will be available and won't see qcomtee
>> driver issue log there.
> 
> You are responding to the user who uses a COTS commercial device. Are
> you suggesting that the user can somehow update the firmware on that
> device?

Ahh, for COTS devices as one cannot replace firmware so it's better to
use qseecom path in that case.
For latest ones, one can switch to qcomtee based approach.

If Xilin already has qseecom interface written then it's best to have it
for the COTS devices.

-- 
Regards
Kuldeep


  reply	other threads:[~2026-10-05 12:00 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-01  5:50 zeroknots
2026-10-05  6:57 ` Kuldeep Singh
2026-10-05  7:24   ` Dmitry Baryshkov
2026-10-05 12:00     ` Kuldeep Singh [this message]
  -- strict thread matches above, loose matches on Subject: below --
2026-09-07  9:28 Kuldeep Singh
2026-09-16  9:02 ` Kuldeep Singh
2026-09-18  1:53 ` Jarkko Sakkinen
2026-09-21  8:36   ` Kuldeep Singh
2026-09-25 14:46     ` Jarkko Sakkinen
2026-09-28  9:34       ` Kuldeep Singh

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=e1ae7f91-0787-434d-9553-3ced487fac6f@oss.qualcomm.com \
    --to=kuldeep.singh@oss.qualcomm.com \
    --cc=amirreza.zarrabi@oss.qualcomm.com \
    --cc=dmitry.baryshkov@oss.qualcomm.com \
    --cc=jarkko@kernel.org \
    --cc=jenswi@kernel.org \
    --cc=jgg@ziepe.ca \
    --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=sophon@radxa.com \
    --cc=sumit.garg@kernel.org \
    --cc=zeroknots@protonmail.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®