devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Jarkko Sakkinen" <jarkko@kernel.org>
To: "Lukas Wunner" <lukas@wunner.de>, "Rob Herring" <robh@kernel.org>
Cc: <devicetree@vger.kernel.org>, <linux-integrity@vger.kernel.org>,
	"Peter Huewe" <peterhuewe@gmx.de>,
	"Jason Gunthorpe" <jgg@ziepe.ca>
Subject: Re: [PATCH v2 1/4] dt-bindings: tpm: Add compatible string atmel,attpm20p
Date: Sat, 13 Jan 2024 23:17:39 +0200	[thread overview]
Message-ID: <CYDW3GS1VGP4.2PUT4XW283L99@kernel.org> (raw)
In-Reply-To: <8886271d52025065eddf5915bb7778ab14362255.1705140898.git.lukas@wunner.de>

On Sat Jan 13, 2024 at 7:10 PM EET, Lukas Wunner wrote:
> Commit 4f2a348aa365 ("arm64: dts: imx8mm-venice-gw73xx: add TPM device")
> added a devicetree node for the Trusted Platform Module on certain
> Gateworks boards.
>
> The commit only used the generic "tcg,tpm_tis-spi" compatible string,
> but public documentation shows that the chip is an ATTPM20P from Atmel
> (nowadays Microchip):
> https://trac.gateworks.com/wiki/tpm
>
> Add the chip to the supported compatible strings of the TPM TIS SPI
> schema.
>
> For reference, a datasheet is available at:
> https://ww1.microchip.com/downloads/en/DeviceDoc/ATTPM20P-Trusted-Platform-Module-TPM-2.0-SPI-Interface-Summary-Data-Sheet-DS40002082A.pdf
>
> Signed-off-by: Lukas Wunner <lukas@wunner.de>
> Reviewed-by: Jarkko Sakkinen <jarkko@kernel.org>
> Cc: Tim Harvey <tharvey@gateworks.com>
> ---
>  Documentation/devicetree/bindings/tpm/tcg,tpm_tis-spi.yaml | 1 +
>  1 file changed, 1 insertion(+)
>
> diff --git a/Documentation/devicetree/bindings/tpm/tcg,tpm_tis-spi.yaml b/Documentation/devicetree/bindings/tpm/tcg,tpm_tis-spi.yaml
> index c3413b4..6cb2de7 100644
> --- a/Documentation/devicetree/bindings/tpm/tcg,tpm_tis-spi.yaml
> +++ b/Documentation/devicetree/bindings/tpm/tcg,tpm_tis-spi.yaml
> @@ -20,6 +20,7 @@ properties:
>    compatible:
>      items:
>        - enum:
> +          - atmel,attpm20p
>            - infineon,slb9670
>            - st,st33htpm-spi
>            - st,st33zp24-spi

You should to send the patch set with Rob Herring as CC for syncing
up. Please do it for future versions, if there is need for additional
versions.

Rob, 3 out of 4 patches are TPM patches. Do you mind if I take all
four patches once the patch set is ready or do you want to pick this
patch (assuming that you think it is correctly implemented ofc)?

BR, Jarkko

  reply	other threads:[~2024-01-13 21:17 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-13 17:10 [PATCH v2 0/4] Add missing TPM compatible strings Lukas Wunner
2024-01-13 17:10 ` [PATCH v2 1/4] dt-bindings: tpm: Add compatible string atmel,attpm20p Lukas Wunner
2024-01-13 21:17   ` Jarkko Sakkinen [this message]
2024-01-16 18:37     ` Rob Herring
2024-01-16 18:37   ` Rob Herring
2024-01-13 17:10 ` [PATCH v2 2/4] tpm_tis_spi: " Lukas Wunner
2024-01-13 17:10 ` [PATCH v2 3/4] tpm_tis: Add compatible string atmel,at97sc3204 Lukas Wunner
2024-01-13 21:54   ` Jarkko Sakkinen
2024-01-13 17:10 ` [PATCH v2 4/4] tpm: tis_i2c: Add compatible string nuvoton,npct75x Lukas Wunner
2024-01-13 21:55   ` Jarkko Sakkinen
2024-02-20 10:55 ` [PATCH v2 0/4] Add missing TPM compatible strings Lukas Wunner
2024-02-20 18:06   ` Jarkko Sakkinen
2024-02-20 18:09     ` Jarkko Sakkinen
2024-02-20 18:12       ` Jarkko Sakkinen

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=CYDW3GS1VGP4.2PUT4XW283L99@kernel.org \
    --to=jarkko@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=jgg@ziepe.ca \
    --cc=linux-integrity@vger.kernel.org \
    --cc=lukas@wunner.de \
    --cc=peterhuewe@gmx.de \
    --cc=robh@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;
as well as URLs for NNTP newsgroup(s).