mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Mike Frysinger" <vapier.adi@gmail.com>
To: "Bryan Wu" <cooloney.lkml@gmail.com>
Cc: "Pierre Ossman" <drzeus-mmc@drzeus.cx>,
	"Cai, Cliff" <Cliff.Cai@analog.com>,
	linux-kernel@vger.kernel.org
Subject: Re: [patch] split MMC_CAP_4_BIT_DATA
Date: Fri, 11 Jan 2008 01:25:01 -0500	[thread overview]
Message-ID: <8bd0f97a0801102225q69b56703gaffbc85a31390b4e@mail.gmail.com> (raw)
In-Reply-To: <386072610801102217u1739d7d7v497e73a38aa876c2@mail.gmail.com>

On Jan 11, 2008 1:17 AM, Bryan Wu <cooloney.lkml@gmail.com> wrote:
> On Jan 10, 2008 7:57 PM, Pierre Ossman <drzeus-mmc@drzeus.cx> wrote:
> > On Thu, 10 Jan 2008 17:22:55 +0800
> > "Bryan Wu" <cooloney.lkml@gmail.com> wrote:
> >
> > >
> > > At page 4-3 of  ADSP-BF54x Blackfin(R) Processor Peripheral Hardware
> > > Reference, there is a table which guide us the SDH controller does not
> > > support 4-bit mode MMC card. Please found the table picture in the
> > > attachment or get the document at:
> > > http://www.analog.com/UploadedFiles/Associated_Docs/61460151169789ADSP_BF54x_Blackfin_Processor_Peripheral_Hardware_Reference.pdf
> > >
> >
> > Ok, but this just means the controller wasn't designed with 4-bit MMC in mind. As several other "SD-only" controller have been tested with modern MMC cards without a problem, this is not sufficient to explain any problem.
> >
>
> This should be some HW design issue and BF54x including SDH controller
> is in mass production.
> There is no chance to change the silicon, we just wanna use software
> driver to workaround this issue.
> So Mike's patch is here.
>
> > >
> > > Thanks, actually we are not yet convinced  by our hardware designer
> > > why BF54x SDH does not support 4-bit MMC.
> > >
> >
> > Please keep me informed on how it progresses. I'd like an at least plausible explanation, preferably also some empirical data, before I'm ready to accept Mike's patch.
> >
>
> We were told this is an hardware design issue, so please help us to
> workaround it in software side with Mike's patch.
> And how do you think my suggestion to Mike's patch,
> #define MMC_CAP_4_BIT_DATA ( MMC_CAP_SD_4_BIT_DATA | MMC_CAP_MMC_4_BIT_DATA)
> Then no need to change other MMC host drivers

i can send an updated patch as needed.  i think Bryan's suggestion
here is a good one.
-mike

  reply	other threads:[~2008-01-11  6:25 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
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 [this message]
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=8bd0f97a0801102225q69b56703gaffbc85a31390b4e@mail.gmail.com \
    --to=vapier.adi@gmail.com \
    --cc=Cliff.Cai@analog.com \
    --cc=cooloney.lkml@gmail.com \
    --cc=drzeus-mmc@drzeus.cx \
    --cc=linux-kernel@vger.kernel.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®