[PATCH v3 00/12] add imx usb driver for mx28/6x

[Richard Zhao]

On Wed, Jun 06, 2012 at 09:03:50AM +0300, Felipe Balbi wrote:
> On Wed, Jun 06, 2012 at 10:27:22AM +0800, Shawn Guo wrote:
> > On Tue, Jun 05, 2012 at 06:02:13PM +0300, Felipe Balbi wrote:
> > > Hi,
> > > 
> > > On Fri, May 25, 2012 at 10:24:13AM +0800, Richard Zhao wrote:
> > > > The work is based on  ci13xxx rework done by Alexander Shishkin.
> > > > 
> > > > Status:
> > > >   - this version only support host
> > > >   - usbotg controler works at host role
> > > > 
> > > > Changes since V2:
> > > >   - Rebase to Alex's tree
> > > >   - Use regulator to control vbus power
> > > >   - Remove ARCH check in Kconfig, but add OF_DEV check.
> > > >   - Other changes according laster version comments.
> > > > 
> > > > Richard Zhao (12):
> > > >   usb: otg: add notify_connect/notify_disconnect callback
> > > >   usb: chipidea: permit driver bindings pass phy pointer
> > > >   usb: ehci-hcd: notify phy when connect change
> > > >   usb: otg: add basic mxs phy driver support
> > > >   usb: chipidea: add imx platform driver
> > > >   ARM: imx6q: correct device name of usbphy and usb controller clock
> > > >     export
> > > >   ARM: imx6q: add config-on-boot gpios
> > > >   ARM: imx6q: add usbphy clocks
> > > >   ARM: imx6q: disable usb charger detector
> > > >   ARM: dts: imx6q-sabrelite: add usb devices
> > > >   ARM: mxs: clk_register_clkdev mx28 usb clocks
> > > >   ARM: dts: imx28-evk: add usb devices
> > > 
> > > how are we going to handle these series ? drivers/usb/otg/* parts are
> > > mostly ok (I need to look deeper) but if I take drivers/usb/otg/* we
> > > will have to delay drivers/usb/chipidea I guess...
> > > 
> > > So someone would have to take the whole series ? Who will be that
> > > person? Alex, will it be you ?
> > > 
> > I'm unsure about drivers/usb part, but arch/arm part should go via
> > arm-soc tree.
> 
> Yes, sure but the whole series is very "coupled" together... Maybe
> Richard could try to split this series into things that can go through
> arm-soc with no dependency on the other part and things that depend on
> drivers/usb/*
I'm not clear. How does the ARM part depend on drivers/usb?
Shawn maybe could pick the ARM platform part. But the usb driver part
is divided into three maintainer, Balbi for otg, Alan for ehci-hcd,
Alex for Chipidea. Chipidea part depends on ehci-hcd and otg. So I
guess Greg could pick up all the driver part and Balbi, Alan and Alex
merge them back. Hope it could avoid loop dependency.

Thanks
Richard
> 
> Richard, can you do that ?
> 
> -- 
> balbi