From: Mark Brown <broonie@kernel.org>
To: Linus Walleij <linus.walleij@linaro.org>
Cc: "Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>,
linuxppc-dev@lists.ozlabs.org,
"Anatolij Gustschin" <agust@denx.de>,
linux-spi@vger.kernel.org
Subject: Re: [PATCH 1/2] spi: mpc512x-psc: Use the framework .set_cs()
Date: Thu, 30 Jul 2020 11:38:07 +0100 [thread overview]
Message-ID: <20200730103807.GA5055@sirena.org.uk> (raw)
In-Reply-To: <20200729214817.478834-1-linus.walleij@linaro.org>
[-- Attachment #1: Type: text/plain, Size: 323 bytes --]
On Wed, Jul 29, 2020 at 11:48:16PM +0200, Linus Walleij wrote:
> The mpc512x-psc is rolling its own chip select control code,
> but the SPI master framework can handle this. It was also
> evaluating the CS status for each transfer but the CS change
> should be per-message not per-transfer.
No, CS change is per transfer.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
prev parent reply other threads:[~2020-07-30 10:41 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-29 21:48 [PATCH 1/2] spi: mpc512x-psc: Use the framework .set_cs() Linus Walleij
2020-07-29 21:48 ` [PATCH 2/2] spi: mpc512x-psc: Convert to use GPIO descriptors Linus Walleij
2020-07-30 10:38 ` 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=20200730103807.GA5055@sirena.org.uk \
--to=broonie@kernel.org \
--cc=agust@denx.de \
--cc=linus.walleij@linaro.org \
--cc=linux-spi@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=u.kleine-koenig@pengutronix.de \
/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).