Linux kernel and device drivers for NXP i.MX platforms
 help / color / mirror / Atom feed
From: sashiko-bot@kernel.org
To: "Stefano Radaelli" <stefano.radaelli21@gmail.com>
Cc: conor+dt@kernel.org, robh@kernel.org, devicetree@vger.kernel.org,
	Frank.Li@kernel.org, imx@lists.linux.dev
Subject: Re: [PATCH v2 10/15] arm64: dts: imx8mn-var-som-symphony: Add TPM2 support
Date: Mon, 06 Jul 2026 10:47:54 +0000	[thread overview]
Message-ID: <20260706104755.2B40D1F000E9@smtp.kernel.org> (raw)
In-Reply-To: <7cd17d03fa70ee1f5fd5986fbb0e8a39ad7b4fbe.1783330236.git.stefano.r@variscite.com>

Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Medium] The device tree specifies `reset-gpios` for the TPM device, but the kernel lacks support to drive this GPIO, potentially leaving the TPM stuck in reset.
--

commit 5bd051d2688db25353ab678262b0998bf9810906
Author: Stefano Radaelli <stefano.r@variscite.com>

arm64: dts: imx8mn-var-som-symphony: Add TPM2 support

This commit adds support for the ST33K TPM2 device on the VAR-SOM Symphony
carrier board over I2C. It also adds the PCA6408 GPIO expander node used to
control the TPM reset signal.

> diff --git a/arch/arm64/boot/dts/freescale/imx8mn-var-som-symphony.dts b/arch/arm64/boot/dts/freescale/imx8mn-var-som-symphony.dts
> index 53130b521b5b7..7d016ed5e911a 100644
> --- a/arch/arm64/boot/dts/freescale/imx8mn-var-som-symphony.dts
> +++ b/arch/arm64/boot/dts/freescale/imx8mn-var-som-symphony.dts

[ ... ]

> @@ -160,6 +160,20 @@ typec1_dr_sw: endpoint {
>  };
>  
>  &i2c3 {
> +	pca6408: gpio@21 {
> +		compatible = "nxp,pcal6408";
> +		reg = <0x21>;
> +		gpio-controller;
> +		#gpio-cells = <2>;
> +	};
> +
> +	st33ktpm2xi2c: tpm@2e {
> +		compatible = "st,st33ktpm2xi2c", "tcg,tpm-tis-i2c";
> +		reg = <0x2e>;
> +		label = "tpm";
> +		reset-gpios = <&pca6408 4 GPIO_ACTIVE_LOW>;

[Severity: Medium]
Will the kernel actually use this reset-gpios property to release the TPM?

The commit message states the PCA6408 is used to control the reset signal
to release the TPM from reset. However, neither the tpm_tis_i2c driver nor
the TPM core appear to parse the reset-gpios property or request a reset GPIO.
There is also no gpio-hog configured in the pca6408 node to force the pin
state.

Does this setup rely entirely on the bootloader initializing the PCA6408
and leaving the GPIO driven to the correct state?

If the system goes through a suspend/resume sequence or if the PCA6408
defaults back to an input state, could the TPM become stuck in reset and
fail to probe?

> +	};

-- 
Sashiko AI review · https://sashiko.dev/#/patchset/cover.1783330236.git.stefano.r@variscite.com?part=10

  reply	other threads:[~2026-07-06 10:47 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-06  9:34 [PATCH v2 00/15] arm64: dts: freescale: imx8mn-var-som: Align SOM and Symphony DTSs Stefano Radaelli
2026-07-06  9:34 ` [PATCH v2 01/15] arm64: dts: freescale: imx8mn-var-som: Move UART4 description to Symphony Stefano Radaelli
2026-07-06 11:16   ` Peng Fan
2026-07-06  9:34 ` [PATCH v2 02/15] arm64: dts: freescale: imx8mn-var-som: move uSD support to carrier boards Stefano Radaelli
2026-07-06 11:18   ` Peng Fan
2026-07-06  9:34 ` [PATCH v2 03/15] arm64: dts: freescale: imx8mn-var-som: Align fsl,pins tables Stefano Radaelli
2026-07-06  9:34 ` [PATCH v2 04/15] arm64: dts: freescale: imx8mn-var-som: Update FEC support with MaxLinear PHY Stefano Radaelli
2026-07-06 11:21   ` Peng Fan
2026-07-06  9:34 ` [PATCH v2 05/15] arm64: dts: freescale: imx8mn-var-som: Add support for WM8904 audio codec Stefano Radaelli
2026-07-06 10:09   ` sashiko-bot
2026-07-06 15:00     ` Frank Li
2026-07-06  9:34 ` [PATCH v2 06/15] arm64: dts: freescale: imx8mn-var-som: Add MCP251xFD CAN controller Stefano Radaelli
2026-07-06 12:34   ` Peng Fan
2026-07-06  9:34 ` [PATCH v2 07/15] arm64: dts: freescale: imx8mn-var-som: Rework WiFi/BT and add legacy dts Stefano Radaelli
2026-07-06 10:26   ` sashiko-bot
2026-07-06  9:34 ` [PATCH v2 08/15] arm64: dts: freescale: imx8mn-var-som: drop duplicate USB OTG node Stefano Radaelli
2026-07-06 12:34   ` Peng Fan
2026-07-06  9:34 ` [PATCH v2 09/15] arm64: dts: freescale: imx8mn-var-som: enable FlexSPI interface Stefano Radaelli
2026-07-06 10:38   ` sashiko-bot
2026-07-06  9:34 ` [PATCH v2 10/15] arm64: dts: imx8mn-var-som-symphony: Add TPM2 support Stefano Radaelli
2026-07-06 10:47   ` sashiko-bot [this message]
2026-07-06  9:34 ` [PATCH v2 11/15] arm64: dts: imx8mn-var-som-symphony: Enable I2C4 Stefano Radaelli
2026-07-06 12:36   ` Peng Fan
2026-07-06  9:34 ` [PATCH v2 12/15] arm64: dts: imx8mn-var-som-symphony: add wakeup sources Stefano Radaelli
2026-07-06 12:37   ` Peng Fan
2026-07-06  9:34 ` [PATCH v2 13/15] arm64: dts: imx8mn-var-som-symphony: keep RGB_SEL low Stefano Radaelli
2026-07-06 12:37   ` Peng Fan
2026-07-06  9:34 ` [PATCH v2 14/15] arm64: dts: imx8mn-var-som-symphony: enable PWM1 Stefano Radaelli
2026-07-06 12:38   ` Peng Fan
2026-07-06  9:34 ` [PATCH v2 15/15] arm64: dts: imx8mn-var-som-symphony: Disable internal RTC Stefano Radaelli
2026-07-06 12:38   ` Peng Fan

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=20260706104755.2B40D1F000E9@smtp.kernel.org \
    --to=sashiko-bot@kernel.org \
    --cc=Frank.Li@kernel.org \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=imx@lists.linux.dev \
    --cc=robh@kernel.org \
    --cc=sashiko-reviews@lists.linux.dev \
    --cc=stefano.radaelli21@gmail.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