From: Rob Herring <robh-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
To: Nayna Jain <nayna-23VcF4HTsmIX0ybBhKVfKdBPR1lH4CV8@public.gmane.org>
Cc: mark.rutland-5wv7dgnIgG8@public.gmane.org,
devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
pawel.moll-5wv7dgnIgG8@public.gmane.org,
ijc+devicetree-KcIKpvwj1kUDXYZnReoRVg@public.gmane.org,
wsa-z923LK4zBo2bacvFa/9K2g@public.gmane.org,
honclo-23VcF4HTsmIX0ybBhKVfKdBPR1lH4CV8@public.gmane.org,
tpmdd-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org,
linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
galak-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org,
cclaudio-23VcF4HTsmIX0ybBhKVfKdBPR1lH4CV8@public.gmane.org
Subject: Re: [PATCH v2 1/2] Documentation: tpm: add the IBM Virtual TPM device tree binding documentation
Date: Sat, 8 Oct 2016 16:11:23 -0500 [thread overview]
Message-ID: <20161008211123.GA30452@rob-hp-laptop> (raw)
In-Reply-To: <1475051441-23008-1-git-send-email-nayna-23VcF4HTsmIX0ybBhKVfKdBPR1lH4CV8@public.gmane.org>
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-ePGOBjL8dl3ta4EC/59zMFaTQe2KTcn/@public.gmane.org>
> Signed-off-by: Nayna Jain <nayna-23VcF4HTsmIX0ybBhKVfKdBPR1lH4CV8@public.gmane.org>
> ---
> 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'
You use IBM here, but...
> +- device_type : specifies type of virtual device
> +- interrupts : property specifying the interrupt source number and
> + sense code associated with this virtual I/O Adapters
> +- ibm,my-drc-index : integer index for the connector between the device
use ibm here. These should be the same unless there's some history I'm
not aware of.
> + and its parent - present only if Dynamic
> + Reconfiguration(DR) Connector is enabled
> +- ibm,#dma-address-cells: specifies the number of cells that are used to
> + encode the physical address field of dma-window
> + properties
> +- ibm,#dma-size-cells : specifies the number of cells that are used to
> + encode the size field of dma-window properties
> +- ibm,my-dma-window : specifies DMA window associated with this virtual
> + IOA
Are these "standard" IBM properties? Does dma-ranges not work for you?
> +- ibm,loc-code : specifies the unique and persistent location code
> + associated with this virtual I/O Adapters
> +- 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 (IBM Virtual Trusted Platform Module)
> +---------------------------------------------
> +
> + vtpm@30000003 {
> + ibm,#dma-size-cells = <0x2>;
> + compatible = "IBM,vtpm";
> + device_type = "IBM,vtpm";
> + ibm,my-drc-index = <0x30000003>;
> + ibm,#dma-address-cells = <0x2>;
> + linux,sml-base = <0xc60e 0x0>;
> + interrupts = <0xa0003 0x0>;
> + ibm,my-dma-window = <0x10000003 0x0 0x0 0x0 0x10000000>;
> + ibm,loc-code = "U8286.41A.10082DV-V3-C3";
> + reg = <0x30000003>;
> + linux,sml-size = <0xbce10200>;
> + };
> --
> 2.5.0
>
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, SlashDot.org! http://sdm.link/slashdot
next prev parent reply other threads:[~2016-10-08 21:11 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
[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 ` Rob Herring [this message]
2016-10-17 2:11 ` [PATCH v2 1/2] Documentation: tpm: add the IBM Virtual " 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=20161008211123.GA30452@rob-hp-laptop \
--to=robh-dgejt+ai2ygdnm+yrofe0a@public.gmane.org \
--cc=cclaudio-23VcF4HTsmIX0ybBhKVfKdBPR1lH4CV8@public.gmane.org \
--cc=devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=galak-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org \
--cc=honclo-23VcF4HTsmIX0ybBhKVfKdBPR1lH4CV8@public.gmane.org \
--cc=ijc+devicetree-KcIKpvwj1kUDXYZnReoRVg@public.gmane.org \
--cc=linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=mark.rutland-5wv7dgnIgG8@public.gmane.org \
--cc=nayna-23VcF4HTsmIX0ybBhKVfKdBPR1lH4CV8@public.gmane.org \
--cc=pawel.moll-5wv7dgnIgG8@public.gmane.org \
--cc=tpmdd-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
--cc=wsa-z923LK4zBo2bacvFa/9K2g@public.gmane.org \
/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