The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Xing Loong <xing.xl.loong@gmail.com>
To: Jens Wiklander <jens.wiklander@oss.qualcomm.com>
Cc: Jens Wiklander <jenswi@kernel.org>,
	Krzysztof Kozlowski <krzk+dt@kernel.org>,
	Conor Dooley <conor+dt@kernel.org>, Rob Herring <robh@kernel.org>,
	Sumit Garg <sumit.garg@kernel.org>,
	op-tee@lists.trustedfirmware.org, devicetree@vger.kernel.org,
	linux-riscv@lists.infradead.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v4 3/3] tee: add MbedTEE driver
Date: Fri, 21 Aug 2026 23:58:57 +0800	[thread overview]
Message-ID: <aoh1wdtxXF5PkPPw@ubuntu24> (raw)
In-Reply-To: <CAGgiveU2TjkA1YnPxBy2e9qtCorSumuno04aEir-u74yKvXBsw@mail.gmail.com>


Hi Jens,

On 20/08/2026 10:10, Jens Wiklander wrote:
> I took a quick look at the mbedtee project, and it appears to be a
> one-person hobby project. Sounds like fun, but I wonder how meaningful
> it is to upstream a kernel driver if you're the only user.

Fair point. I wasn't fully aware that an active user base was a strict
requirement for upstreaming a new driver, but that completely makes
sense from a maintenance perspective.

I'll hold off on pushing this driver for now until mbedtee gains more
actual users. For what it's worth, the integration side is fully in
place with tested QEMU/FastModel support and a working Buildroot
overlay, so it's very easy for anyone interested to try it out.

Thanks for your time and the prompt review!

Cheers,
Xing

      reply	other threads:[~2026-08-21 15:59 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-19  8:35 [PATCH v4 0/3] tee: add MbedTEE driver Xing Loong
2026-08-19  8:35 ` [PATCH v4 1/3] dt-bindings: vendor-prefixes: add mbedtee Xing Loong
2026-08-19  8:35 ` [PATCH v4 2/3] dt-bindings: firmware: add mbedtee,tee binding Xing Loong
2026-08-19  8:35 ` [PATCH v4 3/3] tee: add MbedTEE driver Xing Loong
2026-08-20  8:10   ` Jens Wiklander
2026-08-21 15:58     ` Xing Loong [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=aoh1wdtxXF5PkPPw@ubuntu24 \
    --to=xing.xl.loong@gmail.com \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=jens.wiklander@oss.qualcomm.com \
    --cc=jenswi@kernel.org \
    --cc=krzk+dt@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-riscv@lists.infradead.org \
    --cc=op-tee@lists.trustedfirmware.org \
    --cc=robh@kernel.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