public inbox for linux-mmc@vger.kernel.org
 help / color / mirror / Atom feed
From: Wolfram Sang <w.sang@pengutronix.de>
To: Chris Ball <cjb@laptop.org>
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 13:35:53 +0100	[thread overview]
Message-ID: <20101120123553.GA11936@pengutronix.de> (raw)
In-Reply-To: <20101119215333.GB19272@void.printf.net>

[-- Attachment #1: Type: text/plain, Size: 1513 bytes --]

I know it's too late, but...

On Fri, Nov 19, 2010 at 09:53:33PM +0000, Chris Ball wrote:
> On Fri, Nov 19, 2010 at 09:40:02PM +0000, Chris Ball wrote:
> > I don't see why we should re-read ctrl here, since we've already written
> > it back to the device at this point, and we don't use it anywhere below
> > this line.
> 
> Ah, I see why now; please ignore this. 
> 
> Here's a rebased version of the patch, with some more comments:
> 
> From: Philip Rakity <prakity@marvell.com>
> Date: Fri, 19 Nov 2010 16:48:39 -0500
> Subject: [PATCH] mmc: sdhci: 8-bit bus width changes
> 
> We now:
>  * check for a v3 controller before setting 8-bit bus width
>  * offer a callback for platform code to switch to 8-bit mode, which
>    allows non-v3 controllers to support it

What does the platform_-prefix of the callback indicate?

>  * 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?

> We were previously relying only on whether the controller supported
> 8-bit, which doesn't tell us anything about the pin configuration in
> the board design.
> 
> Signed-off-by: Philip Rakity <prakity@marvell.com>
> Tested-by: Giuseppe Cavallaro <peppe.cavallaro@st.com>
> Signed-off-by: Chris Ball <cjb@laptop.org>

-- 
Pengutronix e.K.                           | Wolfram Sang                |
Industrial Linux Solutions                 | http://www.pengutronix.de/  |

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 197 bytes --]

  reply	other threads:[~2010-11-20 12:36 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 [this message]
2010-11-20 16:37       ` Philip Rakity
2010-11-20 18:24       ` Chris Ball
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=20101120123553.GA11936@pengutronix.de \
    --to=w.sang@pengutronix.de \
    --cc=cjb@laptop.org \
    --cc=linux-mmc@vger.kernel.org \
    --cc=prakity@marvell.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