public inbox for linux-omap@vger.kernel.org
 help / color / mirror / Atom feed
From: Nishanth Menon <nm@ti.com>
To: Kevin Hilman <khilman@ti.com>
Cc: Koen Kooi <koen@dominion.thruhere.net>,
	Brad Parker <brad@heeltoe.com>, Anand Gadiyar <gadiyar@ti.com>,
	Ming Lei <tom.leiming@gmail.com>,
	Benoit Cousson <b-cousson@ti.com>,
	Stephen Rothwell <sfr@canb.auug.org.au>,
	Paul Walmsley <paul@pwsan.com>, Greg KH <greg@kroah.com>,
	linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
	Felipe Balbi <balbi@ti.com>, Tony Lindgren <tony@atomide.com>,
	linux-omap@vger.kernel.org
Subject: Re: linux-next: manual merge of the usb tree with the omap tree
Date: Thu, 06 Jan 2011 12:21:06 -0600	[thread overview]
Message-ID: <4D260812.3010605@ti.com> (raw)
In-Reply-To: <87pqs9vqya.fsf@ti.com>

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

Kevin Hilman had written, on 01/06/2011 12:15 PM, the following:
> Koen Kooi <koen@dominion.thruhere.net> writes:
> 
>> Op 6 jan 2011, om 16:43 heeft Brad Parker het volgende geschreven:
>>
>>> It's probably expected, but I can't get the EHCI USB port  to work
>>> on a beagle board XM (36xx) using the current omap tree.
>>>
>>> It this most likely due to these clock issues?
>> You need this patch: http://thread.gmane.org/gmane.linux.ports.arm.omap/47807/
>>
>> I'm currently too lazy to split it up like Nishant wants as I don't
>> see the point splitting for the sake of splitting.--
> 
> IMO, it doesn't need to be split up.
> 
> But it does have to fix the other comments I made on the same thread[1]
> 
> 1) add a descriptive changelog, and
> 2) Cc linux-arm-kernel

Kevin,
there are four things being done in the patch:
a) fix GPIO number for EHCI power on
b) fix GPIO number for DVI reset line
c) switch on DVI
d) switch on Camera

I have split the first 2 up. I just splitting the (c) up when I noticed 
the code is confusing - I will reply in thread to the original patch.

I apologize, but I disagree - as far as I see it, these are separate 
changes being done.

-- 
Regards,
Nishanth Menon

