From: Lee Revell <rlrevell@joe-job.com>
To: Hinko Kocevar <hinko.kocevar@cetrtapot.si>
Cc: Greg KH <greg@kroah.com>, Rui Sousa <rui.sousa@laposte.net>,
"Mark M. Hoffman" <mhoffman@lightlink.com>,
dmitry pervushin <dpervushin@ru.mvista.com>,
linux-kernel@vger.kernel.org,
lm-sensors <lm-sensors@lm-sensors.org>
Subject: Re: [RFC] SPI core
Date: Thu, 09 Jun 2005 11:41:30 -0400 [thread overview]
Message-ID: <1118331690.15527.32.camel@mindpipe> (raw)
In-Reply-To: <42A81C56.1070602@cetrtapot.si>
On Thu, 2005-06-09 at 12:39 +0200, Hinko Kocevar wrote:
> I would also like to see SPI core in linux driver model, but nothing
> like I2C
> stuff. SPI is far to simple (and yet so diverse) that much more simple
> concept
> could be used.
Did you look at sound/i2c/i2c.c? ALSA has its own i2c implementation,
only 333 lines, due to the kernel i2c core being overly complex for
ALSA's needs.
"Although there is a standard i2c layer on Linux, ALSA has its own i2c
codes for some cards, because the soundcard needs only a simple
operation and the standard i2c API is too complicated for such a
purpose."
(from http://www.alsa-project.org/~iwai/writing-an-alsa-driver/x77.htm)
Personally, I would start with this, then add any needed functionality.
Lee
next prev parent reply other threads:[~2005-06-09 15:41 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-31 16:09 [RFC] SPI core dmitry pervushin
2005-05-31 18:33 ` randy_dunlap
2005-05-31 20:44 ` Alexey Dobriyan
2005-05-31 21:41 ` NZG
2005-05-31 23:20 ` Greg KH
2005-05-31 23:32 ` Greg KH
2005-06-02 4:06 ` Mark M. Hoffman
2005-06-02 4:51 ` Greg KH
2005-06-02 13:02 ` Rui Sousa
2005-06-09 7:15 ` Greg KH
2005-06-09 10:39 ` Hinko Kocevar
2005-06-09 15:41 ` Lee Revell [this message]
2005-06-02 10:09 ` dmitry pervushin
2005-06-09 12:33 ` Pekka Enberg
2005-06-09 16:19 ` Alexey Dobriyan
2005-06-09 17:41 ` Pekka Enberg
-- strict thread matches above, loose matches on Subject: below --
2005-06-01 1:19 David Brownell
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=1118331690.15527.32.camel@mindpipe \
--to=rlrevell@joe-job.com \
--cc=dpervushin@ru.mvista.com \
--cc=greg@kroah.com \
--cc=hinko.kocevar@cetrtapot.si \
--cc=linux-kernel@vger.kernel.org \
--cc=lm-sensors@lm-sensors.org \
--cc=mhoffman@lightlink.com \
--cc=rui.sousa@laposte.net \
/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