From: s.hauer@pengutronix.de (Sascha Hauer)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/2] ARM: imx6q: add pll round_rate support
Date: Thu, 15 Mar 2012 19:50:04 +0100 [thread overview]
Message-ID: <20120315185004.GD3852@pengutronix.de> (raw)
In-Reply-To: <20120315151521.GB5701@richard-laptop>
On Thu, Mar 15, 2012 at 11:15:23PM +0800, Richard Zhao wrote:
> On Thu, Mar 15, 2012 at 04:00:48PM +0100, Sascha Hauer wrote:
> > On Thu, Mar 15, 2012 at 10:46:04PM +0800, Richard Zhao wrote:
> > > On Wed, Mar 14, 2012 at 09:52:28AM +0100, Sascha Hauer wrote:
> > > > On Wed, Mar 14, 2012 at 04:22:58PM +0800, Richard Zhao wrote:
> > > > > Signed-off-by: Richard Zhao <richard.zhao@linaro.org>
> > > > > ---
> > > > >
> > > > > #define DEF_PLL(name) \
> > > > > static struct clk name = { \
> > > > > @@ -681,6 +741,7 @@ static int pll_set_rate(struct clk *clk, unsigned long rate)
> > > > > .disable = pll_disable, \
> > > > > .get_rate = name##_get_rate, \
> > > > > .set_rate = name##_set_rate, \
> > > > > + .round_rate = name##_round_rate, \
> > > >
> > > > I hope this ## stuff is gone soon with the generic clock framework. It
> > > > is so ugly and inefficient.
> > > I hope this doesn't prevent this two patches go in.
> >
> > Given that we are short from getting a generic clock framework (and I
> > think this time it's for real) and that you are not mention in any words
> > what these patches fix I don't see a reason for merging them.
> I think the cpu clock is a great challenge for generic clock framework.
> When it set_rate, it includes reparent, and change parent's parent's rate.
> I don't see any upstream code like that till now. and it's really what
> we need.
Then do a clk_set_parent, clk_set_rate and a clk_set_parent again
in your cpufreq driver. The notifying mechanism even allows you to
block any concurrent change in between these three steps if necessary.
Noone says that these three steps have to be encapsulated in a single
clk_set_rate call like you did in your patch.
>
> And it also block cpufreq from upstreaming.
Yes, and that's a good way to tell your management why you have to
invest some time into porting i.MX6 to the generic clock framework ;)
Sascha
--
Pengutronix e.K. | |
Industrial Linux Solutions | http://www.pengutronix.de/ |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
next prev parent reply other threads:[~2012-03-15 18:50 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-14 8:22 [PATCH 0/2] improve imx6q arm_clk set rate Richard Zhao
2012-03-14 8:22 ` [PATCH 1/2] ARM: imx6q: add pll round_rate support Richard Zhao
2012-03-14 8:52 ` Sascha Hauer
2012-03-15 14:46 ` Richard Zhao
2012-03-15 15:00 ` Sascha Hauer
2012-03-15 15:07 ` Shawn Guo
2012-03-15 15:15 ` Richard Zhao
2012-03-15 18:50 ` Sascha Hauer [this message]
2012-03-16 1:10 ` Richard Zhao
2012-03-17 12:28 ` Sascha Hauer
2012-03-19 1:51 ` Richard Zhao
2012-03-19 2:48 ` Shawn Guo
2012-03-19 8:31 ` Sascha Hauer
2012-03-19 1:54 ` Richard Zhao
2012-03-14 8:22 ` [PATCH 2/2] ARM: imx6q: change pll1 rate when change arm_clk rate Richard Zhao
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=20120315185004.GD3852@pengutronix.de \
--to=s.hauer@pengutronix.de \
--cc=linux-arm-kernel@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).