On Wed, Mar 21, 2012 at 4:34 PM, Andrew Lunn <and...@lunn.ch> wrote: > On Wed, Mar 21, 2012 at 04:21:45PM +0800, Haojian Zhuang wrote: >> On Wed, Mar 21, 2012 at 11:54 AM, Nicolas Pitre <n...@fluxnic.net> 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. >> > >> > >> OK. We could try to rename ehci-mv to ehci-pxa. >> >> By the way, we aren't allowed to append "depends on PLAT_PXA" in Kconfig. > > Hi Hoajian > > Could you explain that a bit more? What was the reason you could not > append it? Is the driver used by some other platform as well? > > Thanks > Andrew
The driver isn't used by any other platform. It's only used in arch-pxa & arch-mmp. I can't find the original mail. But I remembered that maintainer said the driver should be built with any other platform, even with x86. So we aren't allowed to append it in Kconfig. Best Regards Haojian _______________________________________________ devicetree-discuss mailing list devicetree-discuss@lists.ozlabs.org https://lists.ozlabs.org/listinfo/devicetree-discuss
