From: Pierre Ossman <drzeus@drzeus.cx>
To: Andres Salomon <dilinger@queued.net>
Cc: akpm@linux-foundation.org, drzeus-sdhci@drzeus.cx,
sdhci-devel@lists.drzeus.cx, linux-kernel@vger.kernel.org
Subject: Re: [OLPC] sdhci: add quirk for the Marvell CaFe's vdd/powerup issue
Date: Fri, 27 Jun 2008 18:29:45 +0200 [thread overview]
Message-ID: <20080627182945.615d5adf@mjolnir.drzeus.cx> (raw)
In-Reply-To: <20080621211516.0645a46f@xo-debian>
[-- Attachment #1: Type: text/plain, Size: 1269 bytes --]
On Sat, 21 Jun 2008 21:15:16 -0400
Andres Salomon <dilinger@queued.net> wrote:
> This has been sitting around unloved for way too long..
>
> The Marvell CaFe chip's SD implementation chokes during card insertion
> if one attempts to set the voltage and power up in the same
> SDHCI_POWER_CONTROL register write. This adds a quirk that does
> that particular dance in two steps.
>
> It also adds an entry to pci_ids.h for the CaFe chip's SD device.
>
> Signed-off-by: Andres Salomon <dilinger@debian.org>
> ---
Looks ok, but please try to diff against my -next branch. The sdhci
driver has been split up into a core and PCI part.
> @@ -774,6 +784,14 @@ static void sdhci_set_power(struct sdhci_host *host, unsigned short power)
> BUG();
> }
>
> + /*
> + * At least the CaFe chip gets confused if we set the voltage
> + * and set turn on power at the same time, so set the voltage first.
> + */
This comment should probably say "Marvell controller" or something like
that. Few know of the CaFE name.
--
-- Pierre Ossman
WARNING: This correspondence is being monitored by the
Swedish government. Make sure your server uses encryption
for SMTP traffic and consider using PGP for end-to-end
encryption.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 197 bytes --]
next prev parent reply other threads:[~2008-06-27 16:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-22 1:15 Andres Salomon
2008-06-27 16:29 ` Pierre Ossman [this message]
2008-06-28 17:02 ` Joel Stanley
2008-07-01 3:07 ` Andres Salomon
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=20080627182945.615d5adf@mjolnir.drzeus.cx \
--to=drzeus@drzeus.cx \
--cc=akpm@linux-foundation.org \
--cc=dilinger@queued.net \
--cc=drzeus-sdhci@drzeus.cx \
--cc=linux-kernel@vger.kernel.org \
--cc=sdhci-devel@lists.drzeus.cx \
/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
all inboxes | Powered by JetHome®