public inbox for linux-mmc@vger.kernel.org
 help / color / mirror / Atom feed
From: Chris Ball <cjb@laptop.org>
To: Wolfram Sang <w.sang@pengutronix.de>
Cc: Philip Rakity <prakity@marvell.com>,
	"linux-mmc@vger.kernel.org" <linux-mmc@vger.kernel.org>
Subject: Re: [RFC]  sdhci: 8 bit bus width changes
Date: Sat, 20 Nov 2010 18:24:23 +0000	[thread overview]
Message-ID: <20101120182423.GA31030@void.printf.net> (raw)
In-Reply-To: <20101120123553.GA11936@pengutronix.de>

Hi,

On Sat, Nov 20, 2010 at 01:35:53PM +0100, Wolfram Sang wrote:
> I know it's too late, but...

It's late, but it's not too late.  I'd like to send a fix for MMC cards
to Linus within the next week.  If we decide to make some small changes
here and can do it quickly, that should be fine.

> What does the platform_-prefix of the callback indicate?

That it's a hook for code (whether that's a -pltfm driver or an SDHCI
driver) that knows more about the board-level setup to implement.

> >  * introduce a quirk to specify that the board designers have indeed
> >    brought out all the pins for 8-bit to the slot.
> 
> This is not a quirk, this is platform_data, no?

Yes, I agree that platform code would be more correct than the quirk.

Thanks,

-- 
Chris Ball   <cjb@laptop.org>   <http://printf.net/>
One Laptop Per Child

  parent reply	other threads:[~2010-11-20 18:24 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-10-01 22:45 [RFC] sdhci: 8 bit bus width changes Philip Rakity
2010-11-05  7:13 ` Peppe CAVALLARO
2010-11-19 21:40 ` Chris Ball
2010-11-19 21:53   ` Chris Ball
2010-11-20 12:35     ` Wolfram Sang
2010-11-20 16:37       ` Philip Rakity
2010-11-20 18:24       ` Chris Ball [this message]
2010-11-21 19:17         ` Philip Rakity
2010-11-22 10:16           ` zhangfei gao
2010-11-22 10:36           ` zhangfei gao
2010-11-22 16:13             ` Philip Rakity
2010-11-23  2:45               ` zhangfei gao
2010-11-24 17:35           ` Chris Ball
2010-11-20 16:37     ` Philip Rakity

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=20101120182423.GA31030@void.printf.net \
    --to=cjb@laptop.org \
    --cc=linux-mmc@vger.kernel.org \
    --cc=prakity@marvell.com \
    --cc=w.sang@pengutronix.de \
    /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