From: Mark Brown <broonie-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
To: Christophe Leroy <christophe.leroy-GgN8y9CXRhA@public.gmane.org>
Cc: linux-spi <linux-spi-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: Re: How to handle SPI components requiring heading/leading clock cycles with CS off
Date: Wed, 24 Aug 2016 11:56:40 +0100 [thread overview]
Message-ID: <20160824105640.GC22076@sirena.org.uk> (raw)
In-Reply-To: <8c6cbd99-7dd8-bbbf-89ee-a33752ab3063-GgN8y9CXRhA@public.gmane.org>
[-- Attachment #1: Type: text/plain, Size: 613 bytes --]
On Wed, Aug 24, 2016 at 12:49:55PM +0200, Christophe Leroy wrote:
> Le 24/08/2016 à 11:44, Mark Brown a écrit :
> > If you leave the device with cs_change set so the chip select is low it
> > should do the right thing after the first message, though obviously you
> > won't be able to share the chip select then.
> What is needed is to get some SPI clock cycles with CS off i.e. CS high.
> With cs_change, CS will remain low i.e. CS active
No, it'll change chip select so if it's already set it'll deassert and
if you leave it deasserted at the end of a transaction it should leave
it deasserted.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 473 bytes --]
next prev parent reply other threads:[~2016-08-24 10:56 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-23 16:10 How to handle SPI components requiring heading/leading clock cycles with CS off Christophe Leroy
[not found] ` <79679118-c092-1f9c-1972-0bb81bc59411-GgN8y9CXRhA@public.gmane.org>
2016-08-24 9:44 ` Mark Brown
[not found] ` <20160824094456.GB22076-GFdadSzt00ze9xe1eoZjHA@public.gmane.org>
2016-08-24 10:49 ` Christophe Leroy
[not found] ` <8c6cbd99-7dd8-bbbf-89ee-a33752ab3063-GgN8y9CXRhA@public.gmane.org>
2016-08-24 10:56 ` Mark Brown [this message]
[not found] ` <20160824105640.GC22076-GFdadSzt00ze9xe1eoZjHA@public.gmane.org>
2016-08-24 11:03 ` Christophe Leroy
[not found] ` <15444613-2f3d-9417-7d81-e545058afdf0-GgN8y9CXRhA@public.gmane.org>
2016-08-24 11:12 ` Mark Brown
[not found] ` <20160824111206.GD22076-GFdadSzt00ze9xe1eoZjHA@public.gmane.org>
2016-08-24 11:19 ` Christophe Leroy
[not found] ` <9e854e9d-146c-61ea-da6e-a46b316b56c5-GgN8y9CXRhA@public.gmane.org>
2016-08-24 11:27 ` 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=20160824105640.GC22076@sirena.org.uk \
--to=broonie-dgejt+ai2ygdnm+yrofe0a@public.gmane.org \
--cc=christophe.leroy-GgN8y9CXRhA@public.gmane.org \
--cc=linux-spi-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
/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).