lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <CAL_JsqLEkoa1+nnWBQHah14_6BozkMzjcSpbk-hhLS=Rnqaa8Q@mail.gmail.com>
Date:   Wed, 6 May 2020 14:02:57 -0500
From:   Rob Herring <robh@...nel.org>
To:     Amir Mizinski <amirmizi6@...il.com>
Cc:     Eyal.Cohen@...oton.com,
        Jarkko Sakkinen <jarkko.sakkinen@...ux.intel.com>,
        Oshri Alkobi <oshrialkoby85@...il.com>,
        Alexander Steffen <alexander.steffen@...ineon.com>,
        Mark Rutland <mark.rutland@....com>,
        Peter Huewe <peterhuewe@....de>,
        Jason Gunthorpe <jgg@...pe.ca>, Arnd Bergmann <arnd@...db.de>,
        Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
        benoit.houyere@...com, Eddie James <eajames@...ux.ibm.com>,
        Joel Stanley <joel@....id.au>, devicetree@...r.kernel.org,
        "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
        linux-integrity@...r.kernel.org,
        IS20 Oshri Alkoby <oshri.alkoby@...oton.com>,
        Tomer Maimon <tmaimon77@...il.com>, gcwilson@...ibm.com,
        kgoldman@...ibm.com, IS30 Dan Morav <Dan.Morav@...oton.com>,
        oren.tanami@...oton.com, shmulik.hager@...oton.com,
        amir.mizinski@...oton.com
Subject: Re: [PATCH v7 6/7] tpm: Add YAML schema for TPM TIS I2C options

On Wed, May 6, 2020 at 10:20 AM Amir Mizinski <amirmizi6@...il.com> wrote:
>
>
> On 2020-05-05 16:12, Rob Herring wrote:
> > On Mon, Apr 27, 2020 at 03:49:30PM +0300, amirmizi6@...il.com wrote:
> >> From: Amir Mizinski <amirmizi6@...il.com>
> >>
> >> Added a YAML schema to support tpm tis i2c related dt-bindings for the I2c
> >> PTP based physical layer.
> >>
> >> This patch adds the documentation for corresponding device tree bindings of
> >> I2C based Physical TPM.
> >> Refer to the 'I2C Interface Definition' section in
> >> 'TCG PC Client PlatformTPMProfile(PTP) Specification' publication
> >> for specification.
> >
> > Again, DT bindings describe h/w devices, not just a protocol. A device
> > is more than just a protocol interface. There's clocks, power rails,
> > resets, interrupts, firmware, etc.
> >
> > Unless there's something special about TPM chips that makes none of this
> > applicable and no chip will ever have any quirks (or extensions) in
> > their protocol to work-around, then you need compatible string(s) that
> > are specific to the TPM chip. You can have tcg,tpm-tis-i2c as a
> > fallback, but you need specific compatible to handle any quirks.
> >
> > Rob
>
> Hello Rob, currently yes. All TPM chip are implemented according to the TGC specs and should use the same properties for this I2C driver.
> I can't say for sure that it will be the case in the future.

Exactly. That's the issue. If you have just "tcg,tpm-tis-i2c" and need
to handle some difference in the future, then you can't without
updating the DT. You must be able to handle future issues without
updating the DT.

> Shouldn't we use the standard "tcg,tpm-tis-i2c" compatible, and if a specific TPM chip will deviate from the specs, the vendor should add an additional compatible string for it?

Name something where multiple vendors have implemented a spec and
there's no deviation. It simply doesn't exist. How would you know?

Does the TPM spec define all the things I listed above outside of just
the I2C protocol?

Also, what version of the spec is "tcg,tpm-tis-i2c"? Few specs have
only 1 version.

Rob

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