On 14 May 2013 19:13, Mike Turquette [off-list ref] wrote:
Quoting James Hogan (2013-04-19 09:28:23)
quoted
Add core support to allow clock implementations to select the best
parent clock when rounding a rate, e.g. the one which can provide the
closest clock rate to that requested. This is by way of adding a new
clock op, determine_rate(), which is like round_rate() but has an extra
parameter to allow the clock implementation to optionally select a
different parent clock. The core then takes care of reparenting the
clock when setting the rate.
Hi James,
Can you rebase this onto -rc1? It does not apply cleanly.
Hi Mike,
Sure, I rebased onto clk-next the other day so I'll update to rc1 and
resubmit tomorrow.
Cheers
James