From: Arnd Bergmann <arnd@arndb.de>
To: Roger Quadros <rogerq@ti.com>
Cc: "Adrien Vergé" <adrienverge@gmail.com>,
"Greg Kroah-Hartman" <gregkh@linuxfoundation.org>,
"Alan Stern" <stern@rowland.harvard.edu>,
"Florian Fainelli" <florian@openwrt.org>,
"Manjunath Goudar" <manjunath.goudar@linaro.org>,
linux-usb@vger.kernel.org, linux-kernel@vger.kernel.org,
"Yannick Brosseau" <yannick.brosseau@gmail.com>,
"Balbi, Felipe" <balbi@ti.com>
Subject: Re: [PATCH] ARM: OMAP4: USB_EHCI_HCD needs USB_PHY and NOP_USB_XCEIV
Date: Tue, 28 May 2013 10:40:38 +0200 [thread overview]
Message-ID: <2720824.63SknuJcmD@wuerfel> (raw)
In-Reply-To: <51A4676D.9010404@ti.com>
On Tuesday 28 May 2013 11:14:37 Roger Quadros wrote:
> >> depends on USB_ARCH_HAS_EHCI
> >> + select USB_PHY if ARCH_OMAP4
> >> + select NOP_USB_XCEIV if ARCH_OMAP4
> >> ---help---
> >> The Enhanced Host Controller Interface (EHCI) is standard for USB 2.0
> >> "high speed" (480 Mbit/sec, 60 Mbyte/sec) host controller hardware.
> >
> > 'select'ing USB_PHY sounds wrong too, I think you mean 'depends on'.
> >
> > Also note that Roger Quadros has just removed the 'select NOP_USB_XCEIV'
> > there, I think you should coordinate with him.
>
> 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.
My preferred option would be to turn the 'menuconfig PHY' into 'menu',
which is what we did to solve a similar problem in drivers/mfd: It lets
us 'select' specific PHY drivers without turning on the entire
menu. Using 'select PHY' has the nasty side-effect of creating an
incorrect dependency between the OMAP EHCI driver and all the
non-OMAP phy drivers that become visible once the usb-phy directory
gets enabled.
Arnd
next prev parent reply other threads:[~2013-05-28 8:40 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CANsc=4W7ZVuCoimeALsv6xEQAURYc=QYsCvXd_kZD-A52aTL5w@mail.gmail.com>
2013-05-25 4:43 ` Adrien Vergé
2013-05-27 18:23 ` Arnd Bergmann
2013-05-28 8:14 ` Roger Quadros
2013-05-28 8:40 ` Arnd Bergmann [this message]
2013-05-28 9:17 ` Roger Quadros
2013-05-28 13:30 ` Adrien Vergé
2013-05-28 14:34 ` Roger Quadros
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=2720824.63SknuJcmD@wuerfel \
--to=arnd@arndb.de \
--cc=adrienverge@gmail.com \
--cc=balbi@ti.com \
--cc=florian@openwrt.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=manjunath.goudar@linaro.org \
--cc=rogerq@ti.com \
--cc=stern@rowland.harvard.edu \
--cc=yannick.brosseau@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome