From: Mark Brown <broonie@kernel.org>
To: Krishna Yarlagadda <kyarlagadda@nvidia.com>
Cc: 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,
thierry.reding@gmail.com, jonathanh@nvidia.com,
skomatineni@nvidia.com, ldewangan@nvidia.com
Subject: Re: [Patch V4 3/3] spi: tegra210-quad: set half duplex flag
Date: Fri, 24 Feb 2023 16:37:31 +0000 [thread overview]
Message-ID: <Y/jny4dDix7txf0y@sirena.org.uk> (raw)
In-Reply-To: <20230224154941.68587-4-kyarlagadda@nvidia.com>
[-- Attachment #1: Type: text/plain, Size: 281 bytes --]
On Fri, Feb 24, 2023 at 09:19:41PM +0530, Krishna Yarlagadda wrote:
> Tegra QSPI controller only supports half duplex transfers.
> Set half duplex constrain flag.
This was already applied I think? If any changes are required to what
was applied please send an incremental patch.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2023-02-24 16:37 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-24 15:49 [Patch V4 0/3] Tegra TPM driver with HW flow control Krishna Yarlagadda
2023-02-24 15:49 ` [Patch V4 1/3] spi: Add TPM HW flow flag Krishna Yarlagadda
2023-02-24 15:49 ` [Patch V4 2/3] tpm_tis-spi: Support hardware wait polling Krishna Yarlagadda
2023-02-24 15:49 ` [Patch V4 3/3] spi: tegra210-quad: set half duplex flag Krishna Yarlagadda
2023-02-24 16:37 ` Mark Brown [this message]
2023-02-24 16:43 ` Krishna Yarlagadda
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/jny4dDix7txf0y@sirena.org.uk \
--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