[-- Attachment #2: 0001-omap3-beaglexm-fix-EHCI-power-up-GPIO-dir.patch --]
[-- Type: text/x-patch, Size: 1541 bytes --]

>From c03fd107da409806ec15d508db6c7c352244a1f4 Mon Sep 17 00:00:00 2001
From: Koen Kooi <koen@beagleboard.org>
Date: Thu, 6 Jan 2011 12:08:15 -0600
Subject: [PATCH 1/2] omap3: beaglexm: fix EHCI power up GPIO dir

EHCI enable power pin is inverted (active high) in comparison
to vanilla beagle which is active low. Handle this case conditionally.

[nm@ti.com: helped split up]
Signed-off-by: Nishanth Menon <nm@ti.com>
Signed-off-by: Koen Kooi <koen@beagleboard.org>
---
 arch/arm/mach-omap2/board-omap3beagle.c |    9 ++++++++-
 1 files changed, 8 insertions(+), 1 deletions(-)

diff --git a/arch/arm/mach-omap2/board-omap3beagle.c b/arch/arm/mach-omap2/board-omap3beagle.c
index 6c12760..1b5aa7a 100644
--- a/arch/arm/mach-omap2/board-omap3beagle.c
+++ b/arch/arm/mach-omap2/board-omap3beagle.c
@@ -297,9 +297,16 @@ static int beagle_twl_gpio_setup(struct device *dev,
 	gpio_request(gpio + 1, "EHCI_nOC");
 	gpio_direction_input(gpio + 1);
 
-	/* TWL4030_GPIO_MAX + 0 == ledA, EHCI nEN_USB_PWR (out, active low) */
+	/*
+	 * TWL4030_GPIO_MAX + 0 == ledA, EHCI nEN_USB_PWR (out, XM active
+	 * high / others active low)
+	 */
 	gpio_request(gpio + TWL4030_GPIO_MAX, "nEN_USB_PWR");
 	gpio_direction_output(gpio + TWL4030_GPIO_MAX, 0);
+	if (omap3_beagle_get_rev() == OMAP3BEAGLE_BOARD_XM)
+		gpio_direction_output(gpio + TWL4030_GPIO_MAX, 1);
+	else
+		gpio_direction_output(gpio + TWL4030_GPIO_MAX, 0);
 
 	/* TWL4030_GPIO_MAX + 1 == ledB, PMU_STAT (out, active low LED) */
 	gpio_leds[2].gpio = gpio + TWL4030_GPIO_MAX + 1;
-- 
1.6.3.3


[-- Attachment #3: 0002-omap3-beaglexm-fix-DVI-reset-GPIO.patch --]
[-- Type: text/x-patch, Size: 1496 bytes --]

>From d34971b71d61f3fc20e724a48dbdfe347aa53802 Mon Sep 17 00:00:00 2001
From: Koen Kooi <koen@beagleboard.org>
Date: Thu, 6 Jan 2011 12:14:00 -0600
Subject: [PATCH 2/2] omap3: beaglexm: fix DVI reset GPIO

GPIO reset line for Beagle XM is different from vanilla beagle
so we populate it as part of gpio update routine.

Signed-off-by: Nishanth Menon <nm@ti.com>
Signed-off-by: Koen Kooi <koen@beagleboard.org>
---
 arch/arm/mach-omap2/board-omap3beagle.c |    8 +++++++-
 1 files changed, 7 insertions(+), 1 deletions(-)

diff --git a/arch/arm/mach-omap2/board-omap3beagle.c b/arch/arm/mach-omap2/board-omap3beagle.c
index 1b5aa7a..d628f5e 100644
--- a/arch/arm/mach-omap2/board-omap3beagle.c
+++ b/arch/arm/mach-omap2/board-omap3beagle.c
@@ -199,7 +199,7 @@ static struct omap_dss_device beagle_dvi_device = {
 	.name = "dvi",
 	.driver_name = "generic_panel",
 	.phy.dpi.data_lines = 24,
-	.reset_gpio = 170,
+	.reset_gpio = -EINVAL,
 	.platform_enable = beagle_enable_dvi,
 	.platform_disable = beagle_disable_dvi,
 };
@@ -308,6 +308,12 @@ static int beagle_twl_gpio_setup(struct device *dev,
 	else
 		gpio_direction_output(gpio + TWL4030_GPIO_MAX, 0);
 
+	/* DVI reset GPIO is different between beagle revisions */
+	if (omap3_beagle_get_rev() == OMAP3BEAGLE_BOARD_XM)
+		beagle_dvi_device.reset_gpio = 129;
+	else
+		beagle_dvi_device.reset_gpio = 170;
+
 	/* TWL4030_GPIO_MAX + 1 == ledB, PMU_STAT (out, active low LED) */
 	gpio_leds[2].gpio = gpio + TWL4030_GPIO_MAX + 1;
 
-- 
1.6.3.3


  reply	other threads:[~2011-01-06 18:21 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-23  6:18 linux-next: manual merge of the usb tree with the omap tree Stephen Rothwell
2010-12-23  8:36 ` Felipe Balbi
2010-12-23 18:29 ` Cousson, Benoit
2011-01-06 15:02   ` Ming Lei
2011-01-06 15:07     ` Anand Gadiyar
2011-01-06 15:25       ` Ming Lei
2011-01-06 15:50         ` Ming Lei
2011-01-07 14:07           ` Anand Gadiyar
2011-01-07 14:15             ` Ming Lei
2011-01-07 14:39               ` Anand Gadiyar
2011-01-07 15:20                 ` Anand Gadiyar
2011-01-07 18:54                   ` Gadiyar, Anand
2011-01-07 19:24                     ` Felipe Balbi
2011-01-10 13:53                   ` Ming Lei
2011-01-10 14:09                     ` Anand Gadiyar
2011-01-06 15:43       ` Brad Parker
2011-01-06 16:59         ` Koen Kooi
2011-01-06 17:57           ` Nishanth Menon
2011-01-06 18:15           ` Kevin Hilman
2011-01-06 18:21             ` Nishanth Menon [this message]
2011-01-06 18:38               ` Kevin Hilman
2011-01-06 20:24                 ` Nishanth Menon
2011-01-06 21:29                   ` Kevin Hilman
2011-01-06 18:27             ` Paul Walmsley
  -- strict thread matches above, loose matches on Subject: below --
2011-03-02  5:58 Stephen Rothwell
2011-03-02  5:58 Stephen Rothwell
2011-03-02  5:57 Stephen Rothwell
2011-03-03  8:48 ` Felipe Balbi
2011-03-03 16:02   ` Greg KH
2011-03-03 17:39     ` Felipe Balbi
2011-03-02  5:57 Stephen Rothwell
2011-03-02  8:23 ` Felipe Balbi
2011-03-02 14:23 ` Greg KH
2011-03-03  8:18   ` Felipe Balbi
2009-11-11  8:30 Stephen Rothwell
2009-11-11 19:12 ` Tony Lindgren
2009-11-11 19:20   ` Tony Lindgren
2009-11-11 21:52     ` Stephen Rothwell

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=4D260812.3010605@ti.com \
    --to=nm@ti.com \
    --cc=b-cousson@ti.com \
    --cc=balbi@ti.com \
    --cc=brad@heeltoe.com \
    --cc=gadiyar@ti.com \
    --cc=greg@kroah.com \
    --cc=khilman@ti.com \
    --cc=koen@dominion.thruhere.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=paul@pwsan.com \
    --cc=sfr@canb.auug.org.au \
    --cc=tom.leiming@gmail.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