From: Michael Buesch <mb@bu3sch.de>
To: Ben Nizette <bn@niasdigital.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Stephen Rothwell <sfr@canb.auug.org.au>,
linux-kernel <linux-kernel@vger.kernel.org>,
David Brownell <david-b@pacbell.net>,
Piot Skamruk <piotr.skamruk@gmail.com>,
openwrt-devel@lists.openwrt.org
Subject: Re: [PATCH] Add SPI over GPIO driver
Date: Tue, 15 Jul 2008 15:05:16 +0200 [thread overview]
Message-ID: <200807151505.16371.mb@bu3sch.de> (raw)
In-Reply-To: <1216099851.4265.156.camel@moss.renham>
On Tuesday 15 July 2008 07:30:51 Ben Nizette wrote:
> Looks good overall. I'm not sure that it need pretend to be
> hotpluggable though
Because the hardware _is_ hotpluggable.
> (i.e. the board info can be hardwired so there's no
> need for the board setup callback).
I'm not sure why we should limit ourselves so much by compiling
dynamic and completely individual information, like the bus
wireing into the kernel.
This _has_ to be dynamic, as the wireing is _completely_ random and
different for every machine. This is selfmade hardware. ;)
> What problem are you solving (or whole in board support are you
> plugging) in this dynamic plugging of MMCs?
This is to support running MMCs/SDs on GPIO pins.
Which board or card provides the GPIO pins doesn't matter. It doesn't
matter, as it's completely abstracted. You can even run 10 or more
of the cards at the same time, if you have enough GPIO pins.
Of course, this is mostly useful for embedded systems only.
But it is not bound to any specific type of hardware. The hardware just
has to implement generic GPIO for its GPIO pins.
--
Greetings Michael.
prev parent reply other threads:[~2008-07-15 13:05 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-14 19:09 [PATCH] Add SPI over GPIO driver Michael Buesch
2008-07-14 20:43 ` Andrew Morton
2008-07-15 12:52 ` Michael Buesch
2008-07-15 5:30 ` Ben Nizette
2008-07-15 13:05 ` Michael Buesch [this message]
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=200807151505.16371.mb@bu3sch.de \
--to=mb@bu3sch.de \
--cc=akpm@linux-foundation.org \
--cc=bn@niasdigital.com \
--cc=david-b@pacbell.net \
--cc=linux-kernel@vger.kernel.org \
--cc=openwrt-devel@lists.openwrt.org \
--cc=piotr.skamruk@gmail.com \
--cc=sfr@canb.auug.org.au \
/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