Raspberry Pi Display Interfaces: DSI, DPI, SPI or HDMI for a Product Design

A Raspberry Pi display connects in one of four ways: MIPI DSI through the ribbon connector, parallel RGB (DPI) on the GPIO header, SPI for small screens, or HDMI through a converter board. For a product, DSI is usually the cleanest choice from about 4 to 10 inches. DPI suits RGB panels if you can give up most of the GPIO header, SPI suits screens up to about 320 × 240, and HDMI is the quickest route to a large LVDS panel at the cost of an extra board.

Request a quote TFT LCD catalogue

Four ways to connect a display to a Raspberry PiBlock diagram. A Raspberry Pi or Compute Module drives a MIPI DSI panel through the DSI ribbon connector, or an LVDS panel through a DSI-to-LVDS bridge; a parallel RGB panel through the GPIO header using DPI, where RGB888 takes GPIO 0 to 27; a small SPI TFT through the GPIO header with an init file and the mipi-dbi-spi overlay; and an LVDS or RGB panel through an HDMI converter board.Four ways to connect a display to a Raspberry PiRaspberry Pior Compute ModuleDSI connectorFPC, 2 or 4 lanesGPIO: DPIparallel RGBGPIO: SPI4 to 5 signalsHDMImicro HDMI on Pi 4/5MIPI DSI panelneeds panel driver + initDSI-to-LVDS bridgeLVDS panelParallel RGB panelRGB888 uses GPIO 0 to 27Small SPI TFTinit file + mipi-dbi-spiHDMI converter boardto LVDS or RGBLVDS or RGB panellarger panelsPi 4: one 2-lane DSIPi 5: two 4-lane DSI/CSIBest under about 3.5 inchGreen: the panel talks to the Pi directly. Grey: an extra board or bridge chip sits in the path.
Figure: the four ways to connect a display to a Raspberry Pi. Green routes connect the panel directly; grey routes add a bridge chip or a converter board.

How to connect a display to Raspberry Pi: four routes compared

RoutePi connectorSignalsWhat the panel side needsGives up
MIPI DSI15-way 1 mm FPC on Pi 4 (2 lanes); 22-way 0.5 mm on Pi 5 (4 lanes, two ports)1 clock pair + 2 or 4 data pairsA kernel driver or overlay with the panel timing and init sequenceDriver effort; FPC pinouts differ between panels
DPI (parallel RGB)40-pin GPIO header20 GPIOs for RGB565, 28 for RGB888, including clock and syncTiming in the vc4-kms-dpi-generic overlay; an SPI init driver if the panel IC needs oneMost of the GPIO header, including the I²C, SPI and UART pins
SPISPI0 on the GPIO headerClock, data, chip select, D/C, reset, backlightThe mipi-dbi-spi overlay and a firmware file with the init commandsFrame rate on anything larger than about 320 × 240
HDMIMicro HDMI on Pi 4 and Pi 5One cableA converter board to LVDS or RGBSpace, power and another board to qualify

Raspberry Pi DSI display: lanes, connectors and drivers

The Raspberry Pi 4 Model B has one 2-lane DSI display port on a 15-way, 1 mm connector. The Pi 5 has two 4-lane MIPI transceivers on 22-way, 0.5 mm connectors, each usable for a camera or a display; an adapter cable fits older 15-way displays. A Compute Module 4 carrier exposes a 2-lane DSI0 and a 4-lane DSI1. Raspberry Pi’s drivers do not support DSI command mode, so the panel must run in video mode.

Software is the bigger job. A panel behind a simple bridge can often use the generic panel-simple driver; an integrated DSI panel needs its own driver, because its driver IC expects a manufacturer-specific init sequence. Overlays already exist for some bridges, including TI’s SN65DSI83 DSI-to-LVDS bridge. Get the init code, timing and FPC pinout from the supplier before you choose; see also our MIPI DSI interface guide.

Worked example: will the panel fit in two lanes? Per-lane bit rate = pixel clock × bits per pixel ÷ lanes. A 720 × 1280 panel at 60 Hz, with assumed totals of 800 × 1320, needs 63.36 MHz × 24 = 1,521 Mbit/s, about 760 Mbit/s per lane on two lanes. A 1200 × 1920 panel, with assumed totals of 1300 × 1960, needs 152.9 MHz × 24 = 3,669 Mbit/s: about 1,835 Mbit/s per lane on two lanes, well above the 1 Gbit/s of the original D-PHY specification, or 917 Mbit/s on four. That is why Raspberry Pi says its 10-inch 1200 × 1920 Touch Display 2 needs four lanes. Use real totals from the datasheet or the pixel clock calculator.

Our MIPI references include STFT397D (3.97 inch, 480 × 800, capacitive touch), S400MB1ZS-01F2 (4 inch square, 720 × 720, capacitive touch), STFT50-01D (5 inch, 800 × 480, MIPI + RGB, capacitive touch), S550MEKI-01 (5.5 inch, 720 × 1280) and STFT1010D (10.1 inch, 800 × 1280, capacitive touch). Each needs an adapter FPC or a matching connector on the carrier board, plus a device-tree overlay with its init sequence.

DPI: parallel RGB panels on the GPIO header

DPI drives a parallel RGB panel from the 40-pin header. Raspberry Pi’s DPI white paper lists RGB565 on GPIO 0 to 19, an RGB666 mode on GPIO 0 to 9, 12 to 17 and 20 to 25, and RGB888 on GPIO 0 to 27, which is every GPIO on the header. GPIO 2 and 3 carry I²C and 14 and 15 the UART, so the touch controller, sensors and debug port must fit around the RGB bus. That usually decides whether DPI is viable.

