linux-omap.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Tony Lindgren <tony@atomide.com>
To: Yanick Saugy <yanick.saugy@heig-vd.ch>
Cc: "linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>
Subject: Re: LCD on Zoom2 dev board with DSS
Date: Thu, 16 Sep 2010 13:42:57 -0700	[thread overview]
Message-ID: <20100916204256.GN29610@atomide.com> (raw)
In-Reply-To: <1284641813.1798.589.camel@A05BPC17>

* Yanick Saugy <yanick.saugy@heig-vd.ch> [100916 05:48]:
> Hi,
> 
> I solved my problem. It appeared the PIN which controls LCD's reset
> signal (VGA_nRESET/h_GPIO_96) was not configured as a GPIO, and the
> driver tries to use it as GPIO, so the logical value was 0. We had to
> modify the OMAP MUX, and select this PIN (CAM_XCLKA) as an output GPIO
> (OMAP_MUX_MODE4).
> 
> Be aware of changing this PIN will probably disable the camera, because
> it was previously configured as a clock.
> 
> There is the patch for the LCD (diff -Naur):
> 
> --- a/arch/arm/mach-omap2/board-zoom2.c	2010-09-15 15:27:05.148399721
> +0200
> +++ b/arch/arm/mach-omap2/board-zoom2.c	2010-09-15 14:46:09.792900019
> +0200
> @@ -71,6 +71,7 @@
>  
>  #ifdef CONFIG_OMAP_MUX
>  static struct omap_board_mux board_mux[] __initdata = {
> +	OMAP3_MUX(CAM_XCLKA, OMAP_MUX_MODE4 | OMAP_PIN_OUTPUT),
>  	{ .reg_offset = OMAP_MUX_TERMINATOR },
>  };
>  #else

Please repost with proper Signed-off-by. You might want to also
Cc Tomi Valkeinen.

Regards,

Tony


  reply	other threads:[~2010-09-16 20:43 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-09-13 12:43 LCD on Zoom2 dev board with DSS Yanick Saugy
2010-09-13 12:52 ` Felipe Balbi
2010-09-16 12:56 ` Yanick Saugy
2010-09-16 20:42   ` Tony Lindgren [this message]
2010-09-21 12:21 ` [PATCH] OMAP: ZOOM2: Change GPIO to enable LCD NEC NL8048HL11-01B on OMAP34x-II MDP Yanick Saugy
2010-09-28 21:31   ` Tony Lindgren
2010-09-29  7:35   ` 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=20100916204256.GN29610@atomide.com \
    --to=tony@atomide.com \
    --cc=linux-omap@vger.kernel.org \
    --cc=yanick.saugy@heig-vd.ch \
    /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).