From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751776AbcGOEF4 (ORCPT ); Fri, 15 Jul 2016 00:05:56 -0400 Received: from mail-qk0-f171.google.com ([209.85.220.171]:33888 "EHLO mail-qk0-f171.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750796AbcGOEFy (ORCPT ); Fri, 15 Jul 2016 00:05:54 -0400 MIME-Version: 1.0 In-Reply-To: <1468549218-19215-2-git-send-email-apronin@chromium.org> References: <1468549218-19215-1-git-send-email-apronin@chromium.org> <1468549218-19215-2-git-send-email-apronin@chromium.org> From: Guenter Roeck Date: Thu, 14 Jul 2016 21:05:53 -0700 Message-ID: Subject: Re: [PATCH 1/2] tpm: devicetree: document properties for cr50 To: Andrey Pronin Cc: Jarkko Sakkinen , Peter Huewe , Marcel Selhorst , Jason Gunthorpe , tpmdd-devel@lists.sourceforge.net, linux-kernel , Guenter Roeck , smbarber@chromium.org, Douglas Anderson , devicetree@vger.kernel.org, Rob Herring , Pawel Moll , Mark Rutland , Ian Campbell , Kumar Gala Content-Type: text/plain; charset=UTF-8 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thu, Jul 14, 2016 at 7:20 PM, Andrey Pronin wrote: > Add TPM2.0-compatible interface to Cr50. Document its properties > in devicetree. > > Signed-off-by: Andrey Pronin > --- > .../devicetree/bindings/security/tpm/cr50_spi.txt | 30 ++++++++++++++++++++++ > 1 file changed, 30 insertions(+) > create mode 100644 Documentation/devicetree/bindings/security/tpm/cr50_spi.txt > > diff --git a/Documentation/devicetree/bindings/security/tpm/cr50_spi.txt b/Documentation/devicetree/bindings/security/tpm/cr50_spi.txt > new file mode 100644 > index 0000000..1b05e51 > --- /dev/null > +++ b/Documentation/devicetree/bindings/security/tpm/cr50_spi.txt > @@ -0,0 +1,30 @@ > +* Cr50 Chip on SPI. > + > +TCG PTP FIFO Compliant Interface to Cr50 on SPI bus. > + > +Required properties: > +- compatible: Should be "google,cr50_spi". google,cr50, maybe ? The "_spi" seems redundant. Also, I agree with comments from others - the term cr50 really needs an explanation (Google thinks that it is a motor bike, a scanner, or a coffee roaster). Thanks, Guenter > +- spi-max-frequency: Maximum SPI frequency. > + > +Optional properties: > +- access-delay-msec: Required delay between subsequent transactions on SPI. > +- sleep-delay-msec: Time after the last SPI activity, after which the chip > + may go to sleep. > +- wake-start-delay-msec: Time after initiating wake up before the chip is > + ready to accept commands over SPI. > + > +Example: > + > +&spi0 { > + status = "okay"; > + > + cr50@0 { > + compatible = "google,cr50_spi"; > + reg = <0>; > + spi-max-frequency = <800000>; > + > + access-delay-msec = <2>; > + sleep-delay-msec = <1000>; > + wake-start-delay-msec = <60>; > + }; > +}; > -- > 2.6.6 >