From: Pierre Ossman <drzeus-mmc@drzeus.cx>
To: "Bryan Wu" <cooloney.lkml@gmail.com>
Cc: "Cai, Cliff" <Cliff.Cai@analog.com>,
"Mike Frysinger" <vapier.adi@gmail.com>,
linux-kernel@vger.kernel.org
Subject: Re: [patch] split MMC_CAP_4_BIT_DATA
Date: Thu, 10 Jan 2008 09:54:28 +0100 [thread overview]
Message-ID: <20080110095428.3b93fd18@poseidon.drzeus.cx> (raw)
In-Reply-To: <386072610801090845r14510fb8tbcca76d605458a96@mail.gmail.com>
On Thu, 10 Jan 2008 00:45:27 +0800
"Bryan Wu" <cooloney.lkml@gmail.com> wrote:
>
> Actually, Blackfin BF54x on-chip SDIO host controller is supposed to
> support 1-bit and 4-bit MMC or SD. But in the real platform, when MMC
> works at 4-bit mode there will be a FIFO underrun error
> (http://blackfin.uclinux.org/gf/project/uclinux-dist/tracker/?action=TrackerItemEdit&tracker_item_id=3535).
> While SD works at 4-bit mode is OK. We believe this is a hardware
> issue of the SDIO host controller of BF54x.
Odd. As there shouldn't be a difference, I'm inclined to believe that this is card dependent. So it could as well appear with some SD cards as well.
How much have you tested this issue? That tracker entry isn't very verbose.
Also, how can an underrun appear? The system should have flow control. And an underrun does not sound like a bus problem, rather that you have a card with different speed characteristics than the hardware/driver can handle.
>
> We intend to workaround in our own BF54x SDIO host controller driver,
> but there is no place for us to determine MMC or SD. One choice is to
> hack common code like this:
_If_ it truly cannot handle 4-bit MMC, then Mike's patch is the way to go. But I'm not yet convinced that the problem is related to MMC vs SD.
Rgds
--
-- Pierre Ossman
Linux kernel, MMC maintainer http://www.kernel.org
PulseAudio, core developer http://pulseaudio.org
rdesktop, core developer http://www.rdesktop.org
next prev parent reply other threads:[~2008-01-10 8:54 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-08 18:29 Mike Frysinger
2008-01-08 19:21 ` Pierre Ossman
2008-01-08 19:40 ` Mike Frysinger
2008-01-08 20:49 ` Pierre Ossman
2008-01-08 21:44 ` Mike Frysinger
2008-01-09 7:21 ` Pierre Ossman
2008-01-09 2:32 ` Bryan Wu
2008-01-09 3:21 ` Cai, Cliff
2008-01-09 7:23 ` Pierre Ossman
2008-01-09 16:45 ` Bryan Wu
2008-01-10 8:54 ` Pierre Ossman [this message]
2008-01-10 9:22 ` Bryan Wu
2008-01-10 11:57 ` Pierre Ossman
2008-01-11 6:17 ` Bryan Wu
2008-01-11 6:25 ` Mike Frysinger
2008-01-11 8:40 ` Pierre Ossman
2008-01-11 9:08 ` Mike Frysinger
2008-01-11 9:35 ` Pierre Ossman
2008-01-11 9:47 ` Mike Frysinger
2008-01-11 10:05 ` Pierre Ossman
2008-01-11 10:22 ` Bryan Wu
2008-01-11 11:18 ` Pierre Ossman
2008-01-11 17:52 ` Robin Getz
2008-01-12 13:02 ` Robin Getz
2008-01-12 15:24 ` Bryan Wu
2008-01-12 15:39 ` Pierre Ossman
2008-01-09 4:23 ` Bryan Wu
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=20080110095428.3b93fd18@poseidon.drzeus.cx \
--to=drzeus-mmc@drzeus.cx \
--cc=Cliff.Cai@analog.com \
--cc=cooloney.lkml@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=vapier.adi@gmail.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
Powered by JetHome