public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Mika Westerberg <mika.westerberg@linux.intel.com>
To: Linus Walleij <linus.walleij@linaro.org>
Cc: linux-mmc@vger.kernel.org, linux-kernel@vger.kernel.org, cjb@laptop.org
Subject: Re: [PATCH 1/2] mmc: add functions to enable/disable aggressive clock gating
Date: Thu, 18 Aug 2011 13:34:41 +0300	[thread overview]
Message-ID: <20110818103441.GX16790@intel.com> (raw)
In-Reply-To: <20110817121914.GW16790@intel.com>

On Wed, Aug 17, 2011 at 03:19:14PM +0300, Mika Westerberg wrote:
> On Wed, Aug 17, 2011 at 09:51:31AM +0200, Linus Walleij wrote:
> > 
> > I would suggest that in all patches using these functions, try
> > to replace:
> > 
> > mmc_host_clk_disable() -> mmc_host_clk_ungate()
> > mmc_host_clk_enable() -> mmc_host_clk_gate()
> > 
> 
> Wow, that is indeed *much* cleaner way of doing this!
> 
> One thing is that if I call these from those ios functions,
> mmc_host_clk_ungate() will always try to restore the clock
> even if there is really no need. Do you see this as a problem?
> 
> > Please tell us if this works!
> 
> Certainly. I'll try this overnight and see whether it works.

The device survived overnight reboot loop test, so this scheme seems to
work.

I'll prepare a new series which uses mmc_host_clk_{ungate|gate}().

  reply	other threads:[~2011-08-18 10:34 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-15 10:03 [PATCH 1/2] mmc: add functions to enable/disable aggressive clock gating Mika Westerberg
2011-08-15 10:03 ` [PATCH 2/2] mmc: prevent aggressive clock gating to race with ios updates Mika Westerberg
2011-08-17  7:56   ` Linus Walleij
2011-08-17  5:59 ` [PATCH 1/2] mmc: add functions to enable/disable aggressive clock gating Mika Westerberg
2011-08-17  7:51 ` Linus Walleij
2011-08-17 12:19   ` Mika Westerberg
2011-08-18 10:34     ` Mika Westerberg [this message]
2011-08-18 11:11       ` Andy Shevchenko
2011-08-18 11:33         ` Mika Westerberg

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=20110818103441.GX16790@intel.com \
    --to=mika.westerberg@linux.intel.com \
    --cc=cjb@laptop.org \
    --cc=linus.walleij@linaro.org \
    --cc=linux-kernel@vger.kernel.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