From: Linus Walleij <linus.walleij@stericsson.com>
To: David Vrabel <david.vrabel@csr.com>
Cc: "linux-mmc@vger.kernel.org" <linux-mmc@vger.kernel.org>,
Ghorai Sukumar <s-ghorai@ti.com>, Chris Ball <cjb@laptop.org>,
Nicolas Pitre <nico@fluxnic.net>,
Adrian Hunter <adrian.hunter@nokia.com>,
Kyungmin Park <kmpark@infradead.org>,
"jh80.chung@samsung.com" <jh80.chung@samsung.com>
Subject: Re: [PATCH] mmc: agressive clocking framework v9
Date: Thu, 4 Nov 2010 15:25:04 +0100 [thread overview]
Message-ID: <4CD2C240.8030400@stericsson.com> (raw)
In-Reply-To: <4CD2B1FF.6030708@csr.com>
David Vrabel wrote:
> Linus Walleij wrote:
>> @@ -148,14 +148,19 @@ static int mmc_runtime_suspend(struct device *dev)
>> {
>> struct mmc_card *card = mmc_dev_to_card(dev);
>>
>> + mmc_gate_clock(card->host);
>> return mmc_power_save_host(card->host);
>> }
>
> Haven't you tied the clock gating to the power on/off state of the
> card/host? This looks like the wrong thing to me. Surely we want to
> gate the clock even if the card (or SDIO functions) are active?
You're probably right :-/
Since the runtime_pm_get/put calls are balanced for the host
enable/disable case and the clock gating is orthogonal,
I need to create an orthogonal instance of hooks, maybe it's
easiest to just spawn a second dummy device like mmc0_clk
for this to be able to use the runtime PM hooks?
Back to hacking!
Yours,
Linus Walleij
next prev parent reply other threads:[~2010-11-04 14:55 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-04 11:16 [PATCH] mmc: agressive clocking framework v9 Linus Walleij
2010-11-04 13:15 ` David Vrabel
2010-11-04 14:25 ` Linus Walleij [this message]
2010-11-04 17:01 ` Nicolas Pitre
2010-11-05 8:35 ` Linus Walleij
2010-11-05 10:03 ` Ohad Ben-Cohen
2010-11-04 21:20 ` Ohad Ben-Cohen
-- strict thread matches above, loose matches on Subject: below --
2010-11-06 5:38 Philip Rakity
2010-11-06 17:24 ` Ohad Ben-Cohen
2010-11-06 17:38 ` Philip Rakity
2010-11-07 1:44 ` Nicolas Pitre
2010-11-07 18:18 ` Philip Rakity
2010-11-08 4:33 ` Nicolas Pitre
2010-11-08 9:40 ` Linus Walleij
2010-11-08 9:45 ` Philip Rakity
2010-11-09 10:29 ` Jaehoon Chung
2010-11-09 16:52 ` Linus Walleij
2010-11-07 9:32 ` Ohad Ben-Cohen
2010-11-08 9:37 ` Linus Walleij
2010-11-08 9:47 ` Philip Rakity
2010-11-08 10:40 ` Linus Walleij
2010-11-08 18:49 ` Nicolas Pitre
2010-11-08 22:06 ` Linus Walleij
2010-11-08 18:47 ` Nicolas Pitre
2010-11-08 9:23 ` Linus Walleij
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=4CD2C240.8030400@stericsson.com \
--to=linus.walleij@stericsson.com \
--cc=adrian.hunter@nokia.com \
--cc=cjb@laptop.org \
--cc=david.vrabel@csr.com \
--cc=jh80.chung@samsung.com \
--cc=kmpark@infradead.org \
--cc=linux-mmc@vger.kernel.org \
--cc=nico@fluxnic.net \
--cc=s-ghorai@ti.com \
/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