public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: David Brownell <david-b@pacbell.net>
To: Ben Nizette <bn@niasdigital.com>, Michael Buesch <mb@bu3sch.de>
Cc: Andrew Morton <akpm@linux-foundation.org>,
	Stephen Rothwell <sfr@canb.auug.org.au>,
	linux-kernel <linux-kernel@vger.kernel.org>,
	Piot Skamruk <piotr.skamruk@gmail.com>,
	Pierre Ossman <drzeus-mmc@drzeus.cx>,
	openwrt-devel@lists.openwrt.org
Subject: Re: [PATCH] Add dynamic MMC-over-SPI-GPIO driver
Date: Mon, 21 Jul 2008 13:49:36 -0700	[thread overview]
Message-ID: <200807211349.37227.david-b@pacbell.net> (raw)
In-Reply-To: <1216098409.4265.144.camel@moss.renham>

On Monday 14 July 2008, Ben Nizette wrote:
> 
> On Mon, 2008-07-14 at 21:09 +0200, Michael Buesch wrote:
> > This driver provides a sysfs interface to dynamically create
> > and destroy GPIO-based MMC/SD card interfaces.
> > So an MMC or SD card can be connected to generic GPIO pins
> > and be configured dynamically from userspace.
> 
> Can you use mmc-spi attached to spi-gpio and be done with it? 

Yes, that's how some of the early mmc-spi work was done.  ;)


> Sure you 
> won't have the dynamic alloc capability but you won't be reinventing the
> wheel either.  You don't have dynamic creation for any other platform
> device and if you need it then, IMO, it'd be better solved in a more
> generic way.
> 
> btw, what's this spi-gpio thing?  I can't see it in mainline except in a
> s3c24xx specific way.  My domestic blindness??

ISTR a patch for that, sitting somewhere in my mailbox waiting
for review cycles.  I've sent examples of such stuff around
before too.

I've held back submitting a spi-gpio driver until I could come
up with a way to configure it which would let the GPIO calls
get inlined ... because otherwise, there's a nasty speed penalty.

It's the difference between a function call per GPIO operation
and an instruction per GPIO operation.  Consider that each SPI
clock cycle requires four such operations, and GPIO function
calls often take 30 instructions ... there's a big penalty to
the non-inlined bitbangers, which is only partly addressed by
having those function calls sitting in I-cache.

- Dave

  parent reply	other threads:[~2008-07-21 20:49 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-14 19:09 [PATCH] Add dynamic MMC-over-SPI-GPIO driver Michael Buesch
2008-07-14 20:54 ` Andrew Morton
2008-07-15 12:58   ` Michael Buesch
2008-07-15  5:06 ` Ben Nizette
2008-07-15 13:00   ` Michael Buesch
2008-07-21 20:49   ` David Brownell [this message]
2008-07-15 17:42 ` Michael Buesch

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=200807211349.37227.david-b@pacbell.net \
    --to=david-b@pacbell.net \
    --cc=akpm@linux-foundation.org \
    --cc=bn@niasdigital.com \
    --cc=drzeus-mmc@drzeus.cx \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mb@bu3sch.de \
    --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