From: Jarkko Sakkinen <jarkko@kernel.org>
To: Krishna Yarlagadda <kyarlagadda@nvidia.com>
Cc: robh+dt@kernel.org, broonie@kernel.org, peterhuewe@gmx.de,
jgg@ziepe.ca, krzysztof.kozlowski+dt@linaro.org,
linux-spi@vger.kernel.org, linux-tegra@vger.kernel.org,
linux-integrity@vger.kernel.org, linux-kernel@vger.kernel.org,
thierry.reding@gmail.com, jonathanh@nvidia.com,
skomatineni@nvidia.com, ldewangan@nvidia.com
Subject: Re: [PATCH 0/4] Tegra TPM driver with hw flow control
Date: Wed, 8 Feb 2023 04:16:25 +0200 [thread overview]
Message-ID: <Y+MF+SdrE99YCuQB@kernel.org> (raw)
In-Reply-To: <20230202161750.21210-1-kyarlagadda@nvidia.com>
On Thu, Feb 02, 2023 at 09:47:46PM +0530, Krishna Yarlagadda wrote:
> Tegra234 and Tegra241 chips have QSPI controller that supports TCG
> PC Client Specific TPM Interface Specification (TIS) flow control.
> Since the controller only supports half duplex, sw wait polling
> (flow control using full duplex transfers) method implemented in
> tpm_tis_spi_main.c does not suffice.
> Added extended driver to disable sw flow control and send
s/Added/Add/
What is "extended driver"?
> all transfers in single message. Flow control is handled by hardware.
>
> Krishna Yarlagadda (4):
> dt-bindings: tpm: Add compatible for Tegra TPM
> tpm: tegra: Support SPI tpm wait state detect
> spi: dt-bindings: Add Tegra TPM wait polling flag
> spi: tegra210-quad: Enable TPM wait polling
>
> .../security/tpm/nvidia,tegra-tpm-spi.txt | 14 ++
> ...nvidia,tegra210-quad-peripheral-props.yaml | 6 +
> drivers/char/tpm/Makefile | 1 +
> drivers/char/tpm/tpm_tis_spi.h | 1 +
> drivers/char/tpm/tpm_tis_spi_main.c | 4 +-
> drivers/char/tpm/tpm_tis_spi_tegra.c | 123 ++++++++++++++++++
> drivers/spi/spi-tegra210-quad.c | 16 +++
> 7 files changed, 164 insertions(+), 1 deletion(-)
> create mode 100644 Documentation/devicetree/bindings/security/tpm/nvidia,tegra-tpm-spi.txt
> create mode 100644 drivers/char/tpm/tpm_tis_spi_tegra.c
>
> --
> 2.17.1
>
BR, Jarkko
prev parent reply other threads:[~2023-02-08 2:16 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-02 16:17 [PATCH 0/4] Tegra TPM driver with hw flow control Krishna Yarlagadda
2023-02-02 16:17 ` [PATCH 1/4] dt-bindings: tpm: Add compatible for Tegra TPM Krishna Yarlagadda
2023-02-02 16:25 ` Krzysztof Kozlowski
2023-02-02 16:17 ` [PATCH 2/4] tpm: tegra: Support SPI tpm wait state detect Krishna Yarlagadda
2023-02-02 20:08 ` kernel test robot
2023-02-08 2:39 ` Jarkko Sakkinen
2023-02-02 16:17 ` [PATCH 3/4] spi: dt-bindings: Add Tegra TPM wait polling flag Krishna Yarlagadda
2023-02-02 16:26 ` Krzysztof Kozlowski
2023-02-02 16:17 ` [PATCH 4/4] spi: tegra210-quad: Enable TPM wait polling Krishna Yarlagadda
2023-02-08 2:16 ` Jarkko Sakkinen [this message]
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=Y+MF+SdrE99YCuQB@kernel.org \
--to=jarkko@kernel.org \
--cc=broonie@kernel.org \
--cc=jgg@ziepe.ca \
--cc=jonathanh@nvidia.com \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=kyarlagadda@nvidia.com \
--cc=ldewangan@nvidia.com \
--cc=linux-integrity@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-spi@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=peterhuewe@gmx.de \
--cc=robh+dt@kernel.org \
--cc=skomatineni@nvidia.com \
--cc=thierry.reding@gmail.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 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).