From: Tomi Valkeinen <tomi.valkeinen@ti.com>
To: florian.vaussard@epfl.ch, Joachim Eastwood <manabian@gmail.com>
Cc: Tony Lindgren <tony@atomide.com>,
linux-omap <linux-omap@vger.kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
devicetree@vger.kernel.org
Subject: Re: [PATCH] ARM: dts: duovero-parlor: Add HDMI output
Date: Wed, 21 May 2014 11:26:10 +0300 [thread overview]
Message-ID: <537C6322.2000101@ti.com> (raw)
In-Reply-To: <537C6082.2000405@epfl.ch>
[-- Attachment #1: Type: text/plain, Size: 1005 bytes --]
On 21/05/14 11:14, Florian Vaussard wrote:
>> I think Parlor has one and the "hdmi-connector" binding now supports
>> it. See Tomi's 3.16/fbdev-omap branch.
>>
>
> Looking into the details, the HPD pin of the parlor board is connected
> to the OMAP4 HDMI IP. The LINK_CONNECT and LINK_DISCONNECT events are
> managed by hdmi_irq_handler() in hdmi4.c to turn on/off the PHY's power.
> So there is no need to use the hgp-gpios binding of "hdmi-connector"
> IMHO. Correct me if I am wrong, as the public TRM is pretty thin
> regarding the OMAP4 HDMI IP.
The PHY's link-connect and disconnect are a separate thing, not really
related to the HPD.
The hdmi_hpd pin on OMAP should be configured to GPIO mode, and the GPIO
should be handled by the hdmi-connector.
The HDMI driver doesn't have support for the HDMI IP's HPD, and if I
recall right, the HDMI IP's HPD was not without problems. And afaik it
doesn't really bring anything, a normal GPIO does the job just fine.
Tomi
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
WARNING: multiple messages have this Message-ID (diff)
From: tomi.valkeinen@ti.com (Tomi Valkeinen)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: dts: duovero-parlor: Add HDMI output
Date: Wed, 21 May 2014 11:26:10 +0300 [thread overview]
Message-ID: <537C6322.2000101@ti.com> (raw)
In-Reply-To: <537C6082.2000405@epfl.ch>
On 21/05/14 11:14, Florian Vaussard wrote:
>> I think Parlor has one and the "hdmi-connector" binding now supports
>> it. See Tomi's 3.16/fbdev-omap branch.
>>
>
> Looking into the details, the HPD pin of the parlor board is connected
> to the OMAP4 HDMI IP. The LINK_CONNECT and LINK_DISCONNECT events are
> managed by hdmi_irq_handler() in hdmi4.c to turn on/off the PHY's power.
> So there is no need to use the hgp-gpios binding of "hdmi-connector"
> IMHO. Correct me if I am wrong, as the public TRM is pretty thin
> regarding the OMAP4 HDMI IP.
The PHY's link-connect and disconnect are a separate thing, not really
related to the HPD.
The hdmi_hpd pin on OMAP should be configured to GPIO mode, and the GPIO
should be handled by the hdmi-connector.
The HDMI driver doesn't have support for the HDMI IP's HPD, and if I
recall right, the HDMI IP's HPD was not without problems. And afaik it
doesn't really bring anything, a normal GPIO does the job just fine.
Tomi
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: OpenPGP digital signature
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20140521/24220845/attachment-0001.sig>
next prev parent reply other threads:[~2014-05-21 8:26 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-20 14:25 [PATCH] ARM: dts: duovero-parlor: Add HDMI output Florian Vaussard
2014-05-20 14:25 ` Florian Vaussard
2014-05-20 14:39 ` Tony Lindgren
2014-05-20 14:39 ` Tony Lindgren
2014-05-21 6:41 ` Florian Vaussard
2014-05-21 6:41 ` Florian Vaussard
2014-05-20 18:09 ` Joachim Eastwood
2014-05-20 18:09 ` Joachim Eastwood
2014-05-21 6:43 ` Florian Vaussard
2014-05-21 6:43 ` Florian Vaussard
2014-05-21 8:14 ` Florian Vaussard
2014-05-21 8:14 ` Florian Vaussard
2014-05-21 8:26 ` Tomi Valkeinen [this message]
2014-05-21 8:26 ` Tomi Valkeinen
2014-05-21 9:04 ` Florian Vaussard
2014-05-21 9:04 ` Florian Vaussard
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=537C6322.2000101@ti.com \
--to=tomi.valkeinen@ti.com \
--cc=devicetree@vger.kernel.org \
--cc=florian.vaussard@epfl.ch \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-omap@vger.kernel.org \
--cc=manabian@gmail.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.