From: Mark Brown <broonie-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
To: Oleksij Rempel <linux-YEK0n+YFykbzxQdaRaTXBw@public.gmane.org>
Cc: linux-spi-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
dirk.behme-V5te9oGctAVWk0Htik3J/w@public.gmane.org,
"EXTERNAL Rempel Oleksij (Brunel,
CM-AI/ECO3)"
<fixed-term.Oleksij.Rempel-V5te9oGctAVWk0Htik3J/w@public.gmane.org>
Subject: Re: propper support of 5 wire SPI (SPI_READY signal)
Date: Sat, 12 Mar 2016 14:21:32 +0700 [thread overview]
Message-ID: <20160312072132.GA3898@sirena.org.uk> (raw)
In-Reply-To: <56CAF443.8010705-YEK0n+YFykbzxQdaRaTXBw@public.gmane.org>
[-- Attachment #1: Type: text/plain, Size: 832 bytes --]
On Mon, Feb 22, 2016 at 12:42:59PM +0100, Oleksij Rempel wrote:
> Am 22.02.2016 um 12:09 schrieb Mark Brown:
> > Oh, so this isn't SPI_READY?
> Not 100%.
> According to TI documentation, transfer initiated by master looks like:
> 1. Master: SPIx_CS (on)
> 2. Slave: SPIx_READY (on)
> 3. Master: Date transfer
> 4. Slave: SPIx_READY (off)
> 5. Master: SPIx_CS (off)
> Bosch version of 5-wire transfer initiated by master:
> 1. Master: SPIx_CS (on)
> 2. Slave: SPIx_REQUEST (on)
> 3. Master: Date transfer
> 4. Master: SPIx_CS (off) <----- different order.
> 5. Slave: SPIx_REQUEST (on) <-----
I can't tell the difference between these two cases. In the first case
the device gets busy after the data is transferred, in the second case
it never changes the request line but really there's no meaningful
difference I can see.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 473 bytes --]
next prev parent reply other threads:[~2016-03-12 7:21 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-19 9:08 propper support of 5 wire SPI (SPI_READY signal) Oleksij Rempel
[not found] ` <56C6DB9E.5080905-YEK0n+YFykbzxQdaRaTXBw@public.gmane.org>
2016-02-20 19:56 ` Mark Brown
[not found] ` <20160220195641.GE18327-GFdadSzt00ze9xe1eoZjHA@public.gmane.org>
2016-02-20 21:40 ` Oleksij Rempel
[not found] ` <56C8DD64.1070700-YEK0n+YFykbzxQdaRaTXBw@public.gmane.org>
2016-02-22 11:09 ` Mark Brown
[not found] ` <20160222110948.GE18327-GFdadSzt00ze9xe1eoZjHA@public.gmane.org>
2016-02-22 11:42 ` Oleksij Rempel
[not found] ` <56CAF443.8010705-YEK0n+YFykbzxQdaRaTXBw@public.gmane.org>
2016-03-12 7:21 ` Mark Brown [this message]
[not found] ` <20160312072132.GA3898-GFdadSzt00ze9xe1eoZjHA@public.gmane.org>
2016-03-13 14:18 ` Oleksij Rempel
2016-02-22 9:21 ` Geert Uytterhoeven
[not found] ` <CAMuHMdW0P-uNBA94jvvVQqXH2c4DY45U4GnYufkPDQAqZm7u9g-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2016-02-22 11:30 ` Oleksij Rempel
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=20160312072132.GA3898@sirena.org.uk \
--to=broonie-dgejt+ai2ygdnm+yrofe0a@public.gmane.org \
--cc=dirk.behme-V5te9oGctAVWk0Htik3J/w@public.gmane.org \
--cc=fixed-term.Oleksij.Rempel-V5te9oGctAVWk0Htik3J/w@public.gmane.org \
--cc=linux-YEK0n+YFykbzxQdaRaTXBw@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.