On Thursday 24 March 2016 12:02 AM, David Lechner wrote:

On 03/23/2016 12:29 PM, Sekhar Nori wrote:

quoted

Alright, I guess 'can be called' in the comment should have used
stronger language :) How about late registration of USB clocks as I
suggested. It should also help consolidate code across da830 and da850.

What about the new async3 clock? It will require later registration too,
but it has many children that depend on it.

I guess that was the reason why it was done the way it was. Can we leave
that alone for now (not use the new set_parent interface)? You don't
really need that to be changed for USB functionality, right?

Thanks,
sekhar