From: Pierre Ossman <drzeus@drzeus.cx>
To: Madhusudhan c <cr.madhusudhan@gmail.com>
Cc: linux-kernel@vger.kernel.org, philipl@overt.org
Subject: Re: MMCv4 support (8-bit support missing)
Date: Wed, 18 Apr 2007 16:21:07 +0200 [thread overview]
Message-ID: <46262953.3040801@drzeus.cx> (raw)
In-Reply-To: <ff1613620704180453t69585e21h5c31a4fe908d0aac@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1290 bytes --]
Madhusudhan c wrote:
>
> Kyung-ju Hyun from samsung had submitted a patch for MMCPlus support
> long back, which had the bus testing procedure implemented and it
> works fine. I am able to write and read the data pattern back
> successfuly with his patch. I am not sure why his patch was not
> integrated into the main line kernel.
>
I don't think I've seen that patch. And now we have the work by Philip and
myself which adds support for both MMC 4.0 and 4.2. The only missing piece is
8-bit data and I'm not that interested in adding it until we have a driver that
can use it.
> Why should we be bothered about how controllers respond at the MMC
> core level. We need to just implement what specification says and
> leave the controller handling part to the controller driver. Am I
> correct?
Kindof. The controller drivers should indeed just handle the controller and
leave the protocol stuff to the mmc core. The problem is that this bus testing
stuff breaks the previous standards. Sending invalid CRC was not previously a
supported operation, so many controllers just toss the data when that happens.
And since the bus testing is specified as a test, not a required part of the
wide bus song and dance, we've decided to leave it out.
Rgds
Pierre
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 251 bytes --]
next prev parent reply other threads:[~2007-04-18 14:20 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 [this message]
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=46262953.3040801@drzeus.cx \
--to=drzeus@drzeus.cx \
--cc=cr.madhusudhan@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=philipl@overt.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