linux-integrity.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jason Gunthorpe <jgg@ziepe.ca>
To: Peter Huewe <peterhuewe@gmx.de>
Cc: oshri.alkoby@nuvoton.com, Dan.Morav@nuvoton.com,
	nayna@linux.vnet.ibm.com, dana.cohen@nuvoton.com,
	linux-integrity@vger.kernel.org, gcwilson@us.ibm.com
Subject: Re: device tree "compatible" string value for Nuvoton TPM 75xxx
Date: Mon, 21 Jan 2019 12:51:07 -0700	[thread overview]
Message-ID: <20190121195107.GE25163@ziepe.ca> (raw)
In-Reply-To: <CFC10279-4983-4EF7-8323-CFF29674D80A@gmx.de>

On Mon, Jan 21, 2019 at 08:16:04PM +0100, Peter Huewe wrote:
> Am 21. Januar 2019 17:58:48 MEZ schrieb Jason Gunthorpe <jgg@ziepe.ca>:

> >But the device compatabile string should still be something like:
> >
> > 'nuvoton,npct751','tcg,tpm-i2c-ptp'

> Since there are no quirks and no existing bindings, I would advise
> for tcg,tpm-i2c-ptp only.

At least at one point the advise was to always add a very specific
compatible string to the binding - this way if we find a problem with
that chip in the future the driver can match that string.

Jason

  reply	other threads:[~2019-01-21 19:51 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-18 15:34 device tree "compatible" string value for Nuvoton TPM 75xxx Nayna
2019-01-20 15:53 ` Dan.Morav
2019-01-21  2:26   ` Jason Gunthorpe
2019-01-21 13:51     ` Dan.Morav
2019-01-21 16:55       ` oshri.alkoby
2019-01-21 16:58         ` Jason Gunthorpe
2019-01-21 19:16           ` Peter Huewe
2019-01-21 19:51             ` Jason Gunthorpe [this message]
2019-01-23 20:22         ` Nayna
2019-01-31 21:46           ` Nayna
2019-02-04 16:39             ` oshri.alkoby

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=20190121195107.GE25163@ziepe.ca \
    --to=jgg@ziepe.ca \
    --cc=Dan.Morav@nuvoton.com \
    --cc=dana.cohen@nuvoton.com \
    --cc=gcwilson@us.ibm.com \
    --cc=linux-integrity@vger.kernel.org \
    --cc=nayna@linux.vnet.ibm.com \
    --cc=oshri.alkoby@nuvoton.com \
    --cc=peterhuewe@gmx.de \
    /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).