mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Felipe Balbi <balbi@ti.com>
To: Paul Bolle <pebolle@tiscali.nl>
Cc: <balbi@ti.com>, Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	<linux-usb@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] usb: gadget: remove MACH_OMAP_H4_OTG
Date: Thu, 14 Mar 2013 18:07:56 +0200	[thread overview]
Message-ID: <20130314160756.GD3001@arwen.pp.htv.fi> (raw)
In-Reply-To: <1363272657.1335.79.camel@x61.thuisdomein>

[-- Attachment #1: Type: text/plain, Size: 1659 bytes --]

On Thu, Mar 14, 2013 at 03:50:57PM +0100, Paul Bolle wrote:
> On Thu, 2013-03-14 at 16:13 +0200, Felipe Balbi wrote:
> > On Mon, Mar 11, 2013 at 09:14:41PM +0100, Paul Bolle wrote:
> > > diff --git a/drivers/usb/gadget/Kconfig b/drivers/usb/gadget/Kconfig
> > > index 5a0c541..c65b5e2 100644
> > > --- a/drivers/usb/gadget/Kconfig
> > > +++ b/drivers/usb/gadget/Kconfig
> > > @@ -194,7 +194,7 @@ config USB_FUSB300
> > >  config USB_OMAP
> > >  	tristate "OMAP USB Device Controller"
> > >  	depends on ARCH_OMAP1
> > > -	select ISP1301_OMAP if MACH_OMAP_H2 || MACH_OMAP_H3 || MACH_OMAP_H4_OTG
> > > +	select ISP1301_OMAP if MACH_OMAP_H2 || MACH_OMAP_H3
> > 
> > could you, instead, just remove the entire line ? we have an overuse of
> > select and this is one of those cases where it doesn't make sense.
> 
> Sure, but there's one problem: I need to come up with a descriptive
> summary. "Remove "select" because Felipe told it makes no sense" might

heh :-) that'd look very funny 10 years from now ;-)

> not be good enough. Any hint why you think this entire line can be
> dropped?

How about:

"An improper use of 'select' has been proliferating through a bunch of
Kconfig files, this is just one instance of such case which prevents the
particular PHY driver to be enabled as a dynamically loaded module.

Users of the omap_udc, or any other UDC, should know that PHYs need to
be enabled in order for proper functionality. Based on that, we're
dropping the entire 'select' statement which will also remove warnings
further down the line when the PHY layer re-write is finished."

Sounds good to you ?

-- 
balbi

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]

      reply	other threads:[~2013-03-14 16:08 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-11 20:14 Paul Bolle
2013-03-14 14:13 ` Felipe Balbi
2013-03-14 14:50   ` Paul Bolle
2013-03-14 16:07     ` Felipe Balbi [this message]

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=20130314160756.GD3001@arwen.pp.htv.fi \
    --to=balbi@ti.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=pebolle@tiscali.nl \
    /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

all inboxes | Powered by JetHome®