From: Jamey Hicks <jamey.hicks@hp.com>
To: dpervushin@gmail.com
Cc: linux-kernel@vger.kernel.org
Subject: Re: [RFC] SPI core -- revisited
Date: Thu, 23 Jun 2005 11:50:26 -0400 [thread overview]
Message-ID: <42BADA42.9090908@hp.com> (raw)
In-Reply-To: <1119529135.4739.6.camel@diimka.dev.rtsoft.ru>
dmitry pervushin wrote:
>Hello guys,
>
>we finally decided to rework the SPI core and now it its ready for your comments..
>Here we have several boards equipped with SPI bus, and use this spi core with these boards;
>Drivers for them are available by request (...and if community approve this patch)
>
>
>
I'm glad to see that work is progressing on SPI core. I've worked on
drivers on both ARM linux and Blackfin uclinux that use SPI and would
prefer that they not be platform specific.
What I've found in my Blackfin work is that I need asynchronous SPI
support. The driver starts an SPI transaction and receives a callback
when the SPI transaction has completed. The operations are similar to
what you've suggested, except that the message structure includes a
pointer to a callback and a void *data pointer.
The driver I'm working on is for the Chipcon CC2420 802.15.4 radio,
which uses SPI to access its registers and transmit and receive FIFOs.
In my CC2420, it queues SPI requests and initiates the next one when an
SPI transaction completes.
Jamey
next prev parent reply other threads:[~2005-06-23 15:50 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-23 12:18 [RFC] SPI core -- revisited dmitry pervushin
2005-06-23 15:50 ` Jamey Hicks [this message]
2005-06-23 16:43 ` Russell King
2005-06-24 12:56 ` Jamey Hicks
2005-06-23 21:59 ` Jean Delvare
2005-06-24 0:35 ` Greg KH
-- strict thread matches above, loose matches on Subject: below --
2005-06-26 19:36 dpervushin
2005-06-26 20:49 ` Alexey Dobriyan
2005-06-26 20:59 ` Arjan van de Ven
2005-06-27 3:37 ` Vitaly Wool
2005-06-27 8:28 ` Arjan van de Ven
2005-06-27 9:13 ` Vitaly Wool
2005-06-27 9:20 ` Russell King
2005-06-27 10:20 ` Vitaly Wool
2005-06-28 16:49 ` Greg KH
2005-06-27 3:39 ` Vitaly Wool
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=42BADA42.9090908@hp.com \
--to=jamey.hicks@hp.com \
--cc=dpervushin@gmail.com \
--cc=linux-kernel@vger.kernel.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