From: Jarkko Sakkinen <jarkko@kernel.org>
To: Rob Herring <robh+dt@kernel.org>
Cc: Joel Stanley <joel@jms.id.au>, Peter Huewe <peterhuewe@gmx.de>,
devicetree@vger.kernel.org, linux-integrity@vger.kernel.org,
Jason Gunthorpe <jgg@ziepe.ca>,
Johannes Holland <johannes.holland@infineon.com>,
eajames@linux.ibm.com
Subject: Re: [PATCH v2 3/3] tpm: tis-i2c: Add more compatible strings
Date: Wed, 5 Oct 2022 02:10:23 +0300 [thread overview]
Message-ID: <Yzy9X1QgtVQL+OAe@kernel.org> (raw)
In-Reply-To: <CAL_Jsq+nVQ6_RbjygeEfPYAC2p_KBdqtRdfsaukoWFG_FjRy5g@mail.gmail.com>
On Tue, Oct 04, 2022 at 04:20:56PM -0500, Rob Herring wrote:
> On Fri, Sep 30, 2022 at 4:47 PM Jarkko Sakkinen <jarkko@kernel.org> wrote:
> >
> > On Wed, Sep 28, 2022 at 02:09:57PM +0930, Joel Stanley wrote:
> > > The NPCT75x TPM is TIS compatible. It has an I2C and SPI interface.
> > >
> > > https://www.nuvoton.com/products/cloud-computing/security/trusted-platform-module-tpm/
> > >
> > > Add a compatible string for it, and the generic compatible.
> > >
> > > Signed-off-by: Joel Stanley <joel@jms.id.au>
> > > ---
> > > drivers/char/tpm/tpm_tis_i2c.c | 2 ++
> > > 1 file changed, 2 insertions(+)
> > >
> > > diff --git a/drivers/char/tpm/tpm_tis_i2c.c b/drivers/char/tpm/tpm_tis_i2c.c
> > > index 0692510dfcab..4af27b7ec5b1 100644
> > > --- a/drivers/char/tpm/tpm_tis_i2c.c
> > > +++ b/drivers/char/tpm/tpm_tis_i2c.c
> > > @@ -368,6 +368,8 @@ MODULE_DEVICE_TABLE(i2c, tpm_tis_i2c_id);
> > > #ifdef CONFIG_OF
> > > static const struct of_device_id of_tis_i2c_match[] = {
> > > { .compatible = "infineon,slb9673", },
> > > + { .compatible = "nuvoton,npct75x", },
> > > + { .compatible = "tcg,tpm-tis-i2c", },
> > > {}
> > > };
> > > MODULE_DEVICE_TABLE(of, of_tis_i2c_match);
> > > --
> > > 2.35.1
> > >
> >
> > Acked-by: Jarkko Sakkinen <jarkko@kernel.org>
> >
> > IMHO could be picked to the same tree with DT changes instead
> > of my tree.
>
> It's supposed to be the other way around. DT bindings go with drivers
> via subsystem tree. I don't take drivers.
>
> But it seems this first needs some coordination with this[1] series.
>
> Rob
>
> [1] https://lore.kernel.org/all/20220930165116.13329-1-Alexander.Steffen@infineon.com/
WFM, I can pick it (once the issues are fixed).
BR, Jarkko
next prev parent reply other threads:[~2022-10-04 23:10 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-28 4:39 [PATCH v2 0/3] tpm: tsi-i2c: Add compatible strings Joel Stanley
2022-09-28 4:39 ` [PATCH v2 1/3] dt-bindings: trivial-devices: Remove Infineon SLB9673 TPM Joel Stanley
2022-09-30 14:44 ` Rob Herring
2022-09-28 4:39 ` [PATCH v2 2/3] dt-bindings: tpm: Add schema for TIS I2C devices Joel Stanley
2022-09-30 14:45 ` Rob Herring
2022-09-28 4:39 ` [PATCH v2 3/3] tpm: tis-i2c: Add more compatible strings Joel Stanley
2022-09-30 14:44 ` Rob Herring
2022-10-05 2:28 ` Joel Stanley
2022-09-30 21:47 ` Jarkko Sakkinen
2022-10-04 21:20 ` Rob Herring
2022-10-04 23:10 ` Jarkko Sakkinen [this message]
2023-12-12 6:40 ` Guenter Roeck
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=Yzy9X1QgtVQL+OAe@kernel.org \
--to=jarkko@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=eajames@linux.ibm.com \
--cc=jgg@ziepe.ca \
--cc=joel@jms.id.au \
--cc=johannes.holland@infineon.com \
--cc=linux-integrity@vger.kernel.org \
--cc=peterhuewe@gmx.de \
--cc=robh+dt@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).