From: Lukas Wunner <lukas@wunner.de>
To: "Heiko Stübner" <heiko@sntech.de>
Cc: Arnd Bergmann <arnd@arndb.de>, Olof Johansson <olof@lixom.net>,
soc@kernel.org, devicetree@vger.kernel.org,
linux-integrity@vger.kernel.org, Yannic Moog <Y.Moog@phytec.de>,
Alexander Bauer <a.bauer@phytec.de>,
upstream@lists.phytec.de, Teresa Remmet <T.Remmet@phytec.de>,
Tim Harvey <tharvey@gateworks.com>,
Shawn Guo <shawnguo@kernel.org>,
Sascha Hauer <s.hauer@pengutronix.de>,
kernel@pengutronix.de, Fabio Estevam <festevam@gmail.com>,
linux-imx@nxp.com, Adam Ford <aford173@gmail.com>,
Heiko Thiery <heiko.thiery@gmail.com>,
Enric Balletbo i Serra <eballetbo@kernel.org>,
Matthias Brugger <matthias.bgg@gmail.com>,
AngeloGioacchino Del Regno
<angelogioacchino.delregno@collabora.com>,
Hsin-Yi Wang <hsinyi@chromium.org>,
Chen-Yu Tsai <wenst@chromium.org>,
Nicolas Prado <nfraprado@collabora.com>,
Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Conor Dooley <conor+dt@kernel.org>
Subject: Re: [PATCH] arm64: dts: Fix TPM schema violations
Date: Sun, 14 Jan 2024 11:33:03 +0100 [thread overview]
Message-ID: <20240114103303.GA3805@wunner.de> (raw)
In-Reply-To: <11865970.MucGe3eQFb@diego>
On Sat, Jan 13, 2024 at 08:13:35PM +0100, Heiko Stübner wrote:
> Am Samstag, 13. Januar 2024, 19:06:56 CET schrieb Lukas Wunner:
> > Since commit 26c9d152ebf3 ("dt-bindings: tpm: Consolidate TCG TIS
> > bindings"), several issues are reported by "make dtbs_check" for arm64
> > devicetrees:
> >
> > The compatible property needs to contain the chip's name in addition to
> > the generic "tcg,tpm_tis-spi" and the nodename needs to be "tpm@0"
> > rather than "cr50@0":
> >
> > tpm@1: compatible: ['tcg,tpm_tis-spi'] is too short
> > from schema $id: http://devicetree.org/schemas/tpm/tcg,tpm_tis-spi.yaml#
> >
> > cr50@0: $nodename:0: 'cr50@0' does not match '^tpm(@[0-9a-f]+)?$'
> > from schema $id: http://devicetree.org/schemas/tpm/google,cr50.yaml#
> >
> > Fix these schema violations.
[...]
> > arch/arm64/boot/dts/freescale/imx8mm-phygate-tauri-l.dts | 2 +-
> > arch/arm64/boot/dts/freescale/imx8mm-venice-gw72xx.dtsi | 2 +-
> > arch/arm64/boot/dts/freescale/imx8mm-venice-gw73xx.dtsi | 2 +-
> > arch/arm64/boot/dts/freescale/imx8mp-beacon-kit.dts | 2 +-
> > arch/arm64/boot/dts/freescale/imx8mp-venice-gw72xx.dtsi | 2 +-
> > arch/arm64/boot/dts/freescale/imx8mp-venice-gw73xx.dtsi | 2 +-
> > arch/arm64/boot/dts/freescale/imx8mp-venice-gw74xx.dts | 2 +-
> > arch/arm64/boot/dts/freescale/imx8mq-kontron-pitx-imx8m.dts | 2 +-
> > arch/arm64/boot/dts/mediatek/mt8183-kukui.dtsi | 2 +-
> > arch/arm64/boot/dts/mediatek/mt8192-asurada.dtsi | 2 +-
> > arch/arm64/boot/dts/rockchip/rk3399-gru-bob.dts | 2 +-
> > arch/arm64/boot/dts/rockchip/rk3399-gru-scarlet.dtsi | 2 +-
>
> you might want to split this per sub-architecture perhaps (freescale,
> mediatek, rockchip) as such dts changes normally go through the trees
> of the subarchitecture maintainers.
My concern was that other developers may see these new warnings
and start submitting piecemeal fixes. That would be a waste
of time since I already prepared fixes for everything weeks ago.
I was only waiting for the schema changes to hit mainline.
I was hoping that these might make it to Linus during the back half
of the merge window so that the warnings are gone by rc1 time
and nobody will ever see them.
Of course I can split them up if that's what Arnd & Olof prefer.
> For the rockchip-parts itself, I'm also fine with them going through
> somewhere else - gru devices are pretty much "finished" by now,
> so for the rockchip changes
> Acked-by: Heiko Stuebner <heiko@sntech.de>
Thanks for taking a look!
Lukas
next prev parent reply other threads:[~2024-01-14 10:41 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-13 18:06 [PATCH] arm64: dts: Fix TPM schema violations Lukas Wunner
2024-01-13 19:13 ` Heiko Stübner
2024-01-14 10:33 ` Lukas Wunner [this message]
2024-01-15 8:41 ` AngeloGioacchino Del Regno
2024-01-15 20:17 ` Arnd Bergmann
2024-01-16 10:24 ` Lukas Wunner
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=20240114103303.GA3805@wunner.de \
--to=lukas@wunner.de \
--cc=T.Remmet@phytec.de \
--cc=Y.Moog@phytec.de \
--cc=a.bauer@phytec.de \
--cc=aford173@gmail.com \
--cc=angelogioacchino.delregno@collabora.com \
--cc=arnd@arndb.de \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=eballetbo@kernel.org \
--cc=festevam@gmail.com \
--cc=heiko.thiery@gmail.com \
--cc=heiko@sntech.de \
--cc=hsinyi@chromium.org \
--cc=kernel@pengutronix.de \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-imx@nxp.com \
--cc=linux-integrity@vger.kernel.org \
--cc=matthias.bgg@gmail.com \
--cc=nfraprado@collabora.com \
--cc=olof@lixom.net \
--cc=robh+dt@kernel.org \
--cc=s.hauer@pengutronix.de \
--cc=shawnguo@kernel.org \
--cc=soc@kernel.org \
--cc=tharvey@gateworks.com \
--cc=upstream@lists.phytec.de \
--cc=wenst@chromium.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;
as well as URLs for NNTP newsgroup(s).