From: Tomi Valkeinen <tomi.valkeinen@nokia.com>
To: ext Omar Ramirez Luna <omar.ramirez@ti.com>
Cc: Tony Lindgren <tony@atomide.com>,
Russell King <linux@arm.linux.org.uk>,
linux-omap@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
Yanick Saugy <yanick.saugy@heig-vd.ch>
Subject: Re: [PATCH] OMAP: ZOOM2: Change GPIO to enable LCD NEC NL8048HL11-01B on OMAP34x-II MDP
Date: Wed, 24 Nov 2010 10:47:15 +0200 [thread overview]
Message-ID: <1290588435.13243.12.camel@tubuntu> (raw)
In-Reply-To: <1290560402-2507-1-git-send-email-omar.ramirez@ti.com>
Hi,
On Tue, 2010-11-23 at 19:00 -0600, ext Omar Ramirez Luna wrote:
> From: Yanick Saugy <yanick.saugy@heig-vd.ch>
>
> The PIN which controls LCD's reset signal (VGA_nRESET/h_GPIO_96) was not
> configured as a GPIO. We had to modify the OMAP MUX, and select this PIN
> (CAM_XCLKA) as an output GPIO (OMAP_MUX_MODE4). (kernel 2.6.35)
>
> Be aware of changing this PIN will probably disable the camera, because
> it was previously configured as a camera clock.
>
> Signed-off-by: Yanick Saugy <yanick.saugy@heig-vd.ch>
> Acked-by: Tony Lindgren <tony@atomide.com>
> Signed-off-by: Omar Ramirez Luna <omar.ramirez@ti.com>
> ---
>
> I'm not sure if this patch was forgotten, hence resending. Without
> it, a blanks screen is seen on zoom2 board.
Yes, I seem to have missed this.
But I'm a bit confused. You say that this will disable camera. Is there
a camera connected to the board, and it won't work after this?
Tomi
next prev parent reply other threads:[~2010-11-24 8:47 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-24 1:00 [PATCH] OMAP: ZOOM2: Change GPIO to enable LCD NEC NL8048HL11-01B on OMAP34x-II MDP Omar Ramirez Luna
2010-11-24 8:47 ` Tomi Valkeinen [this message]
2010-11-30 23:33 ` Ramirez Luna, Omar
-- strict thread matches above, loose matches on Subject: below --
2010-09-13 12:43 LCD on Zoom2 dev board with DSS Yanick Saugy
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=1290588435.13243.12.camel@tubuntu \
--to=tomi.valkeinen@nokia.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-omap@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=omar.ramirez@ti.com \
--cc=tony@atomide.com \
--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).