[Libre-soc-dev] HDMI, DVI, DisplayPort on SBC (like Raspberry Pi) and on BMC

[Luke Kenneth Casson Leighton]

On Monday, January 25, 2021, Jacob Lifshay <programmerjake at gmail.com> wrote:
> We should seriously consider using DisplayPort instead of HDMI, it
supports
> nearly all the same features, can be implemented without requiring
> closed-source firmware since HDCP is optional, and supports higher
> resolutions and other more modern stuff than DVI.

this is some good research.

DVI is directly pin-compatible with HDMI, it is the broken/braindead HDCP,
transferred over the DVI wires, that "makes" it HDMI.

i have absolutely no problem with leaving out HDCP, or at least providing a
way for software implementations of it.

the problem with leaving out HDMI:
* you can't use TVs as monitors
* some TVs esp. at higher resolutions flatly refuse to communicate DVI-only

the problem with leaving out both HDMI and DVI:
* eDP is nowhere near the adoption rate

the problem with eDP:
* it'a nowhere near as ubiquitous as say LVDS, RGBTTL or even MIPI.

much as i despise MIPI it has low-power benefits for this SoC.


> DVI:
> * simple/cheap
> * patent licensing is free
> * max resolution is 1920x1200 at 60Hz, 1080p60 is supported
> * no audio
> * no variable refresh rate (though we might be able to get it to work by
> breaking the spec).

i have not confirmed it but i believe this may not be quite correct: the
I2C channel transfers EDID data just like with VGA. add that I2C channel
and i would be very surprised if it didn't just "work".

> * no high bit-depth
> * forward compatible with HDMI (can run over same HDMI physical connector,
> you can get wires-only cheap (~$5) adaptors to physical DVI-D connector
for
> old monitors).
>
> DisplayPort:
> * HDCP optional
> * patent licensing is free
> * supports >4K, high refresh rate, variable refresh rate (important for
> power-saving and games), high bit-depth (HDR and better color gamut than
> sRGB).
> * supports audio output
> * works over USB type-C
> * the modern standard for computer monitors
>
>
> So, I think we should have 1 DisplayPort output (perhaps shared with USB
> type-C) if we're licensing someone elses design, as well as 1 DVI-D over a
> HDMI connector for physical compatibility with TVs that only support HDMI
> and older monitors that only support DVI.

i agree this is sane / sensible / workable. i have no idea how to cost it
up though.

bear in mind though that SoCs are RADICALLY different from "The Average
Intel quotes mobile quotes processor" where they think 8 Amps @ 0.6 v is
"low".

power draw and raw data bandwidth for 4k monitors is MENTAL.

i found a datasheet online for DDR4 that estimated power consumption for
"high performance" (lots of FIFOs, 8x AXI4 Buses) DDR4 and it was ONE WATT.

that's insane: it's 30% of the entire power budget for the entire SoC.

we likewise have to be extremely careful about the interface selection
itself, to ensure that driving eDP (which unlike MIPI was never designed
for low-power scenarios) is not overloading the power budget.

l.


-- 
---
crowd-funded eco-conscious hardware: https://www.crowdsupply.com/eoma68