A simple panel needs only timing in the vc4-kms-dpi-generic overlay: active size, porches, sync widths, pixel clock and polarities. A panel that needs SPI commands at power-up needs a small panel driver; one board in the white paper bit-bangs that SPI with spi-gpio. RGB candidates from our catalogue are S430MBWS-01 (4.3 inch, 800 × 480), S500MIWI-04 (5 inch, 800 × 480), S700MIWN-18-W (7 inch, 800 × 480) and S700MI2XE-02 (7 inch, 1024 × 600).

Raspberry Pi SPI display: simple wiring, limited frame rate

An SPI panel needs clock, data, chip select, data/command, reset and a backlight pin. Raspberry Pi kernels drive MIPI DBI-style SPI panels with the mipi-dbi-spi overlay and the panel-mipi-dbi driver, which loads the init commands from a firmware file in /lib/firmware. It supports 16-bit RGB565 and an 18-bit format sent as three bytes per pixel.

Bandwidth is the limit. At the 48 MHz used in one Raspberry Pi kernel issue, ignoring command overhead:

ResolutionBits per frame (16-bit colour)Best case at 48 MHz
240 × 240921,600about 52 frames/s
320 × 2401,228,800about 39 frames/s
320 × 4802,457,600about 19.5 frames/s

Three bytes per pixel cuts these figures by a third. That is fine for menus and status screens, not for video. SPI references include STFT154D (1.54 inch, 240 × 240) and S177MEHS-04 (1.77 inch, 128 × 160); their driver ICs are compared in ILI9341 vs ST7789 vs ILI9488.

Raspberry Pi HDMI display: a converter board in the middle

The Pi 4 has two micro HDMI ports up to 4Kp60, and the Pi 5 has dual 4Kp60 outputs. Most of our larger TFTs, from 7 to 12.8 inches, are LVDS, so a Raspberry Pi HDMI display usually means an LVDS or RGB panel plus a converter board. No Linux panel driver is needed, which makes it the fastest way to a working large screen.

The cost is a second board, its power rail, extra cables and one more part to track for lifecycle. For a 7- to 12-inch LVDS panel in a product, a DSI-to-LVDS bridge on the carrier board is often tidier. Our LVDS references include S700MB1XH-09 (7 inch, 1024 × 600), S800MEKH-01 (8 inch), S10MB1XH-07C0 (10.1 inch, 1024 × 600, capacitive touch) and S10MHYH-02 (12.1 inch, 1280 × 800).

Touch on a Raspberry Pi display

Raspberry Pi’s Touch Display 2 carries touch over the DSI connector. Third-party panels usually put an I²C touch controller on the panel FPC and declare it in the overlay; one overlay in the Raspberry Pi kernel declares a Goodix GT9271 at 0x5D, with options to invert or swap the axes. On a DPI design the I²C pins may already belong to the RGB bus. Our S35001D, for example, pairs RGB + SPI video with an FT5446 touch controller on I²C, so on a Pi it needs DPI plus a free I²C bus.

Choosing a route for a product

  • Pick the board first. A Pi 4 has one 2-lane DSI port; a Pi 5 or a Compute Module carrier gives you 4 lanes. Raspberry Pi states the Pi 5 will stay in production until at least January 2036; check the current statement for your board.
  • Count GPIOs before choosing DPI. With I²C sensors, a UART and SPI peripherals, 24-bit DPI will not fit.
  • For DSI, budget time for the init sequence and a tested overlay.
  • Use HDMI when time to market matters more than board count, for example in a pilot run.
  • Check the panel’s lifecycle as well as the Pi’s; see component obsolescence in LCD and TFT displays.

Raspberry Pi display FAQs

How do I connect a display to a Raspberry Pi?

Through the DSI ribbon connector (MIPI DSI panels, with a kernel overlay and init sequence), the GPIO header (parallel RGB via DPI, or small SPI panels), or HDMI with a converter board. For a product, DSI is usually the cleanest choice from about 4 to 10 inches.

Can a Raspberry Pi Pico run a display?

Yes, small ones, usually over SPI. Memory is the limit: a 16-bit frame buffer for 240 x 240 is 115,200 bytes and fits easily in the 264 kB of an RP2040, while 320 x 480 needs 307,200 bytes, which fits only in the 520 kB of an RP2350 or with partial-screen rendering.

Will a 10-inch 1200 x 1920 DSI display work on a Raspberry Pi 4?

Not on the standard Pi 4 connector. Raspberry Pi says its 10-inch 1200 x 1920 Touch Display 2 needs four DSI lanes, and the Pi 4 Model B has two. Use a Raspberry Pi 5 or the 4-lane DSI1 port on a Compute Module 4 carrier.

Can I use any MIPI DSI panel with a Raspberry Pi?

Only if it runs in video mode and you have its init sequence and timing, because Raspberry Pi drivers do not support command mode. Most integrated DSI panels also need a driver for their driver IC and an adapter for the FPC pinout.

Putting a display on a Raspberry Pi or Compute Module product? Tell us the board, the size and resolution, the GPIOs the rest of the design needs and whether you want touch. We will suggest a DSI, RGB, SPI or LVDS reference and what it needs on the Pi side. Browse the TFT LCD module catalogue, or ask about a Raspberry Pi display.

Scroll to Top
Get a QuoteWhatsApp