From: Pierre Ossman <pierre@ossman.eu>
To: Nicolas Pitre <nico@cam.org>
Cc: lkml <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] mvsdio: fix config failure with some high speed SDHC cards
Date: Wed, 27 May 2009 22:26:22 +0200 [thread overview]
Message-ID: <20090527222622.6539d92f@mjolnir.ossman.eu> (raw)
In-Reply-To: <alpine.LFD.2.00.0905262231120.3906@xanadu.home>
[-- Attachment #1: Type: text/plain, Size: 1280 bytes --]
On Tue, 26 May 2009 22:35:34 -0400 (EDT)
Nicolas Pitre <nico@cam.org> wrote:
>
> Especially with Sandisk SDHC cards, the second SWITCH command was failing
> with a timeout and the card was not recognized at all. However if the
> system was busy, or debugging was enabled, or a udelay(100) was inserted
> before the second SWITCH command in the core code, then the timing was
> so that the card started to work.
>
> This appears to be a problem with the host hardware. With some unusual
> block sizes, the data FIFO status doesn't indicate a "empty" state right
> away when the data transfer is done. Queuing another data transfer in
> that condition results in a transfer timeout.
>
> The empty FIFO bit eventually get set by itself in less than 50 usecs
> when it is not set right away. So let's just poll for that bit before
> configuring the controller with a new data transfer.
>
> Signed-off-by: Nicolas Pitre <nico@marvell.com>
>
You seem to be having a lot of fun with this controller. :)
Patch queued.
Rgds
--
-- 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: 198 bytes --]
prev parent reply other threads:[~2009-05-27 20:26 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-27 2:35 Nicolas Pitre
2009-05-27 20:26 ` Pierre Ossman [this message]
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=20090527222622.6539d92f@mjolnir.ossman.eu \
--to=pierre@ossman.eu \
--cc=linux-kernel@vger.kernel.org \
--cc=nico@cam.org \
/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®