mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Bryan Wu" <cooloney.lkml@gmail.com>
To: "Pierre Ossman" <drzeus-mmc@drzeus.cx>, cliff.cai@analog.com
Cc: "Mike Frysinger" <vapier.adi@gmail.com>, linux-kernel@vger.kernel.org
Subject: Re: [patch] split MMC_CAP_4_BIT_DATA
Date: Wed, 9 Jan 2008 10:32:48 +0800	[thread overview]
Message-ID: <386072610801081832w2befcbafwe9215067f022ed5d@mail.gmail.com> (raw)
In-Reply-To: <20080108214946.03018d95@poseidon.drzeus.cx>

On Jan 9, 2008 4:49 AM, Pierre Ossman <drzeus-mmc@drzeus.cx> wrote:
> On Tue, 8 Jan 2008 14:40:49 -0500
> Mike Frysinger <vapier.adi@gmail.com> wrote:
>
> >
> > i dont understand what's confusing.  the Blackfin on chip host controller only
> > supports 1-bit MMC, but it supports 4-bit SD/SDIO.  this is a fact.  while it
> > may be a stupid decision, it is what it is, and i need the framework made
> > more flexible in order to get the Blackfin driver merged cleanly.  we do
> > software for hardware, we dont do hardware.
>
> Well, since I've seen no _hardware_ differences between 4-bit MMC and 4-bit SD, "support" in this case must me "vendor will guarantee it works". And that is not the kind of "support" that needs a distinction in the code.
>
> So, again, if you feel that there is a hardware difference between 4-bit MMC and 4-bit SD then please elaborate as it is my understanding that they are identical.
>

As Mike said, the reason split this flag is because Blackfin on-chip
SDIO controller's limitation.
Cliff is working on it for a long time, so I dropped him in. Hope he
can clarify the confusing things.

Thanks
-Bryan Wu

  parent reply	other threads:[~2008-01-09  2:33 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 [this message]
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
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=386072610801081832w2befcbafwe9215067f022ed5d@mail.gmail.com \
    --to=cooloney.lkml@gmail.com \
    --cc=cliff.cai@analog.com \
    --cc=drzeus-mmc@drzeus.cx \
    --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

all inboxes | Powered by JetHome®