All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sergei Shtylyov <sshtylyov@mvista.com>
To: Hema HK <hemahk@ti.com>
Cc: linux-usb@vger.kernel.org, linux-omap@vger.kernel.org,
	Felipe Balbi <balbi@ti.com>, Tony Lindgren <tony@atomide.com>
Subject: Re: [PATCH 5/7] usb: musb: TWL6030: Selecting TWL6030_USB transceiver
Date: Wed, 08 Dec 2010 19:03:59 +0300	[thread overview]
Message-ID: <4CFFAC6F.9000808@ru.mvista.com> (raw)
In-Reply-To: <1291824130-7181-1-git-send-email-hemahk@ti.com>

Hello.

Hema HK wrote:

> Selecting the twl6030-usb for OMAP4430SDP and OMAP4 PANDA board and
> adding OMAP4 internal phy code for compilation

> Signed-off-by: Hema HK <hemahk@ti.com>
> Cc: Felipe Balbi <balbi@ti.com>
> Cc: Tony Lindgren <tony@atomide.com>
[...]

> Index: linux-2.6/drivers/usb/musb/Kconfig
> ===================================================================
> --- linux-2.6.orig/drivers/usb/musb/Kconfig
> +++ linux-2.6/drivers/usb/musb/Kconfig
> @@ -12,6 +12,7 @@ config USB_MUSB_HDRC
>  	depends on (ARM || (BF54x && !BF544) || (BF52x && !BF522 && !BF523))
>  	select NOP_USB_XCEIV if (ARCH_DAVINCI || MACH_OMAP3EVM || BLACKFIN)
>  	select TWL4030_USB if MACH_OMAP_3430SDP
> +	select TWL6030_USB if (MACH_OMAP_3430SDP || MACH_OMAP4_PANDA)

    Parens are not necessary. Though the previous code uses them...

WBR, Sergei


  reply	other threads:[~2010-12-08 16:05 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-08 16:02 [PATCH 5/7] usb: musb: TWL6030: Selecting TWL6030_USB transceiver Hema HK
2010-12-08 16:03 ` Sergei Shtylyov [this message]
     [not found]   ` <4CFFAC6F.9000808-hkdhdckH98+B+jHODAdFcQ@public.gmane.org>
2010-12-09  5:12     ` Kalliguddi, Hema
  -- strict thread matches above, loose matches on Subject: below --
2010-12-08  8:30 Hema HK
2010-12-08  0:11 Hema HK

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=4CFFAC6F.9000808@ru.mvista.com \
    --to=sshtylyov@mvista.com \
    --cc=balbi@ti.com \
    --cc=hemahk@ti.com \
    --cc=linux-omap@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=tony@atomide.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.