From: Alexander Holler <holler@ahsoftware.de>
To: Roger Quadros <rogerq@ti.com>
Cc: balbi@ti.com, Greg KH <gregkh@linuxfoundation.org>,
Alan Stern <stern@rowland.harvard.edu>,
Linux USB Mailing List <linux-usb@vger.kernel.org>,
Kernel development list <linux-kernel@vger.kernel.org>,
"linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>
Subject: Re: [PATCH] USB: ehci-omap: Select USB_PHY
Date: Thu, 11 Apr 2013 19:33:32 +0200 [thread overview]
Message-ID: <5166F3EC.8040807@ahsoftware.de> (raw)
In-Reply-To: <5166CC30.4060507@ti.com>
Am 11.04.2013 16:44, schrieb Roger Quadros:
>> Sorry, but this just will end up with many users having broken configs
>> because of disabled stuff they don't know why they have to enable them.
>> And thus with a never ending stream of questions and thus with a needed
>> FAQ entry.
>>
>
> Alexander,
>
> I agree with you that it can get difficult with users. But it is best for
> users do not disable anything they are not familiar with.
>
> As the USB_PHY option doesn't depend on anything, it is safe to select it
> from USB_EHCI_HCD_OMAP.
>
> However, the PHY drivers themselves must be selected from the board configs.
Maybe I understood something wrong, but if the OMAP USB driver requires
CONFIG_USB_PHY (or similiar), it should be selected automatically and
not just enabled in the board config.
I just had it to often, that I needed to search around why a driver
doesn't work (or even compiles), just to find out that I need to enable
some strange config option which wasn't selected automatically.
Especially with OMAPs. ;)
And this not only occured when disabling options, it often occured by
just updating the kernel. Suddenly some obscur option was needed too, it
wasn't selected automatically by make oldconfig, bang. So the argument
to not remove anything from a board config doesn't help much.
Sorry for the rant. ;)
Regards,
Alexander
next prev parent reply other threads:[~2013-04-11 17:33 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-11 9:42 [PATCH] USB: ehci-omap: Select USB_PHY Roger Quadros
2013-04-11 10:04 ` Felipe Balbi
2013-04-11 10:51 ` Roger Quadros
2013-04-11 10:55 ` Felipe Balbi
2013-04-11 12:42 ` Roger Quadros
2013-04-11 13:02 ` Alexander Holler
2013-04-11 14:44 ` Roger Quadros
2013-04-11 15:02 ` Felipe Balbi
2013-04-11 17:33 ` Alexander Holler [this message]
2013-04-11 18:29 ` Felipe Balbi
2013-04-12 0:22 ` Alexander Holler
2013-04-11 13:18 ` Roger Quadros
2013-04-11 14:34 ` Felipe Balbi
2013-04-11 14:53 ` Roger Quadros
2013-04-11 15:09 ` Felipe Balbi
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=5166F3EC.8040807@ahsoftware.de \
--to=holler@ahsoftware.de \
--cc=balbi@ti.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=rogerq@ti.com \
--cc=stern@rowland.harvard.edu \
/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