From: mturquette@baylibre.com (Michael Turquette)
To: linux-arm-kernel@lists.infradead.org
Subject: [Query]set clk rate must operate its coordinated clock
Date: Fri, 11 Mar 2016 08:51:52 -0800 [thread overview]
Message-ID: <20160311165152.4103.82090@quark.deferred.io> (raw)
In-Reply-To: <20160309152420.20de187a@xhacker>
Jisheng,
Quoting Jisheng Zhang (2016-03-08 23:24:20)
> Dear Stephen, Michael, Sebastian and all,
>
> I have the following clk case which I dunno the elegant solution:
>
>
> cpuclk have two parents: cpupll and refclk. When set the cpuclk freq, we
> have to set its parent's freq, I.E cpupll freq. But before changing the
> cpupll's freq, we should set its refclk as its parent firstly.
>
> AFAIK, this is a common case, I have seen such requirement in rockchip, samsung
> clk driver. They solve this by notifier, but as pointed out by Michael
> in http://lists.infradead.org/pipermail/linux-arm-kernel/2015-June/351565.html
>
> "This is also a hack and it points towards some missing infrastructure in the
> clock framework."
>
> I also don't like the notifier solution, I believe the elegant solution could
> be using the coordinated clock infrastructure. So what's the status of
> this infrastructure? I can test, and I can even add some code to make it be
> ready to be merged if you guide me ;)
Thanks for the email. I hope to finish that feature before ELC. I have
Cc'd Pi-Cheng Chen from Mediatek who is also interested in coordinated
clock rates.
Regards,
Mike
>
> Thanks in advance,
> Jisheng
next prev parent reply other threads:[~2016-03-11 16:51 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-09 7:24 [Query]set clk rate must operate its coordinated clock Jisheng Zhang
2016-03-09 7:30 ` Jisheng Zhang
2016-03-11 16:51 ` Michael Turquette [this message]
2016-03-14 8:09 ` Jisheng Zhang
2016-03-31 2:34 ` Pi-Cheng Chen
2016-06-06 8:10 ` Heiko Stübner
2016-06-13 15:59 ` Georgi Djakov
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=20160311165152.4103.82090@quark.deferred.io \
--to=mturquette@baylibre.com \
--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).