From: Pierre Ossman <drzeus-list@drzeus.cx>
To: "José María Fernández González" <josemariafg@gmail.com>
Cc: Andrew Morton <akpm@linux-foundation.org>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/1] mmc: Some microSD cards are not recognized by PCIxx12 SDA controller
Date: Fri, 10 Apr 2009 23:35:46 +0200 [thread overview]
Message-ID: <20090410233546.7e8ca52b@mjolnir.ossman.eu> (raw)
In-Reply-To: <49DA9094.1070803@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1099 bytes --]
On Tue, 07 Apr 2009 01:30:28 +0200
José María Fernández González <josemariafg@gmail.com> wrote:
> It is curious. I have concentrated my tests on 2.6.29 with HZ=100 and no preemption, and I have done next tests with my microSD card and laptop:
>
> * mmc_delay(2) -> FAIL
> * mdelay(2) -> FAIL
> * mmc_delay(10) -> Works!
> * mdelay(10) -> Works!
>
Looks good. Although it would have been nice to also know exactly when
it starts working.
> And by mistake I found that:
>
> * msleep(2) -> Works!
>
This is the scheduling effect I was talking about. Basically you can
never get msleep() to delay shorter than 1/HZ seconds.
I'll queue up your patch.
Rgds
--
-- Pierre Ossman
Linux kernel, MMC maintainer http://www.kernel.org
rdesktop, core developer http://www.rdesktop.org
TigerVNC, core developer http://www.tigervnc.org
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-04-10 21:36 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-10 1:21 José María Fernández González
2009-03-24 20:17 ` Pierre Ossman
2009-03-25 8:00 ` José María Fernández González
2009-03-25 16:17 ` Pierre Ossman
2009-03-26 16:37 ` José María Fernández González
2009-04-05 18:33 ` Pierre Ossman
2009-04-06 23:30 ` José María Fernández González
2009-04-10 21:35 ` 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=20090410233546.7e8ca52b@mjolnir.ossman.eu \
--to=drzeus-list@drzeus.cx \
--cc=akpm@linux-foundation.org \
--cc=josemariafg@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
all inboxes | Powered by JetHome®