From: Philip Langdale <philipl@overt.org>
To: Madhusudhan c <cr.madhusudhan@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: MMCv4 support (8-bit support missing)
Date: Tue, 17 Apr 2007 08:15:54 -0700 [thread overview]
Message-ID: <4624E4AA.8050408@overt.org> (raw)
In-Reply-To: <ff1613620704162359w62df9e0ao6c43215a767bd706@mail.gmail.com>
Madhusudhan c wrote:
> Hi Pierre/philip,
>
> This is regarding the MMCv4 support that came in as part of the MMC
> core of 2.6.20 linux kernel version.
>
> The high speed MMC cards can support 4-bit/8-bit transfers. The 8-bit
> support seems to be missing from the MMCv4 support implemented by
> Philip Langdale .
> To support 8-bit transfers the core needs to implement "bus testing
> procedure". This requires support for CMD19 and CMD14.
>
> Why is the support for bus testing procedure msiing from the MMCv4 support?
Because we have not seen any 8-bit hardware - let alone any 8-bit hardware
which we know how to drive. It is unclear how necessary the bus testing sequence
is, but the main reason why it's not there is that I could never get it to work
on the sdhci controller I use for testing. Due to how the CRC is handled for these
commands, the controller gets confused, reports failure, and doesn't provide the
returned data - making the test impossible.
If you have found an 8-bit controller that we can support, we'd love to know about
it!
--phil
next prev parent reply other threads:[~2007-04-17 15:16 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 [this message]
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
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=4624E4AA.8050408@overt.org \
--to=philipl@overt.org \
--cc=cr.madhusudhan@gmail.com \
--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