From: Timo Teras <timo.teras@solidboot.com>
To: Pierre Ossman <drzeus-list@drzeus.cx>
Cc: Timo Teras <timo.teras@solidboot.com>, linux-kernel@vger.kernel.org
Subject: Re: MMC: When rescanning cards check existing cards after mmc_setup()
Date: Tue, 24 Oct 2006 13:14:58 +0300 [thread overview]
Message-ID: <20061024101458.GA17024@mail.solidboot.com> (raw)
In-Reply-To: <453B4005.8080501@drzeus.cx>
On Sun, Oct 22, 2006 at 11:55:17AM +0200, Pierre Ossman wrote:
> Timo Teras wrote:
> > Some broken cards seem to process CMD1 even in stand-by state. The result is
> > that the card replies with ILLEGAL_COMMAND error for the next command sent
> > after rescanning. Currently the next command is select card, which would
> > return the error. But the CMD7 does actually succeed and retries of the
> > command will timeout. The solution is to poll card status after the CMD1
> > which clears the cached error.
>
> I take it these cards do not reply to CMD2?
No. It just caches the error and fails the next command sent.
> This change is ok right now, but might come back to bite us in the
> future if we implement more intelligent voltage selection (right now new
> cards will have to make due with what's already selected).
I see. The voltage selection is done in mmc_setup() based on what cards are
present.
> If we check cards on both sides of mmc_setup(), then we should be covered.
Should I update my patch to do this already? Or is the code fine as is?
> Also, please add some comments about why we do this. Otherwise it will
> run the risk of getting removed in the future.
Will do.
I'll send updated patch later on.
-- Timo
next prev parent reply other threads:[~2006-10-24 10:19 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-16 9:06 MMC: When rescanning cards check existing cards after mmc_setup() Timo Teras
2006-10-22 9:55 ` Pierre Ossman
2006-10-24 10:14 ` Timo Teras [this message]
2006-10-24 16:59 ` Pierre Ossman
2006-10-25 6:37 ` [PATCH] MMC: Poll card status after rescanning cards Timo Teras
2006-10-26 7: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=20061024101458.GA17024@mail.solidboot.com \
--to=timo.teras@solidboot.com \
--cc=drzeus-list@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