[PATCH 3/5] USB: add clk structure for systems that support clkdev framework

saeed bishara saeed.bishara at gmail.com
Sun May 2 11:54:15 EDT 2010


>> well, I think that those drivers that have more than one clk can be
>> redesigned by adding virtual clk for the the usb host, and the clk
>> implementation for that soc should manage all the underlying physical
>> clocks. I've looked at the omap,at91 and atmel, and it looks to me
>> that this is doable. you see can see that the clk stuff in those
>> driver has nothing to do with usb itself. what do you think?
>
> Not happy with this for two reasons:
> 1. You're assuming that they can be managed as one entity; that doesn't seem
>   true for some of the drivers.
can you please give an example?

saeed



More information about the linux-arm-kernel mailing list