* [Query]set clk rate must operate its coordinated clock
2016-03-11 16:51 ` Michael Turquette
@ 2016-03-14 8:09 ` Jisheng Zhang
2016-03-31 2:34 ` Pi-Cheng Chen
2016-06-06 8:10 ` Heiko Stübner
2 siblings, 0 replies; 7+ messages in thread
From: Jisheng Zhang @ 2016-03-14 8:09 UTC (permalink / raw)
To: linux-arm-kernel
Dear Mike,
On Fri, 11 Mar 2016 08:51:52 -0800 Michael Turquette wrote:
> 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.
>
Glad to hear that. I will test the infrastructure once it's sent out.
Thanks,
Jisheng
^ permalink raw reply [flat|nested] 7+ messages in thread
* [Query]set clk rate must operate its coordinated clock
2016-03-11 16:51 ` Michael Turquette
2016-03-14 8:09 ` Jisheng Zhang
@ 2016-03-31 2:34 ` Pi-Cheng Chen
2016-06-06 8:10 ` Heiko Stübner
2 siblings, 0 replies; 7+ messages in thread
From: Pi-Cheng Chen @ 2016-03-31 2:34 UTC (permalink / raw)
To: linux-arm-kernel
+linux-mediatek list
On Sat, Mar 12, 2016 at 12:51 AM, Michael Turquette
<mturquette@baylibre.com> wrote:
> 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.
Hi Mike,
Sorry for my late response.
Glad to hear that you're still working on it.
I am ready to test it on Mediatek platform.
Looking forwards to the new clk feature.
Thanks,
Pi-Cheng
>
> Regards,
> Mike
>
>>
>> Thanks in advance,
>> Jisheng
^ permalink raw reply [flat|nested] 7+ messages in thread
* [Query]set clk rate must operate its coordinated clock
2016-03-11 16:51 ` Michael Turquette
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
2 siblings, 1 reply; 7+ messages in thread
From: Heiko Stübner @ 2016-06-06 8:10 UTC (permalink / raw)
To: linux-arm-kernel
Hi Mike,
Am Freitag, 11. M?rz 2016, 08:51:52 schrieb Michael Turquette:
> Quoting Jisheng Zhang (2016-03-08 23:24:20)
> > 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.ht
> > ml
> >
> > "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.
pulling this up again, did this materialize yet? :-)
Because it looks like on Rockchip we're getting yet another clock that needs
special handling (set_rate needs to go through the trusted-firmware, while
reading stays the same) which might profit from that as well.
Heiko
^ permalink raw reply [flat|nested] 7+ messages in thread
* [Query]set clk rate must operate its coordinated clock
2016-06-06 8:10 ` Heiko Stübner
@ 2016-06-13 15:59 ` Georgi Djakov
0 siblings, 0 replies; 7+ messages in thread
From: Georgi Djakov @ 2016-06-13 15:59 UTC (permalink / raw)
To: linux-arm-kernel
On 06/06/2016 11:10 AM, Heiko St?bner wrote:
> Hi Mike,
>
> Am Freitag, 11. M?rz 2016, 08:51:52 schrieb Michael Turquette:
>> Quoting Jisheng Zhang (2016-03-08 23:24:20)
>>> 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.ht
>>> ml
>>>
>>> "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.
>
> pulling this up again, did this materialize yet? :-)
>
> Because it looks like on Rockchip we're getting yet another clock that needs
> special handling (set_rate needs to go through the trusted-firmware, while
> reading stays the same) which might profit from that as well.
>
Hi,
I am also interested in the CCR. Hopefully Mike will post some patches on
the list soon.
Regards,
Georgi
^ permalink raw reply [flat|nested] 7+ messages in thread