From: Mark Brown <broonie@kernel.org>
To: Hector Martin <marcan@marcan.st>
Cc: Alexandru Ardelean <alexandru.ardelean@analog.com>,
linux-spi@vger.kernel.org, linux-kernel@vger.kernel.org,
Joey Gouly <joey.gouly@arm.com>
Subject: Re: [PATCH] spi: Fix incorrect cs_setup delay handling
Date: Fri, 10 Dec 2021 16:21:04 +0000 [thread overview]
Message-ID: <YbN+cBQlsLprirxW@sirena.org.uk> (raw)
In-Reply-To: <20211210153634.171580-1-marcan@marcan.st>
[-- Attachment #1: Type: text/plain, Size: 331 bytes --]
On Sat, Dec 11, 2021 at 12:36:34AM +0900, Hector Martin wrote:
> We need to wait *after* asserting CS and before the transfer, not before
> asserting CS which isn't very useful.
This needs a better changelog, there's multiple delays being handled
here and it's not clear from this which are affected here or what the
problem is.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2021-12-10 16:21 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-10 15:36 [PATCH] spi: Fix incorrect cs_setup delay handling Hector Martin
2021-12-10 16:21 ` Mark Brown [this message]
2021-12-10 16:32 ` Hector Martin
2021-12-10 16:39 ` Mark Brown
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=YbN+cBQlsLprirxW@sirena.org.uk \
--to=broonie@kernel.org \
--cc=alexandru.ardelean@analog.com \
--cc=joey.gouly@arm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-spi@vger.kernel.org \
--cc=marcan@marcan.st \
/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