All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Shawn.Dong" <shawn.dong.cx@gmail.com>
To: cjb@laptop.org, w.sang@pengutronix.de
Cc: linux-mmc@vger.kernel.org
Subject: Re: [PATCH]mmc: sdhci: use udelay instead of mdelay for some cases
Date: Fri, 4 Nov 2011 16:24:47 +0800	[thread overview]
Message-ID: <20111104082445.GA32546@gmail.com> (raw)
In-Reply-To: <20111027060213.GB28387@pengutronix.de>

On Thu, Oct 27, 2011 at 08:02:13AM +0200, Wolfram Sang wrote:
>
>> Even there are some SDHCI hardwares cannot be stable in microseconds, I
>> think this is also OK since they just need to wait for a few more loops. The
>> total waiting time is the same as before.
>
>Well, I still think this is curing the symptoms not the cause. But will talk
>with Chris about it since we are both in Prague at the moment...
Hi Wolfram & Chris,

   This issue was found by using ftrace to track the irqsoff latency. Each time
   to call mmc_power_off, the latency is about 1ms on my platform. And this 1ms
   delay is causing by the mdelay(1) in _set_ios.

   You know, after changing some register like CLOCK_CONTROL or RESET, driver
   will start to check them every 1ms since we are using mdelay(1). For some
   devices, it needn't software to wait for 1ms, but only some milliseconds. So
   I think change to use udelay() is much better for those devices.

   How do you think? Can you give some of your advice? Thank you.

   Best Regards
   Shawn

      reply	other threads:[~2011-11-04  8:38 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-10-27  4:18 [PATCH]mmc: sdhci: use udelay instead of mdelay for some cases Shawn.Dong
2011-10-27  5:09 ` Barry Song
2011-10-27  5:15 ` Wolfram Sang
2011-10-27  5:09   ` Shawn.Dong
2011-10-27  6:02     ` Wolfram Sang
2011-11-04  8:24       ` Shawn.Dong [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=20111104082445.GA32546@gmail.com \
    --to=shawn.dong.cx@gmail.com \
    --cc=cjb@laptop.org \
    --cc=linux-mmc@vger.kernel.org \
    --cc=w.sang@pengutronix.de \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.