From: Mark Brown <broonie@kernel.org>
To: robh+dt@kernel.org, peterhuewe@gmx.de, jgg@ziepe.ca,
jarkko@kernel.org, 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,
Krishna Yarlagadda <kyarlagadda@nvidia.com>
Cc: thierry.reding@gmail.com, jonathanh@nvidia.com,
skomatineni@nvidia.com, ldewangan@nvidia.com
Subject: Re: (subset) [Patch V3 0/3] Tegra TPM driver with HW flow control
Date: Thu, 23 Feb 2023 18:31:01 +0000 [thread overview]
Message-ID: <167717706126.292016.17503726127804100255.b4-ty@kernel.org> (raw)
In-Reply-To: <20230223162635.19747-1-kyarlagadda@nvidia.com>
On Thu, 23 Feb 2023 21:56:32 +0530, Krishna Yarlagadda wrote:
> TPM interface spec defines flow control where TPM device would drive
> MISO at same cycle as last address bit sent by controller on MOSI. This
> state of wait can be detected by software reading the MISO line or
> by controller hardware. Support sending transfers to controller in
> single message and handle flow control in hardware. Half duplex
> controllers have to support flow control in hardware.
>
> [...]
Applied to
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/spi.git for-next
Thanks!
[2/3] spi: tegra210-quad: set half duplex flag
commit: f7482d8285b638be87a594a30edaaf1341135c1a
All being well this means that it will be integrated into the linux-next
tree (usually sometime in the next 24 hours) and sent to Linus during
the next merge window (or sooner if it is a bug fix), however if
problems are discovered then the patch may be dropped or reverted.
You may get further e-mails resulting from automated or manual testing
and review of the tree, please engage with people reporting problems and
send followup patches addressing any issues that are reported if needed.
If any updates are required or you are submitting further changes they
should be sent as incremental updates against current git, existing
patches will not be replaced.
Please add any relevant lists and maintainers to the CCs when replying
to this mail.
Thanks,
Mark
prev parent reply other threads:[~2023-02-23 18:31 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-23 16:26 [Patch V3 0/3] Tegra TPM driver with HW flow control Krishna Yarlagadda
2023-02-23 16:26 ` [Patch V3 1/3] tpm_tis-spi: Support hardware wait polling Krishna Yarlagadda
2023-02-23 17:18 ` Mark Brown
2023-02-23 18:41 ` Krishna Yarlagadda
2023-02-23 18:43 ` Mark Brown
2023-02-24 14:16 ` Krishna Yarlagadda
2023-02-24 15:51 ` Mark Brown
2023-02-24 16:21 ` Krishna Yarlagadda
2023-02-23 16:26 ` [Patch V3 2/3] spi: tegra210-quad: set half duplex flag Krishna Yarlagadda
2023-02-23 16:26 ` [Patch V3 3/3] spi: tegra210-quad: Enable TPM wait polling Krishna Yarlagadda
2023-02-23 17:28 ` Mark Brown
2023-02-23 18:46 ` Krishna Yarlagadda
2023-02-23 18:31 ` Mark Brown [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=167717706126.292016.17503726127804100255.b4-ty@kernel.org \
--to=broonie@kernel.org \
--cc=jarkko@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