LVDS vs MIPI-DSI: Choosing the Right Display Interface

LVDS and MIPI DSI are the two serial interfaces most industrial display projects choose between, and they differ in ecosystem as much as in electrical behaviour. This page covers the two-way comparison: how each carries the image, how the bandwidth maths works out, and where each family fits. For the wider decision across RGB, SPI, MCU, LVDS, MIPI DSI, eDP and HDMI, arranged by resolution, cable length and volume, see Choosing a TFT Display Interface.

Part of the Interfaces, Touch & Signal Integrity guide — 41 articles on RGB, SPI, LVDS, MIPI, eDP and the touch controller.

How each interface carries the image

LVDS serialises pixel data onto low-voltage differential pairs with a separate clock, traditionally one or two links depending on resolution and colour depth. MIPI DSI is a packet-based, lane-scalable interface developed from the mobile ecosystem, carrying video and control commands with its own protocol and a low-power mode.

The practical consequence is that LVDS is simple, well documented and widely supported on industrial hosts and FPGAs, while DSI is efficient in pins and power but depends on host support and on the specification of the lane configuration.

The bandwidth maths

Both interfaces are chosen against the same figure: active pixels multiplied by refresh rate, with an allowance for blanking, multiplied by bits per colour. LVDS links are quoted in terms of their pixel clock capability per link, so high resolutions need two links or a higher clock. DSI is quoted in lanes and per-lane data rate, so the configuration is a matter of how many lanes the host supports.

Doing the calculation before choosing avoids the situation where an interface is asked to carry more than its link budget allows at the required resolution and refresh rate.

Ecosystem: hosts, drivers and supply

LVDS appears on industrial single-board computers, FPGAs and many display controller boards, with mature driver support. MIPI DSI appears on mobile and embedded processors, and on modules where pin count and power matter. Which one is available usually follows the platform choice rather than the other way round, and that is often the deciding factor in practice.

Long-term supply also differs, because the display modules built around each interface come from different parts of the panel market.

EMI, cable length and routing

Both are differential and both reject common-mode noise when the pairs are routed with consistent impedance, matched lengths and a continuous reference plane. LVDS tolerates a few metres of well-made cable and is the usual choice for machine-length runs; MIPI DSI is typically used over shorter internal connections, with serialiser links used where the run grows longer.

The failure modes are the same for both: split pairs, mismatched lengths and plane discontinuities convert common-mode noise into differential noise.

Migrating between them

Moving from one to the other means changing the host output or adding a bridge, and bridges add cost, board area and, in some cases, latency. Where the platform already provides one of the two, staying with it is usually cheaper than migrating; where the panel is fixed and the platform is not, the interface becomes a host selection criterion.

Interface specifications themselves are published by the relevant standards bodies: MIPI DSI for the mobile-derived family and HDMI.org for the consumer link, with electrical design guidance in vendor material such as TI LVDS application note. CDTech’s modules are available with both interfaces.

Where to go next

For the seven-interface comparison and the selection table by resolution, cable length and volume, read Choosing a TFT Display Interface. Related: interface checks before design freeze and when to use the RGB parallel interface.