EHCI_MV confusion was: Re: kirkwood devicetree respin

[Neil Zhang]

> -----Original Message-----
> From: Alan Stern [mailto:stern at rowland.harvard.edu]
> Sent: 2012年3月22日 0:28
> To: Nicolas Pitre
> Cc: Neil Zhang; Jason Cooper; Arnd Bergmann; Andrew Lunn; Jamie Lentin; USB
> list; michael at walle.cc; devicetree-discuss at lists.ozlabs.org
> Subject: Re: EHCI_MV confusion was: Re: kirkwood devicetree respin
> 
> On Wed, 21 Mar 2012, Nicolas Pitre wrote:
> 
> > On Wed, 21 Mar 2012, Alan Stern wrote:
> >
> > > On Wed, 21 Mar 2012, Jason Cooper wrote:
> > >
> > > > On Tue, Mar 20, 2012 at 11:54:53PM -0400, Nicolas Pitre wrote:
> > > > > On Tue, 20 Mar 2012, Arnd Bergmann wrote:
> > > > >
> > > > > > ehci-orion only makes sense on PLAT_ORION, and they never have any
> > > > > > other platform ehci driver.
> > > > > >
> > > > > > ehci-mv only makese sense on PLAT_PXA, and they  also don't have any
> > > > > > other platform ehci driver.
> > > > >
> > > > > BTW, as someone who once was the active maintainer for PXA, and later
> > > > > the active maintainer for Orion, I should say that ehci-mv is a
> terribly
> > > > > bad name (as demonstrated, not all Marvell SOCs use ehci-mv) and
> > > > > confusion would be much reduced if it was renamed to ehci-pxa.
> 
> > I think there is still value in the rename.  "mv" is a really bad
> > qualifier for an IP block from a company that has many of them for the
> > same purpose.

We have submitted a patch to remove ehci-pxa168.c.
And we have plan to rename the driver name for ehci-mv.c.
Thanks.

> 
> Then you should discuss this with the driver's maintainer (CC'ed).
> 
> Alan Stern


Best Regards,
Neil Zhang