From: Jarkko Sakkinen <jarkko.sakkinen@linux.intel.com>
To: Nayna Jain <nayna@linux.vnet.ibm.com>
Cc: devicetree@vger.kernel.org, tpmdd-devel@lists.sourceforge.net,
robh@kernel.org, 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,
hellerda@linux.vnet.ibm.com, ltcgcw@us.ibm.com,
cclaudio@linux.vnet.ibm.com, honclo@linux.vnet.ibm.com
Subject: Re: [PATCH v2 1/2] Documentation: tpm: add the IBM Virtual TPM device tree binding documentation
Date: Thu, 29 Sep 2016 14:04:13 +0300 [thread overview]
Message-ID: <20160929110413.GA14359@intel.com> (raw)
In-Reply-To: <1475051441-23008-1-git-send-email-nayna@linux.vnet.ibm.com>
On Wed, Sep 28, 2016 at 04:30:40AM -0400, Nayna Jain wrote:
> Virtual TPM, which is being used on IBM POWER7+ and POWER8 systems running
> POWERVM, is currently supported by tpm device driver but lacks the
> documentation. This patch adds the missing documentation for the existing
> support.
>
> Suggested-by: Jason Gunthorpe <jgunthorpe@obsidianresearch.com>
> Signed-off-by: Nayna Jain <nayna@linux.vnet.ibm.com>
> ---
> Changelog v2:
>
> - New Patch
>
> .../devicetree/bindings/security/tpm/ibmvtpm.txt | 41 ++++++++++++++++++++++
> 1 file changed, 41 insertions(+)
> create mode 100644 Documentation/devicetree/bindings/security/tpm/ibmvtpm.txt
>
> diff --git a/Documentation/devicetree/bindings/security/tpm/ibmvtpm.txt b/Documentation/devicetree/bindings/security/tpm/ibmvtpm.txt
> new file mode 100644
> index 0000000..d89f999
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/security/tpm/ibmvtpm.txt
> @@ -0,0 +1,41 @@
> +* Device Tree Bindings for IBM Virtual Trusted Platform Module(vtpm)
> +
> +Required properties:
> +
> +- compatible : property name that conveys the platform architecture
> + identifiers, as 'IBM,vtpm'
> +- device_type : specifies type of virtual device
A generic device tree question. What is the difference between
these fields? Why the I2C one does have 'device_type'?
/Jarkko
next prev parent reply other threads:[~2016-09-29 11:04 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
2016-09-29 11:04 ` Jarkko Sakkinen [this message]
[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
[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
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
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=20160929110413.GA14359@intel.com \
--to=jarkko.sakkinen@linux.intel.com \
--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=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=robh@kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).