From: Linus Walleij <linus.walleij@stericsson.com>
To: Philip Rakity <prakity@marvell.com>
Cc: Nicolas Pitre <nico@fluxnic.net>,
Ohad Ben-Cohen <ohad@wizery.com>,
"linux-mmc@vger.kernel.org" <linux-mmc@vger.kernel.org>
Subject: Re: [PATCH] mmc: agressive clocking framework v9
Date: Mon, 8 Nov 2010 10:40:22 +0100 [thread overview]
Message-ID: <4CD7C586.6020809@stericsson.com> (raw)
In-Reply-To: <AD7183BC-A6C0-4283-BC89-0CC5111437D7@marvell.com>
Philip Rakity wrote:
> I am concerned that having the core/ layer ask for clocks off and on is
>
> a) not needed when h/w clock gating is enabled
> b) may invoke bad behavior in the controller
> c) is not optimal since the h/w is already handling this.
So do not CONFIG_MMC_CLKGATE for this platform?
I don't quite get it I think...
Yours,
Linus Walleij
next prev parent reply other threads:[~2010-11-08 9:40 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-06 5:38 [PATCH] mmc: agressive clocking framework v9 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 [this message]
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
-- strict thread matches above, loose matches on Subject: below --
2010-11-04 11:16 Linus Walleij
2010-11-04 13:15 ` David Vrabel
2010-11-04 14:25 ` Linus Walleij
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
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=4CD7C586.6020809@stericsson.com \
--to=linus.walleij@stericsson.com \
--cc=linux-mmc@vger.kernel.org \
--cc=nico@fluxnic.net \
--cc=ohad@wizery.com \
--cc=prakity@marvell.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