From: Rob Herring <robh@kernel.org>
To: Nayna Jain <nayna@linux.vnet.ibm.com>
Cc: devicetree@vger.kernel.org, tpmdd-devel@lists.sourceforge.net,
wsa@the-dreams.de, pawel.moll@arm.com, mark.rutland@arm.com,
ijc+devicetree@hellion.org.uk, galak@codeaurora.org,
linux-i2c@vger.kernel.org, peterhuewe@gmx.de, tpmdd@selhorst.net,
jarkko.sakkinen@linux.intel.com, hellerda@linux.vnet.ibm.com,
ltcgcw@us.ibm.com, cclaudio@linux.vnet.ibm.com,
honclo@linux.vnet.ibm.com
Subject: Re: [PATCH v2 2/2] Documentation: tpm: add the Physical TPM device tree binding documentation
Date: Sat, 8 Oct 2016 16:05:22 -0500 [thread overview]
Message-ID: <20161008210522.GB22112@rob-hp-laptop> (raw)
In-Reply-To: <1475051441-23008-2-git-send-email-nayna@linux.vnet.ibm.com>
On Wed, Sep 28, 2016 at 04:30:41AM -0400, Nayna Jain wrote:
> Newly added support of TPM 2.0 eventlog securityfs pseudo files in tpm
> device driver consumes device tree bindings representing I2C based
> Physical TPM. This patch adds the documentation for corresponding device
> tree bindings of I2C based Physical TPM. These bindings are similar to
> vtpm device tree bindings being used on IBM Power7+ and Power8 Systems
> running PowerVM.
>
> Suggested-by: Jason Gunthorpe <jgunthorpe@obsidianresearch.com>
> Signed-off-by: Nayna Jain <nayna@linux.vnet.ibm.com>
> ---
> Changelog v2:
>
> - Include review feedbacks.
> - Move the doc within bindings/security/tpm.
> - Add example for compatible property in description.
> - Delete implicit properties like status, label from description.
> - Redefine linux,sml-base description.
>
> .../devicetree/bindings/security/tpm/tpm-i2c.txt | 20 ++++++++++++++++++++
> 1 file changed, 20 insertions(+)
> create mode 100644 Documentation/devicetree/bindings/security/tpm/tpm-i2c.txt
>
> diff --git a/Documentation/devicetree/bindings/security/tpm/tpm-i2c.txt b/Documentation/devicetree/bindings/security/tpm/tpm-i2c.txt
> new file mode 100644
> index 0000000..16df8bb
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/security/tpm/tpm-i2c.txt
> @@ -0,0 +1,20 @@
> +* Device Tree Bindings for I2C based Trusted Platform Module(TPM)
> +
> +Required properties:
> +
> +- compatible : 'manufacturer,model', eg. nuvoton,npct650
> +- linux,sml-base : 64-bit base address of the reserved memory allocated for
> + the firmware event log
> +- linux,sml-size : size of the memory allocated for the firmware event log
> +
> +Example (for OpenPower Systems with Nuvoton TPM 2.0 on I2C)
> +----------------------------------------------------------
> +
> +tpm@57 {
> + reg = <0x57>;
> + label = "tpm";
Not documented, but why? label is really only useful when you have
multiple items that humans need to identify like ports on ethernet
switch or LEDs.
> + compatible = "nuvoton,npct650", "nuvoton,npct601";
> + linux,sml-base = <0x7f 0xfd450000>;
> + linux,sml-size = <0x10000>;
> + status = "okay";
> +};
> --
> 2.5.0
>
next prev parent reply other threads:[~2016-10-08 21:05 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-28 8:30 [PATCH v2 1/2] Documentation: tpm: add the IBM Virtual TPM device tree binding documentation Nayna Jain
[not found] ` <1475051441-23008-1-git-send-email-nayna-23VcF4HTsmIX0ybBhKVfKdBPR1lH4CV8@public.gmane.org>
2016-09-28 8:30 ` [PATCH v2 2/2] Documentation: tpm: add the Physical " Nayna Jain
2016-10-08 21:05 ` Rob Herring [this message]
2016-10-17 2:14 ` Nayna
2016-10-08 21:11 ` [PATCH v2 1/2] Documentation: tpm: add the IBM Virtual " Rob Herring
2016-10-17 2:11 ` Nayna
2016-09-29 11:04 ` Jarkko Sakkinen
[not found] ` <20160929110413.GA14359-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
2016-10-05 20:14 ` Nayna
[not found] ` <57F55F28.1090005-23VcF4HTsmIX0ybBhKVfKdBPR1lH4CV8@public.gmane.org>
2016-10-08 21:01 ` Rob Herring
2016-10-17 2:08 ` Nayna
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=20161008210522.GB22112@rob-hp-laptop \
--to=robh@kernel.org \
--cc=cclaudio@linux.vnet.ibm.com \
--cc=devicetree@vger.kernel.org \
--cc=galak@codeaurora.org \
--cc=hellerda@linux.vnet.ibm.com \
--cc=honclo@linux.vnet.ibm.com \
--cc=ijc+devicetree@hellion.org.uk \
--cc=jarkko.sakkinen@linux.intel.com \
--cc=linux-i2c@vger.kernel.org \
--cc=ltcgcw@us.ibm.com \
--cc=mark.rutland@arm.com \
--cc=nayna@linux.vnet.ibm.com \
--cc=pawel.moll@arm.com \
--cc=peterhuewe@gmx.de \
--cc=tpmdd-devel@lists.sourceforge.net \
--cc=tpmdd@selhorst.net \
--cc=wsa@the-dreams.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