linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: paul.gortmaker@windriver.com (Paul Gortmaker)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] usb: limit OMAP related USB options to OMAP2PLUS platforms
Date: Wed, 27 Feb 2013 14:57:51 -0500	[thread overview]
Message-ID: <512E653F.1090706@windriver.com> (raw)
In-Reply-To: <20130227195046.GA2300@arwen.pp.htv.fi>

On 13-02-27 02:51 PM, Felipe Balbi wrote:
> HI,
> 
> On Wed, Feb 27, 2013 at 02:08:39PM -0500, Paul Gortmaker wrote:
>> commit 57f6ce072e35770a63be0c5d5e82f90d8da7d665 ("usb: phy:
>> add a new driver for usb3 phy") added the new Kconfig option
>> OMAP_USB3, but it had no dependencies whatsoever, and hence
>> became available across all arch/platforms.
>>
>> Which presumably caused this to show up in x86 randconfig:
>>
>>     warning: (USB_MUSB_HDRC && OMAP_USB3) selects \
>>         OMAP_CONTROL_USB which has unmet direct \
>>         dependencies (USB_SUPPORT && ARCH_OMAP2PLUS)
>>
>> Then commit 6992819feb39cb9adac72170555d957d07f869f2 ("usb: phy:
>> fix Kconfig warning") was added.  However, this just deleted the
>> ARCH_OMAP2PLUS dependency from OMAP_CONTROL_USB, further
>> compounding the problem by opening up OMAP_CONTROL_USB to
>> all arch/platforms as well.
>>
>> Here we revert the change of 6992819feb to restore the dependency,
>> and add the same ARCH_OMAP2PLUS dependency to the new OMAP_USB3.
>>
>> Perhaps a more platform specific dependency could be chosen for
>> OMAP_USB3, but at least this keeps it from bleeding out to other
>> architectures and non-OMAP ARM platforms as it is currently doing.
>>
>> Cc: Felipe Balbi <balbi@ti.com>
>> Cc: Kishon Vijay Abraham I <kishon@ti.com>
>> Cc: Moiz Sonasath <m-sonasath@ti.com>
>> Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
>> Signed-off-by: Paul Gortmaker <paul.gortmaker@windriver.com>
>> ---
>>  drivers/usb/phy/Kconfig | 2 ++
>>  1 file changed, 2 insertions(+)
>>
>> diff --git a/drivers/usb/phy/Kconfig b/drivers/usb/phy/Kconfig
>> index 65217a5..40b8463 100644
>> --- a/drivers/usb/phy/Kconfig
>> +++ b/drivers/usb/phy/Kconfig
>> @@ -17,6 +17,7 @@ config OMAP_USB2
>>  
>>  config OMAP_USB3
>>  	tristate "OMAP USB3 PHY Driver"
>> +	depends on ARCH_OMAP2PLUS
>>  	select USB_OTG_UTILS
>>  	select OMAP_CONTROL_USB
>>  	help
>> @@ -27,6 +28,7 @@ config OMAP_USB3
>>  
>>  config OMAP_CONTROL_USB
>>  	tristate "OMAP CONTROL USB Driver"
>> +	depends on ARCH_OMAP2PLUS
> 
> I rather not add dependencies here and fix the selections of
> OMAP_CONTROL_USB.

I am not sure I understand what you mean, or why you wouldn't
want sane dependencies in place like those given above.  Perhaps
you can send an alternate patch so there is no ambiguity?

Paul.


> 

  reply	other threads:[~2013-02-27 19:57 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-27 19:08 [PATCH] usb: limit OMAP related USB options to OMAP2PLUS platforms Paul Gortmaker
2013-02-27 19:51 ` Felipe Balbi
2013-02-27 19:57   ` Paul Gortmaker [this message]
2013-03-14 15:17     ` Paul Gortmaker
2013-03-14 16:12       ` Felipe Balbi
2013-03-14 18:40         ` Paul Gortmaker

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=512E653F.1090706@windriver.com \
    --to=paul.gortmaker@windriver.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    /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;
as well as URLs for NNTP newsgroup(s).