Am Mittwoch, 13. April 2016, 17:43:31 schrieb Stephen Boyd:
> On 04/12, Heiko Stuebner wrote:
> > I remember having clocks not overflow their target rate came up in some
> > ELC
> > talk last week (probably in Stephens Qualcomm-kernel-talk) and a general
> > solution might need some changes closer
On 04/12, Heiko Stuebner wrote:
>
> I remember having clocks not overflow their target rate came up in some ELC
> talk last week (probably in Stephens Qualcomm-kernel-talk) and a general
> solution might need some changes closer to the core.
Yep. It's on the list. Hopefully coordinated clk rate
Hi Finley,
Am Montag, 11. April 2016, 09:54:12 schrieb Finlye Xiao:
> From: Finley Xiao
>
> Some of Rockchip's clocks should consider the priority of .set_parent
> and .set_rate to prevent a too large temporary clock rate.
>
> For example, the gpu clock can be parented to cpll(750MHz) and
> usb
From: Finley Xiao
Some of Rockchip's clocks should consider the priority of .set_parent
and .set_rate to prevent a too large temporary clock rate.
For example, the gpu clock can be parented to cpll(750MHz) and
usbphy_480m(480MHz), 375MHz comes from cpll and the div is set
to 2, 480MHz comes from
4 matches
Mail list logo
