From: Oleksij Rempel <linux-YEK0n+YFykbzxQdaRaTXBw@public.gmane.org>
To: linux-spi-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
Mark Brown <broonie-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
Subject: propper support of 5 wire SPI (SPI_READY signal)
Date: Fri, 19 Feb 2016 10:08:46 +0100 [thread overview]
Message-ID: <56C6DB9E.5080905@rempel-privat.de> (raw)
[-- Attachment #1: Type: text/plain, Size: 569 bytes --]
Hallo all,
i'm working on a project which depends on 5 Wire SPI communication. It
is probably identical to spi-davinci.c with SPI_READY signal. Only
difference is that SPI_READY is not supported by hardware, in this case
GPIO input is used.
Currently this project implements SPI_READY and CS on top of spidev
driver. What makes it really ugly, slow and complicated.
My question is, are there any better, upstreamable way to implement it?
For example directly insight of spi framework? Any suggestions and
comments are welcome.
--
Regards,
Oleksij
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 213 bytes --]
next reply other threads:[~2016-02-19 9:08 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-19 9:08 Oleksij Rempel [this message]
[not found] ` <56C6DB9E.5080905-YEK0n+YFykbzxQdaRaTXBw@public.gmane.org>
2016-02-20 19:56 ` propper support of 5 wire SPI (SPI_READY signal) 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
[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=56C6DB9E.5080905@rempel-privat.de \
--to=linux-yek0n+yfykbzxqdaratxbw@public.gmane.org \
--cc=broonie-DgEjT+Ai2ygdnm+yROfE0A@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.