All of lore.kernel.org
 help / color / mirror / Atom feed
From: Oshri Alkoby <oshrialkoby85@gmail.com>
To: robh+dt@kernel.org, mark.rutland@arm.com, peterhuewe@gmx.de,
	jarkko.sakkinen@linux.intel.com, jgg@ziepe.ca, arnd@arndb.de,
	gregkh@linuxfoundation.org, oshrialkoby85@gmail.com,
	oshri.alkoby@nuvoton.com
Cc: devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
	linux-integrity@vger.kernel.org, gcwilson@us.ibm.com,
	kgoldman@us.ibm.com, nayna@linux.vnet.ibm.com,
	dan.morav@nuvoton.com, tomer.maimon@nuvoton.com
Subject: [PATCH v2 1/2] dt-bindings: tpm: add the TPM I2C PTP device tree binding documentation
Date: Fri, 28 Jun 2019 18:13:26 +0300	[thread overview]
Message-ID: <20190628151327.206818-2-oshrialkoby85@gmail.com> (raw)
In-Reply-To: <20190628151327.206818-1-oshrialkoby85@gmail.com>

Signed-off-by: Oshri Alkoby <oshrialkoby85@gmail.com>
---
 .../bindings/security/tpm/tpm-i2c-ptp.txt     | 24 +++++++++++++++++++
 1 file changed, 24 insertions(+)
 create mode 100644 Documentation/devicetree/bindings/security/tpm/tpm-i2c-ptp.txt

diff --git a/Documentation/devicetree/bindings/security/tpm/tpm-i2c-ptp.txt b/Documentation/devicetree/bindings/security/tpm/tpm-i2c-ptp.txt
new file mode 100644
index 000000000000..8b0207fdf3e2
--- /dev/null
+++ b/Documentation/devicetree/bindings/security/tpm/tpm-i2c-ptp.txt
@@ -0,0 +1,24 @@
+* Device Tree Bindings for I2C PTP based Trusted Platform Module(TPM)
+
+The TCG defines a hardware protocol, registers and interface (based
+on the TPM Interface Specification) for accessing TPM devices
+implemented with an I2C interface.
+
+Refer to the 'I2C Interface Definition' section in 'TCG PC Client
+PlatformTPMProfile(PTP) Specification' publication for specification.
+
+Required properties:
+
+- compatible     : Should be "tcg,tpm_i2c_ptp"
+- reg            : Address on the bus
+- tpm-pirq       : Input gpio pin, used for host interrupts
+
+Example (for Raspberry Pie 3 Board with Nuvoton's NPCT75X (2.0)
+-------------------------------------------------------------------
+
+tpm_i2c_ptp: tpm_i2c_ptp@2e {
+
+	compatible = "tcg,tpm_i2c_ptp";
+	reg = <0x2e>;
+	tpm-pirq = <&gpio 24 GPIO_ACTIVE_HIGH>;
+};
-- 
2.18.0


  reply	other threads:[~2019-06-28 15:14 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-06-28 15:13 [PATCH v2 0/2] char: tpm: add new driver for tpm i2c ptp Oshri Alkoby
2019-06-28 15:13 ` Oshri Alkoby [this message]
2019-06-28 15:13 ` [PATCH v2 2/2] " Oshri Alkoby
2019-07-04  8:43 ` [PATCH v2 0/2] " Jarkko Sakkinen
2019-07-04 11:29   ` Alexander Steffen
2019-07-04 11:29     ` Alexander Steffen
2019-07-04 17:48     ` Oshri Alkobi
2019-07-05 11:28       ` Jarkko Sakkinen
     [not found]         ` <6e7ff1b958d84f6e8e585fd3273ef295@NTILML02.nuvoton.com>
2019-07-15  8:08           ` Tomer Maimon
2019-07-15  9:45             ` Jarkko Sakkinen
2019-07-15  9:45               ` Jarkko Sakkinen
2019-07-18 12:51               ` Eyal.Cohen
2019-07-18 12:51                 ` Eyal.Cohen
2019-07-18 12:51                 ` Eyal.Cohen
2019-07-18 17:10                 ` Alexander Steffen
2019-07-18 17:10                   ` Alexander Steffen
2019-07-30  8:39                   ` Benoit HOUYERE
2019-07-30  8:39                     ` Benoit HOUYERE
2019-07-30 17:42                     ` Alexander Steffen
2019-07-30 17:42                       ` Alexander Steffen
2019-09-06 12:16                       ` Benoit HOUYERE
2019-09-06 12:16                         ` Benoit HOUYERE
2019-08-15 17:03                   ` Oshri Alkobi
2019-08-16 16:12                     ` Alexander Steffen
2019-08-16 16:12                       ` Alexander Steffen
2019-08-25 11:25                       ` Oshri Alkobi
2019-07-17  7:48             ` Alexander Steffen
2019-07-17  7:48               ` Alexander Steffen
2019-07-05 11:15     ` Jarkko Sakkinen

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=20190628151327.206818-2-oshrialkoby85@gmail.com \
    --to=oshrialkoby85@gmail.com \
    --cc=arnd@arndb.de \
    --cc=dan.morav@nuvoton.com \
    --cc=devicetree@vger.kernel.org \
    --cc=gcwilson@us.ibm.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=jarkko.sakkinen@linux.intel.com \
    --cc=jgg@ziepe.ca \
    --cc=kgoldman@us.ibm.com \
    --cc=linux-integrity@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mark.rutland@arm.com \
    --cc=nayna@linux.vnet.ibm.com \
    --cc=oshri.alkoby@nuvoton.com \
    --cc=peterhuewe@gmx.de \
    --cc=robh+dt@kernel.org \
    --cc=tomer.maimon@nuvoton.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.