From: Mark Brown <broonie-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
To: "Reizer, Eyal" <eyalr-l0cyMroinI0@public.gmane.org>
Cc: "kvalo-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org"
<kvalo-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org>,
"���� �����" <eyalreizer-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>,
"linux-wireless-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
<linux-wireless-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
"netdev-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
<netdev-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
"linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
<linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
"devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
<devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
"linux-spi-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
<linux-spi-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: Re: [PATCHv2] wlcore: spi: add wl18xx support
Date: Thu, 21 Apr 2016 12:11:49 +0100 [thread overview]
Message-ID: <20160421111149.GO3217@sirena.org.uk> (raw)
In-Reply-To: <8665E2433BC68541A24DFFCA87B70F5B360C2E14-1tpBd5JUCm6IQmiDNMet8wC/G2K4zDHf@public.gmane.org>
[-- Attachment #1: Type: text/plain, Size: 856 bytes --]
On Thu, Apr 21, 2016 at 11:07:37AM +0000, Reizer, Eyal wrote:
> * (i) If the transfer isn't the last one in the message, this flag is
> * used to make the chipselect briefly go inactive in the middle of the
> * message. Toggling chipselect in this way may be needed to terminate
> * a chip command, letting a single spi_message perform all of group of
> * chip transactions together.
> Now, in my case I need the CS pin to go inactive and stay inactive during the transfer
> of the next byte for completing the SPI init correctly (sending the extra clock cycles while CS is inactive)
> If I read the above correctly, CS will only briefly go inactive but will when the next byte
> is sent it will be active again.
> What am I missing?
No, it changes the state. The main use case is a brief bounce but
you can use it for other things.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 473 bytes --]
next prev parent reply other threads:[~2016-04-21 11:11 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1460273570-12298-1-git-send-email-eyalr@ti.com>
[not found] ` <8665E2433BC68541A24DFFCA87B70F5B360B6C90@DFRE01.ent.ti.com>
2016-04-17 22:19 ` [PATCHv2] wlcore: spi: add wl18xx support Arnd Bergmann
2016-04-18 5:55 ` Reizer, Eyal
2016-04-18 14:57 ` Arnd Bergmann
2016-04-19 9:05 ` Reizer, Eyal
2016-04-19 14:21 ` Arnd Bergmann
2016-04-19 14:35 ` Reizer, Eyal
[not found] ` <8665E2433BC68541A24DFFCA87B70F5B360C0745-1tpBd5JUCm6IQmiDNMet8wC/G2K4zDHf@public.gmane.org>
2016-04-19 17:12 ` Mark Brown
[not found] ` <sjdvun1fuj4nyi0bgf268g53.1461086401627@email.android.com>
[not found] ` <sjdvun1fuj4nyi0bgf268g53.1461086401627-2ueSQiBKiTY7tOexoI0I+QC/G2K4zDHf@public.gmane.org>
2016-04-19 17:27 ` Mark Brown
[not found] ` <oe8hqfknrcljrjawnrxlohvr.1461087275186@email.android.com>
[not found] ` <oe8hqfknrcljrjawnrxlohvr.1461087275186-2ueSQiBKiTY7tOexoI0I+QC/G2K4zDHf@public.gmane.org>
2016-04-19 17:54 ` Mark Brown
[not found] ` <us0dopt1inbrt0x47njgc2vy.1461089085965@email.android.com>
[not found] ` <us0dopt1inbrt0x47njgc2vy.1461089085965-2ueSQiBKiTY7tOexoI0I+QC/G2K4zDHf@public.gmane.org>
2016-04-19 18:46 ` Mark Brown
[not found] ` <20160419184627.GG3217-GFdadSzt00ze9xe1eoZjHA@public.gmane.org>
2016-04-21 11:07 ` Reizer, Eyal
[not found] ` <8665E2433BC68541A24DFFCA87B70F5B360C2E14-1tpBd5JUCm6IQmiDNMet8wC/G2K4zDHf@public.gmane.org>
2016-04-21 11:11 ` Mark Brown [this message]
[not found] ` <8665E2433BC68541A24DFFCA87B70F5B360BF614-1tpBd5JUCm6IQmiDNMet8wC/G2K4zDHf@public.gmane.org>
2016-04-19 17:07 ` 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=20160421111149.GO3217@sirena.org.uk \
--to=broonie-dgejt+ai2ygdnm+yrofe0a@public.gmane.org \
--cc=devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=eyalr-l0cyMroinI0@public.gmane.org \
--cc=eyalreizer-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
--cc=kvalo-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org \
--cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-spi-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-wireless-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=netdev-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).