Messages in this thread | | | Date | Mon, 10 Oct 2011 14:59:48 -0600 (MDT) | From | Paul Walmsley <> | Subject | Re: [PATCH 1/5 v13] arm: omap: usb: ehci and ohci hwmod structures for omap4 |
| |
Hi
On Mon, 10 Oct 2011, Munegowda, Keshava wrote:
> Here is the highlights of the change in the design of USB Host which > we can do after kernel 3.2 release; > > 1. separate the TLL changes from UHH > 2. The TLL is be a new platform driver in ./drivers/mfd > 3. the TLL platform driver will export apis for enable/disable clocks > and settings. > 3. the UHH drivers uses these APIS of TLL based on the port > configurations from board files > you don't need the TLL clocks to > be on while all the ports are in phy mode. > > please let me know your thoughts about it.
The TLL driver shouldn't be in drivers/mfd, since it's not an MFD device. The TLL driver should go somewhere under drivers/usb.
Basically, the existing OMAP USB subsystem MFD driver should create a TLL device. Then the existing Linux driver probing system can associate the TLL driver with the TLL device.
- Paul
| |