On Wed, Apr 13, 2016 at 09:55:51PM +0200, Christophe Ricard wrote:
> Spi protocol standardized by the TCG is now supported by most of TPM
> vendors.
>
> It supports SPI Bit Protocol as describe in the TCG PTP
> specification (chapter 6.4.6 SPI Bit Protocol).
>
> Irq mode is not supported.
>
> Cc: devicetree@xxxxxxxxxxxxxxx
> Signed-off-by: Peter Huewe <peter.huewe@xxxxxxxxxxxx>
> Signed-off-by: Alexander Steffen <Alexander.Steffen@xxxxxxxxxxxx>
> Signed-off-by: Christophe Ricard <christophe-h.ricard@xxxxxx>
> ---
> .../bindings/security/tpm/tpm_tis_spi.txt | 21 ++
> drivers/char/tpm/Kconfig | 12 +
> drivers/char/tpm/Makefile | 1 +
> drivers/char/tpm/tpm_tis_spi.c | 242 +++++++++++++++++++++
> 4 files changed, 276 insertions(+)
> create mode 100644 Documentation/devicetree/bindings/security/tpm/tpm_tis_spi.txt
> create mode 100644 drivers/char/tpm/tpm_tis_spi.c
>
> diff --git a/Documentation/devicetree/bindings/security/tpm/tpm_tis_spi.txt b/Documentation/devicetree/bindings/security/tpm/tpm_tis_spi.txt
> new file mode 100644
> index 0000000..31f4dcd
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/security/tpm/tpm_tis_spi.txt
> @@ -0,0 +1,21 @@
> +Required properties:
> +- compatible: Should be "st,st33htpm-spi" or "infineon,slb9670" or "tcg,tpm_tis-spi"
No underscores.
The tcg one is fine, but should not be without a specific device. So
this should be something like this:
Should be one of:
"st,st33htpm-spi"
"infineon,slb9670"
Followed by "tcg,tpm_tis-spi"
> +- spi-max-frequency: Maximum SPI frequency (depends on TPMs).
> +
> +Optional SoC Specific Properties:
> +- pinctrl-names: Contains only one value - "default".
> +- pintctrl-0: Specifies the pin control groups used for this controller.
> +
> +Example (for ARM-based BeagleBoard xM with TPM_TIS on SPI4):
> +
> +&mcspi4 {
> +
> + status = "okay";
> +
> + tpm_tis@0 {
> +
> + compatible = "tcg,tpm_tis-spi";
> +
> + spi-max-frequency = <10000000>;
> + };
> +};
--
To unsubscribe from this list: send the line "unsubscribe devicetree" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
