Thread (5 messages) 5 messages, 4 authors, 2014-03-11

[PATCH 3/9] Doc/DT: Add DT binding documentation for DVI Connector

From: p.zabel@pengutronix.de (Philipp Zabel)
Date: 2014-03-11 11:19:00
Also in: dri-devel, linux-devicetree, linux-fbdev

Possibly related (same subject, not in this thread)

Am Dienstag, den 11.03.2014, 10:04 +0200 schrieb Tomi Valkeinen:
On 11/03/14 10:00, Geert Uytterhoeven wrote:
quoted
On Tue, Mar 11, 2014 at 7:39 AM, Tomi Valkeinen [off-list ref] wrote:
quoted
On 10/03/14 23:45, Rob Herring wrote:
quoted
I like this proposal over the others. Although, would dual link be a
I don't like inferring the information. With the above, you can't find
out that the DVI connector has digital and analog support before all the
drivers are loaded.
quoted
single endpoint or 2 endpoints? How would you differentiate that?
Hmm, well endpoints for a single port are exclusive. So it's either a
single port and a single endpoint, or two ports and two endpoints. I
think dual link has to be single port & endpoint, as the TMDS links need
to be driven together as a single bus.

And dual-link is not really "two links". DVI dual-link means 1 clock
lane and 6 data lanes, compared to 1 clock lane and 3 data lanes for
single-link.
What about having a property for the number of data lanes?
That was already suggested by Philipp in this thread. I don't see
anything wrong with that, but I don't really see benefit either.
"dual-link" is a standard term for 6 data lanes for the DVI connector.
And the choices are 3 or 6 data lanes, nothing else.
The number of lanes of a DisplayPort connector could be 1 to 4. Also,
there's dual-mode DP which can use four lanes to drive
somewhat-like-HDMI single link TMDS signals.

regards
Philipp
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help