From: Andrew Davis <afd@ti.com>
To: Krzysztof Kozlowski <krzk@kernel.org>,
Atharv Dubey <a-dubey@ti.com>,
Krzysztof Kozlowski <krzysztof.kozlowski@oss.qualcomm.com>,
"Geert Uytterhoeven" <geert+renesas@glider.be>,
Bjorn Andersson <bjorn.andersson@oss.qualcomm.com>,
Arnd Bergmann <arnd@arndb.de>
Cc: "Heiko Stuebner" <heiko@sntech.de>,
"Eric Biggers" <ebiggers@kernel.org>,
"Luca Weiss" <luca.weiss@fairphone.com>,
"Nícolas F . R . A . Prado" <nfraprado@collabora.com>,
"Lad Prabhakar" <prabhakar.mahadev-lad.rj@bp.renesas.com>,
"Kuninori Morimoto" <kuninori.morimoto.gx@renesas.com>,
linux-kernel@vger.kernel.org, m-chawdhry@ti.com, vigneshr@ti.com,
u-kumar1@ti.com, nm@ti.com
Subject: Re: [PATCH v2] arm64: defconfig: tpm : Enable fTPM TEE support
Date: Fri, 13 Feb 2026 09:26:43 -0600 [thread overview]
Message-ID: <66aa0f19-9ece-4ea1-8f06-dd4436719678@ti.com> (raw)
In-Reply-To: <b25bc3cd-3c5b-497b-8367-984738160d42@kernel.org>
On 2/11/26 12:22 AM, Krzysztof Kozlowski wrote:
> On 11/02/2026 07:15, Atharv Dubey wrote:
>> Enable CONFIG_TCG_FTPM_TEE as a module for all
>> the platforms to support firmware-based TPM
>> through OP-TEE.
>
> What all platforms? Again, this is not your distro defconfig. Explain
> why do we want it in upstream.
>
"All" seems correct here, the fTPM TA is usable by any ARM64 platform
with OP-TEE support, which looks to be just about everyone[0].
Why do we want it upstream?: to support firmware-based TPM
through OP-TEE.
What more are you looking for, how do we prove some feature that was
deemed useful enough to include in the kernel is useful enough to enable?
> Please wrap commit message according to Linux coding style / submission
> process (neither too early nor over the limit):
> https://elixir.bootlin.com/linux/v6.4-rc1/source/Documentation/process/submitting-patches.rst#L597
>
>>
>> Bloat-o-meter Statistics :
>> add/remove: 0/0 grow/shrink: 0/0 up/down: 0/0 (0)
>> Function old new delta
>> Total: Before=32968311, After=32968311, chg +0.00%
>
> Really? You put here a proof that not enabling built-in has no built-in
> impact?
>
Does it hurt to add? You never know if there are follow-on effects due
to definitions when setting a module (yes that would probably be a bug
but it can happen). Rules like "add Bloat-o-meter results to defconfig
change patches" work much better when you don't add "except when it's
obvious to Krzysztof that there should be no size change"..
Andrew
[0] https://github.com/OP-TEE/optee_os/tree/master/core/arch/arm
> Best regards,
> Krzysztof
>
next prev parent reply other threads:[~2026-02-13 15:26 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-11 6:15 [PATCH v2] arm64: defconfig: tpm : Enable fTPM TEE support Atharv Dubey
2026-02-11 6:22 ` Krzysztof Kozlowski
2026-02-13 15:26 ` Andrew Davis [this message]
2026-02-13 15:49 ` Krzysztof Kozlowski
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=66aa0f19-9ece-4ea1-8f06-dd4436719678@ti.com \
--to=afd@ti.com \
--cc=a-dubey@ti.com \
--cc=arnd@arndb.de \
--cc=bjorn.andersson@oss.qualcomm.com \
--cc=ebiggers@kernel.org \
--cc=geert+renesas@glider.be \
--cc=heiko@sntech.de \
--cc=krzk@kernel.org \
--cc=krzysztof.kozlowski@oss.qualcomm.com \
--cc=kuninori.morimoto.gx@renesas.com \
--cc=linux-kernel@vger.kernel.org \
--cc=luca.weiss@fairphone.com \
--cc=m-chawdhry@ti.com \
--cc=nfraprado@collabora.com \
--cc=nm@ti.com \
--cc=prabhakar.mahadev-lad.rj@bp.renesas.com \
--cc=u-kumar1@ti.com \
--cc=vigneshr@ti.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