From: Adrian Hunter <ext-adrian.hunter@nokia.com>
To: Matt Fleming <matt@console-pimps.org>
Cc: Pierre Ossman <drzeus-mmc@drzeus.cx>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] mmc_core: fix data timeout for SEND_EXT_CSD
Date: Thu, 19 Feb 2009 14:12:38 +0200 [thread overview]
Message-ID: <499D4CB6.3070807@nokia.com> (raw)
In-Reply-To: <20090219112243.GB25903@console-pimps.org>
Matt Fleming wrote:
> On Thu, Feb 19, 2009 at 09:33:48AM +0200, Adrian Hunter wrote:
>> ext Pierre Ossman wrote:
>>> I'm confused. Where did the 64 come from in the first place? That
>>> function will not be called for CID/CSD when !SPI. So the way I see it
>>> the code should be:
>>>
>>> if ((opcode == MMC_SEND_CSD) || (opcode == (MMC_SEND_CID)) {
>>> data.timeout_ns = 0;
>>> data.timeout_clks = 8;
>>> } else {
>>> mmc_set_data_timeout(&data, card);
>>> }
>> Theoretically yes, it should be 8 not 64 - if all the SPI devices obey
>> the standard. As I do not have an SPI device I did not feel comfortable
>> changing it. Also 64 clocks is not a long time anyway, so it did not
>> seem to do any harm.
>
> When I wrote the code, I got the 64 clock cycle timeout from the MMC
> spec that I was looking at. Unfortunately, I don't have the spec in
> front of me at the moment. It is possible that I read the timeout for
> the !SPI case, though.
No it is my mistake. The value is 8 but the unit is 8 clock cycles
i.e. 64 clock cycles. So my comment was wrong.
next prev parent reply other threads:[~2009-02-19 11:58 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-10 15:40 [PATCH] mmc_core: fix data timeout for SEND_EXT_CSD Adrian Hunter
2009-02-11 13:30 ` Matt Fleming
2009-02-11 13:56 ` Adrian Hunter
2009-02-11 14:49 ` Adrian Hunter
2009-02-15 21:46 ` Andrew Morton
2009-02-18 20:16 ` Pierre Ossman
2009-02-19 7:33 ` Adrian Hunter
2009-02-19 11:22 ` Matt Fleming
2009-02-19 12:12 ` Adrian Hunter [this message]
2009-03-02 19:55 ` Pierre Ossman
2009-03-03 11:48 ` Adrian Hunter
2009-03-08 13:46 ` 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=499D4CB6.3070807@nokia.com \
--to=ext-adrian.hunter@nokia.com \
--cc=drzeus-mmc@drzeus.cx \
--cc=linux-kernel@vger.kernel.org \
--cc=matt@console-pimps.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