>> 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 -- To unsubscribe from this list: send the line "unsubscribe linux-usb" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
