public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: David Brownell <david-b@pacbell.net>
To: ngustavson@emacinc.com
Cc: Linux Kernel list <linux-kernel@vger.kernel.org>
Subject: Re: passing function pointers through platform devices?
Date: Wed, 7 Mar 2007 09:55:30 -0800	[thread overview]
Message-ID: <200703070955.31370.david-b@pacbell.net> (raw)

> I'm developing an SPI- bus >MMC/SD block driver translation layer.

Another one?  There's already been significant work in that area.  See for
example

  http://marc.theaimsgroup.com/?l=linux-kernel&m=117000652529003&w=2

Which admittedly didn't behave when I just put it onto my test rig,
but seems nonetheless to be a significant step forward.  It's not like
everyone has hardware that can use such a driver after all!


> As part of this layer the write protect and card detect lines need to be read.
> The method for determining the state of these lines will be board specific.

Example, one usually wants card detect to be an IRQ, to avoid polling...


> Is it appropriate to pass a function pointer through a platform device 
> (declared in the mach initialization) to implement card_available and 
> write_protect function calls?

That's how it's done in that patch.  The model being what the PXA MMC/SD
card driver does, since that's the most generic model I found ... handling
for example systems which need to poll for card detect, as well as ones
that can use real gpio based IRQs.  The mmc_spi driver doesn't need to know
which kind of platform it's got.

- Dave



 

             reply	other threads:[~2007-03-07 17:56 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-03-07 17:55 David Brownell [this message]
2007-03-09 16:31 ` passing function pointers through platform devices? NZG
  -- strict thread matches above, loose matches on Subject: below --
2007-03-06 18:46 NZG
2007-03-07  3:53 ` Ben Nizette
2007-03-07 16:37   ` NZG
2007-03-07 17:07     ` Randy Dunlap
2007-03-07 17:36       ` NZG
2007-03-08 18:41     ` Haavard Skinnemoen
2007-03-08 18:57       ` NZG
2007-03-07 17:11 ` Paul Sokolovsky

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=200703070955.31370.david-b@pacbell.net \
    --to=david-b@pacbell.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=ngustavson@emacinc.com \
    /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