public inbox for linux-omap@vger.kernel.org
 help / color / mirror / Atom feed
From: Anderson Briglia <anderson.briglia@indt.org.br>
To: ext Tony Lindgren <tony@atomide.com>
Cc: "Linux-omap-open-source@linux.omap.com"
	<linux-omap-open-source@linux.omap.com>
Subject: Re: [PATCH] OMAP: Add OMAP_GPIO_SWITCH dependency for TUSB6010 on N800
Date: Mon, 22 Oct 2007 12:07:10 -0400	[thread overview]
Message-ID: <471CCAAE.6040205@indt.org.br> (raw)
In-Reply-To: <20071022000622.GD6984@atomide.com>

ext Tony Lindgren wrote:
> Hi,
> 
> * Anderson Briglia <anderson.briglia@indt.org.br> [071016 15:00]:
>> GPIO switch is needed for TUSB6010 code. It must be
>> selected when TUSB6010 is marked on N800 device.
>>
>> Signed-off-by: Anderson Briglia <anderson.briglia@indt.org.br>
>> ---
>>  arch/arm/mach-omap2/Kconfig |    1 +
>>  1 files changed, 1 insertions(+), 0 deletions(-)
>>
>> diff --git a/arch/arm/mach-omap2/Kconfig b/arch/arm/mach-omap2/Kconfig
>> index 51fc13a..9323bd0 100644
>> --- a/arch/arm/mach-omap2/Kconfig
>> +++ b/arch/arm/mach-omap2/Kconfig
>> @@ -37,6 +37,7 @@ config MACH_NOKIA_N800
>>  	select CBUS if VIDEO_TCM825X
>>  	select CBUS_RETU if VIDEO_TCM825X
>>  	select MENELAUS if VIDEO_TCM825X
>> +	select OMAP_GPIO_SWITCH
>>
>>  config MACH_OMAP2_TUSB6010
>>  	bool
> 
> At least the comment is wrong, can you please check? There's not
> gpio_switch dependency in tusb6010 code AFAIK.

Yes, you're right. I'm re-sending with another comment.

> 
> Tony
> 

  reply	other threads:[~2007-10-22 16:07 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-16 21:58 [PATCH] OMAP: Add OMAP_GPIO_SWITCH dependency for TUSB6010 on N800 Anderson Briglia
2007-10-22  0:06 ` Tony Lindgren
2007-10-22 16:07   ` Anderson Briglia [this message]
2007-11-21 15:06 ` [PATCH] OMAP: Moving TWL id for i2c in board files Chandra shekhar
2007-11-23 21:20   ` Tony Lindgren

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=471CCAAE.6040205@indt.org.br \
    --to=anderson.briglia@indt.org.br \
    --cc=linux-omap-open-source@linux.omap.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox