mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Haozhen Li <dezige131@foxmail.com>
To: Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>
Cc: Bjorn Andersson <andersson@kernel.org>,
	Konrad Dybcio <konradybcio@kernel.org>,
	Abel Vesa <abelvesa@kernel.org>,
	Dawid Wrobel <me@dawidwrobel.com>,
	linux-arm-msm@vger.kernel.org, linux-kernel@vger.kernel.org,
	Haozhen Li <dezige131@foxmail.com>
Subject: Re: [RFC PATCH 2/2] firmware: qcom: scm: Handle QSEECOM listener callbacks
Date: Mon,  2 Nov 2026 16:27:20 +0000	[thread overview]
Message-ID: <tencent_E2B164FCF1BB7BD1B37CF08EAF0F0F0F9D07@qq.com> (raw)
In-Reply-To: <361131a8-4d30-4e8f-92a3-697dd93e7e30@oss.qualcomm.com>

Hi Konrad,

Thanks for the review.

Following Dawid's response on the cover-letter thread, I am withdrawing
this RFC. Dawid maintains a tee: qseecom driver that consumes exactly
these interfaces (github.com/wrobelda/linux, branch qcom-qseecom-tee),
with a Goodix SPI fingerprint sensor driver on top, and intends to file
a proper RFC for the complete stack himself. That is exactly the
in-tree consumer you asked for, and a much cleaner architectural path
than my standalone SCM helpers.

The fixes and hardened checks discussed here will be offered as a PR
against Dawid's tree to support his upstream submission instead.

Best regards,
Haozhen Li


      reply	other threads:[~2026-11-02 16:27 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20261101160110.3622-1-dezige131@foxmail.com>
2026-11-01 16:01 ` [RFC PATCH 1/2] firmware: qcom: scm: Add QSEECOM app loading and shutdown Haozhen Li
2026-11-02 12:26   ` Konrad Dybcio
2026-11-02 16:27     ` Haozhen Li
2026-11-01 16:01 ` [RFC PATCH 2/2] firmware: qcom: scm: Handle QSEECOM listener callbacks Haozhen Li
2026-11-02 12:28   ` Konrad Dybcio
2026-11-02 16:27     ` Haozhen Li [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=tencent_E2B164FCF1BB7BD1B37CF08EAF0F0F0F9D07@qq.com \
    --to=dezige131@foxmail.com \
    --cc=abelvesa@kernel.org \
    --cc=andersson@kernel.org \
    --cc=konrad.dybcio@oss.qualcomm.com \
    --cc=konradybcio@kernel.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=me@dawidwrobel.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®