public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Philip Langdale <philipl@overt.org>
To: Madhusudhan c <cr.madhusudhan@gmail.com>
Cc: Pierre Ossman <drzeus@drzeus.cx>, linux-kernel@vger.kernel.org
Subject: Re: MMCv4 support (8-bit support missing)
Date: Fri, 20 Apr 2007 09:12:58 -0700	[thread overview]
Message-ID: <4628E68A.9000809@overt.org> (raw)
In-Reply-To: <ff1613620704200421w1e1aeea5r5acc3a7c0c548b96@mail.gmail.com>

Madhusudhan c wrote:
> 
> Suppose a host controller is capable of suporting 8-bit and it tells
> the core that it can support 8-bit. Now the card that is plugged in
> might or might not support 8-bit based on the type of the card. There
> is no field in the ext_csd which will tell you what bus width the card
> can support.

My understanding is that 8-bit support on the card is not optional. ie:
the card is not mmc 4 compliant if it doesn't support 8-bit and this
is why there's no ext_csd field. The only case I could think of where
bus testing would be needed would be if a controller was placed into
a configuration where some pins were deliberately left unconnected
(perhaps because space constraints prevented the extra 4 pins from being
placed on a pcb) and there was no way to change the capabilities reported
by the controller.

But in any case - this is all hypothetical right now - one can't find
a controller in the wild for love or money (well - Arasan will sell you
a validation controller for $5000 but still...). As neither Pierre or
myself is in a position to do any sort of tests on an 8-bit controller,
we can't investigate or verify any of this.

It certainly seems that you have access to an 8-bit controller. If you
can help one or both of us get access to one, I'm sure we could work out
the right thing to do.

--phil

  reply	other threads:[~2007-04-20 16:13 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-04-17  6:59 MMCv4 support (8-bit support missing) Madhusudhan c
2007-04-17 15:15 ` Philip Langdale
2007-04-18  8:46 ` Pierre Ossman
2007-04-18 11:53   ` Madhusudhan c
2007-04-18 14:21     ` Pierre Ossman
2007-04-19 14:04       ` Madhusudhan c
2007-04-19 16:25         ` Pierre Ossman
2007-04-20 11:21           ` Madhusudhan c
2007-04-20 16:12             ` Philip Langdale [this message]
2007-04-24  5:03             ` Pierre Ossman
2007-04-26  3:34               ` Madhusudhan c
2007-04-27  6:20                 ` Pierre Ossman

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=4628E68A.9000809@overt.org \
    --to=philipl@overt.org \
    --cc=cr.madhusudhan@gmail.com \
    --cc=drzeus@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