From: Pierre Ossman <pierre@ossman.eu>
To: Chris Ball <cjb@laptop.org>
Cc: Andrew Morton <akpm@linux-foundation.org>,
linux-mmc@vger.kernel.org, HaraldWelte@viatech.com,
Deepak Saxena <dsaxena@laptop.org>
Subject: Re: [PATCH] sdhci: Increase timeout for internal clock stabilization.
Date: Sat, 19 Sep 2009 22:41:58 +0200 [thread overview]
Message-ID: <20090919224158.0e30d05a@mjolnir.ossman.eu> (raw)
In-Reply-To: <m3ocp7c31f.fsf@pullcord.laptop.org>
[-- Attachment #1: Type: text/plain, Size: 1087 bytes --]
On Fri, 18 Sep 2009 18:15:56 -0400
Chris Ball <cjb@laptop.org> wrote:
> On an OLPC XO-1.5 development board with Via VX855 chipset, the sdhci
> controller can take up to 12ms to stabilize its clock, but the current
> timeout at which we give up on the controller is 10ms.
>
> The patch increases the timeout delay rather than using a device-specific
> quirk -- since we exit the loop when the clock comes up, increasing the
> timeout value will only make us mdelay() longer in the errant case of a
> device with a clock that is not stabilizing, which it seems worth waiting
> a little longer for in general.
>
> Signed-off-by: Chris Ball <cjb@laptop.org>
> Cc: Harald Welte <HaraldWelte@viatech.com>
> ---
Seems reasonable enough to me. The initial limit was completely
arbitrary anyway.
Acked-by: Pierre Ossman <pierre@ossman.eu>
Rgds
--
-- Pierre Ossman
WARNING: This correspondence is being monitored by the
Swedish government. Make sure your server uses encryption
for SMTP traffic and consider using PGP for end-to-end
encryption.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
prev parent reply other threads:[~2009-09-19 20:42 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-18 22:15 [PATCH] sdhci: Increase timeout for internal clock stabilization Chris Ball
2009-09-19 20:41 ` Pierre Ossman [this message]
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=20090919224158.0e30d05a@mjolnir.ossman.eu \
--to=pierre@ossman.eu \
--cc=HaraldWelte@viatech.com \
--cc=akpm@linux-foundation.org \
--cc=cjb@laptop.org \
--cc=dsaxena@laptop.org \
--cc=linux-mmc@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