linux-omap.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Tomi Valkeinen <tomi.valkeinen@ti.com>
To: Koen Kooi <koen@dominion.thruhere.net>
Cc: tony@atomide.com, linux-omap@vger.kernel.org
Subject: Re: [PATCH] OMAP: Beagle: fix DVI GPIO request
Date: Mon, 21 May 2012 14:12:43 +0300	[thread overview]
Message-ID: <1337598763.2078.28.camel@lappyti> (raw)
In-Reply-To: <4DA41490-EF90-40A5-B3EE-E6281B4F1313@dominion.thruhere.net>

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

On Mon, 2012-05-21 at 12:59 +0200, Koen Kooi wrote:
> Op 21 mei 2012, om 11:41 heeft Tomi Valkeinen het volgende geschreven:
> 
> > Commit e813a55eb9c9bc6c8039fb16332cf43402125b30 ("OMAP: board-files:
> > remove custom PD GPIO handling for DVI output") moved TFP410 chip's
> > powerdown-gpio handling from the board files to the tfp410 driver. One
> > gpio_request_one(powerdown-gpio, ...) was mistakenly left unremoved in
> > the Beagle board file. This causes the tfp410 driver to fail to request
> > the gpio on Beagle, causing the driver to fail and thus the DVI output
> > doesn't work.
> > 
> > This patch removes the gpio_request_one() from the board file.
> > 
> > Signed-off-by: Tomi Valkeinen <tomi.valkeinen@ti.com>
> > ---
> > arch/arm/mach-omap2/board-omap3beagle.c |    3 +--
> > 1 file changed, 1 insertion(+), 2 deletions(-)
> > 
> > diff --git a/arch/arm/mach-omap2/board-omap3beagle.c b/arch/arm/mach-omap2/board-omap3beagle.c
> > index 8ede8d2..72ad1f6 100644
> > --- a/arch/arm/mach-omap2/board-omap3beagle.c
> > +++ b/arch/arm/mach-omap2/board-omap3beagle.c
> > @@ -510,9 +510,8 @@ static void __init omap3_beagle_init(void)
> > 	omap_sdrc_init(mt46h32m32lf6_sdrc_params,
> > 				  mt46h32m32lf6_sdrc_params);
> > 
> > +	/* DVI power down GPIO */
> > 	omap_mux_init_gpio(170, OMAP_PIN_INPUT);
> 
> Wouldn't it be an output rather than an input?

Indeed. Note that I didn't change the line above =).

It seems this was changed last December:

-       omap_cfg_reg(J25_34XX_GPIO170);
+       omap_mux_init_gpio(170, OMAP_PIN_INPUT);

I wonder if the mux init is even necessary. Shouldn't the bootloader set
the muxes?

 Tomi


[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 836 bytes --]

  reply	other threads:[~2012-05-21 11:12 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-21  9:41 [PATCH] OMAP: Beagle: fix DVI GPIO request Tomi Valkeinen
2012-05-21  9:41 ` Tomi Valkeinen
2012-05-21 10:59   ` Koen Kooi
2012-05-21 11:12     ` Tomi Valkeinen [this message]
2012-05-21 11:28       ` Koen Kooi
2012-05-21 11:36         ` Tomi Valkeinen
2012-05-21 16:11           ` Tony Lindgren
2012-05-21 12:56   ` Tomi Valkeinen
2012-05-21 15:52 ` Russ Dill
2012-05-21 15:55   ` Tomi Valkeinen
2012-05-21 16:01     ` Russ Dill
2012-05-21 16:02       ` Tomi Valkeinen

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=1337598763.2078.28.camel@lappyti \
    --to=tomi.valkeinen@ti.com \
    --cc=koen@dominion.thruhere.net \
    --cc=linux-omap@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 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).