From: Tomi Valkeinen <tomi.valkeinen@ti.com>
To: mythripk@ti.com
Cc: linux-omap@vger.kernel.org
Subject: Re: [PATCH v2 1/3] OMAPDSS: HDMI: HPD support in boardfile
Date: Tue, 10 Jan 2012 09:43:20 +0200 [thread overview]
Message-ID: <1326181400.1939.42.camel@deskari> (raw)
In-Reply-To: <1326181045.1939.38.camel@deskari>
[-- Attachment #1: Type: text/plain, Size: 756 bytes --]
On Tue, 2012-01-10 at 09:37 +0200, Tomi Valkeinen wrote:
> I still think we should try to fix the bug at hand, not try to implement
> proper HPD support. Was there something wrong with the example patch I
> gave? (other than it needs some splitting up).
And one reason I'm saying we shouldn't try to implement HPD properly is
that with device tree the handling of the GPIOs will change, and if you
now make the driver handle the HPD in the generic hdmi layer, it may
well be that with dev tree it will change (I'm not sure yet how the
GPIOs will be managed there, but most likely they will be passed to the
IP driver).
So I think we should make the simplest possible implementation to handle
the PHY bug, inside the IP driver.
Tomi
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
prev parent reply other threads:[~2012-01-10 7:43 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-06 12:44 [PATCH 0/3] OMAPDSS: HDMI: HDMI Hot-plug detect support mythripk
2012-01-06 12:44 ` [PATCH v2 1/3] OMAPDSS: HDMI: HPD support in boardfile mythripk
2012-01-06 12:44 ` [PATCH v2 2/3] OMAPDSS: HDMI: Handle HPD event in ip mythripk
2012-01-06 12:44 ` [PATCH v2 3/3] OMAPDSS: HDMI: HPD support added to HDMI driver mythripk
2012-01-10 7:58 ` Shubhrajyoti
2012-01-10 7:37 ` [PATCH v2 1/3] OMAPDSS: HDMI: HPD support in boardfile Tomi Valkeinen
2012-01-10 7:43 ` Tomi Valkeinen [this message]
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=1326181400.1939.42.camel@deskari \
--to=tomi.valkeinen@ti.com \
--cc=linux-omap@vger.kernel.org \
--cc=mythripk@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