Devicetree
 help / color / mirror / Atom feed
From: Chris Ball <cjb@laptop.org>
To: Daniel Drake <dsd@laptop.org>
Cc: linux-mmc@vger.kernel.org, jrudholm@gmail.com,
	prakity@nvidia.com, devicetree-discuss@lists.ozlabs.org
Subject: Re: [PATCH 1/2] sdhci: add quirk for lack of 1.8v support
Date: Mon, 03 Dec 2012 14:03:28 -0500	[thread overview]
Message-ID: <877gozj6v3.fsf@octavius.laptop.org> (raw)
In-Reply-To: <20121125180121.31FB3FACF5@dev.laptop.org> (Daniel Drake's message of "Sun, 25 Nov 2012 13:01:19 -0500 (EST)")

Hi,

On Sun, Nov 25 2012, Daniel Drake wrote:
> The OLPC XO-1.75 laptop includes a SDHCI controller which is 1.8v
> capable, and it truthfully reports so in its capabilities. This
> alternate voltage is used for driving new "UHS-I" SD cards at their
> full speed.
>
> However, what the controller doesn't know is that the motherboard
> physically doesn't have a 1.8v supply available.
>
> Add a quirk so that systems such as this one can override disable
> 1.8v support, adding support for UHS-I cards (by running them at
> 3.3v).
>
> This avoids a problem where the system would first try to run the
> card at 1.8v, fail, and then not be able to fully reset the card
> to retry at the normal 3.3v voltage.
>
> This is more appropriate than using the MISSING_CAPS quirk, which
> is intended for cases where the SDHCI controller is actually lying
> about its capabilities, and would force us to somehow override both
> caps words from another source.
>
> Signed-off-by: Daniel Drake <dsd@laptop.org>

Thanks, pushed to mmc-next for 3.8.

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

  parent reply	other threads:[~2012-12-03 19:03 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-11-25 18:01 [PATCH 1/2] sdhci: add quirk for lack of 1.8v support Daniel Drake
2012-11-25 18:36 ` Philip Rakity
2012-11-25 18:50   ` Daniel Drake
2012-11-25 20:26 ` Philip Rakity
2012-12-03 19:03 ` Chris Ball [this message]
  -- strict thread matches above, loose matches on Subject: below --
2012-11-25 19:14 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=877gozj6v3.fsf@octavius.laptop.org \
    --to=cjb@laptop.org \
    --cc=devicetree-discuss@lists.ozlabs.org \
    --cc=dsd@laptop.org \
    --cc=jrudholm@gmail.com \
    --cc=linux-mmc@vger.kernel.org \
    --cc=prakity@nvidia.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