[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CANsc=4W0j62vQYXdcKkdd199Jp+jsx_Xgs0n+5fM+WR00pD9Og@mail.gmail.com>
Date: Tue, 28 May 2013 09:30:20 -0400
From: Adrien Vergé <adrienverge@...il.com>
To: Roger Quadros <rogerq@...com>
Cc: Arnd Bergmann <arnd@...db.de>,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
Alan Stern <stern@...land.harvard.edu>,
Florian Fainelli <florian@...nwrt.org>,
Manjunath Goudar <manjunath.goudar@...aro.org>,
linux-usb@...r.kernel.org, linux-kernel@...r.kernel.org,
Yannick Brosseau <yannick.brosseau@...il.com>,
"Balbi, Felipe" <balbi@...com>
Subject: Re: [PATCH] ARM: OMAP4: USB_EHCI_HCD needs USB_PHY and NOP_USB_XCEIV
Dear Arnd and Roger, thank you for your answers.
2013/5/28 Roger Quadros <rogerq@...com>
> Selecting NOP_USB_XCEIV is wrong as it in turn depends on USB_PHY.
>
> I'm not for depends as it would hide USB_EHCI_HCD_OMAP in menuconfig.
> I'm for explicitly selecting both, as it makes the user's life much
> easier.
> But I'm afraid maintainers might object to that.
>
> The other option is to enable the required drivers in omap2plus_defconfig.
> http://comments.gmane.org/gmane.linux.ports.arm.omap/97899
This seems a good idea to me, since many OMAP users boot with NFS and
need USB directly working (Ethernet over USB).
> Maybe you could just resend that patch after addressing Kevin's comments?
It's sad that USB_EHCI_HCD is too instable to be added in omap2plus_defconfig.
Still, USB_PHY and NOP_USB_XCEIV are needed since v3.10 for USB
support (and harmless): should I send a patch adding those two in
omap2plus_defconfig?
Cheers,
Adrien
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists