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  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:   Tue, 5 May 2020 11:12:26 -0500
From:   Rob Herring <robh@...nel.org>
To:     amirmizi6@...il.com
Cc:     Eyal.Cohen@...oton.com, jarkko.sakkinen@...ux.intel.com,
        oshrialkoby85@...il.com, alexander.steffen@...ineon.com,
        mark.rutland@....com, peterhuewe@....de, jgg@...pe.ca,
        arnd@...db.de, gregkh@...uxfoundation.org, benoit.houyere@...com,
        eajames@...ux.ibm.com, joel@....id.au, devicetree@...r.kernel.org,
        linux-kernel@...r.kernel.org, linux-integrity@...r.kernel.org,
        oshri.alkoby@...oton.com, tmaimon77@...il.com, gcwilson@...ibm.com,
        kgoldman@...ibm.com, 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 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

Powered by blists - more mailing lists