From: Tomi Valkeinen <tomi.valkeinen@ti.com>
To: Archit <a0393947@ti.com>
Cc: linux-omap@vger.kernel.org, linux-fbdev@vger.kernel.org,
mythripk@ti.com, archit@ti.com, x0132446@ti.com
Subject: Re: [PATCH 5/6] OMAP: 4430SDP/Panda: add HDMI HPD gpio
Date: Wed, 18 Jan 2012 06:39:49 +0000 [thread overview]
Message-ID: <1326868789.1954.0.camel@deskari> (raw)
In-Reply-To: <4F15DAFB.40203@ti.com>
[-- Attachment #1: Type: text/plain, Size: 388 bytes --]
On Wed, 2012-01-18 at 02:02 +0530, Archit wrote:
> On Tuesday 17 January 2012 06:19 PM, Tomi Valkeinen wrote:
> > Both Panda and 4430SDP use GPIO 64 as HDMI hot-plug-detect. Configure
> > this GPIO in the board files.
>
> Minor comment: the commit message says GPIO 64, and the macros use gpio
> 63. Is this done intentionally?
Thanks, it's a typo. HPD gpio is 63.
Tomi
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2012-01-18 6:39 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-17 12:48 [PATCH 0/6] OMAPDSS: HDMI PHY burnout fix Tomi Valkeinen
2012-01-17 12:48 ` [PATCH 1/6] OMAP: 4430SDP/Panda: use gpio_free_array to free HDMI gpios Tomi Valkeinen
2012-01-17 12:48 ` [PATCH 3/6] OMAPDSS: remove wrong HDMI HPD muxing Tomi Valkeinen
2012-01-17 12:49 ` [PATCH 4/6] OMAP: 4430SDP/Panda: setup HDMI GPIO muxes Tomi Valkeinen
2012-01-17 12:49 ` [PATCH 5/6] OMAP: 4430SDP/Panda: add HDMI HPD gpio Tomi Valkeinen
2012-01-17 20:44 ` Archit
2012-01-18 6:39 ` Tomi Valkeinen [this message]
2012-01-17 13:04 ` [PATCH 6/6] OMAPDSS: HDMI: PHY burnout fix Tomi Valkeinen
2012-01-20 14:49 ` [PATCH 0/6] OMAPDSS: HDMI " 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=1326868789.1954.0.camel@deskari \
--to=tomi.valkeinen@ti.com \
--cc=a0393947@ti.com \
--cc=archit@ti.com \
--cc=linux-fbdev@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=mythripk@ti.com \
--cc=x0132446@ti.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).