Which Interface Options Should You Require for an OEM TFT Display Module?
Require the interface the panel speaks natively, and choose it from your host processor: SPI or parallel RGB on small panels, MIPI DSI when the processor has DSI lanes, and LVDS or eDP on larger panels. HDMI and USB are not panel interfaces. A module that takes HDMI carries an HDMI to LVDS converter board (or one that outputs RGB or MIPI), and a USB display adds a graphics chip and a host driver. Ask for them only when the host is a PC or single-board computer with no display output you can route to the glass. SuccessLCD supplies TFT modules on all five native interfaces, for example the S550MEKI-01 (5.5 inch, 720 × 1280, MIPI DSI), the S10MB1XH-07C0 (10.1 inch, 1024 × 600, LVDS, capacitive touch) and the S60MZJW-01 (15.6 inch, 1920 × 1080, eDP).
Request a quote WhatsApp +86 134 3360 8240 TFT LCD catalogue
Start from the host, not the panel
At a given size there are only one or two panel interfaces on offer, and the host decides which you can use without extra silicon. So the first line of a display RFQ should be the processor part number and its display outputs. Common cases:
- A microcontroller with an RGB LCD peripheral, such as Espressif’s ESP32-S3, streams pixels from a frame buffer by DMA. Some RGB panels also need SPI commands at start-up.
- An application processor running Linux or Android may offer MIPI DSI, LVDS, HDMI or several of them; its reference manual says which pins carry what. Raspberry Pi boards, for example, have DSI connectors alongside HDMI; see Raspberry Pi display options.
- A PC or an x86 box may expose only HDMI or DisplayPort at its connectors. That is where converter boards come in.
If the host has two usable outputs, use the one the panels at your size already have. A bridge can translate almost anything, but it is one more part to qualify, power and keep in production.
Native interfaces by panel size in our catalogue
Interface and size go together. Our TFT references that state an interface fall out like this:
| Interface | Sizes in the catalogue | Resolutions | Example references |
|---|---|---|---|
| SPI | 1.54 to 1.77 in | 128 × 160, 240 × 240 | S177MEHS-04 |
| Parallel RGB | 1.44 to 7 in | 128 × 160 to 1024 × 600 | S430MBWS-01 (4.3 in, 800 × 480), S700MIWN-18-W |
| RGB with SPI for commands | 3.5 to 5 in | 240 × 320 to 480 × 854 | S500MHZI-01 (5 in, 480 × 854) |
| MIPI DSI | 3.97 to 10.1 in | 480 × 800 to 800 × 1280 | S550MEKI-01, STFT1010D |
| LVDS | 5 to 12.8 in | 800 × 480 to 1920 × 1080 | S10MB1XH-07C0 (10.1 in), S80MHJH-04-W (12.8 in) |
| eDP | 15.6 in | 1920 × 1080 | S60MZJW-01 |
| HDMI or USB | None as a native input | Any, through a converter | Converter board plus one of the above |
Parallel RGB stops at 7 inches. A 24-bit bus with clock, sync and data-enable lines is 28 signals, and larger panels move to differential links that carry the data on fewer wires. Nothing in the list accepts HDMI or USB directly.
eDP vs LVDS on 10 inch and larger panels
LVDS (low-voltage differential signaling) in display use means a FlatLink or FPD-Link style link: 28 bits of parallel data serialized 7:1 onto four differential pairs plus a clock pair. TI’s SN75LVDS83B, a typical transmitter, accepts pixel clocks from 10 to 135 MHz. Faster streams use dual-link LVDS: two links side by side, each running at half the pixel rate.
eDP (embedded DisplayPort) is the VESA version of DisplayPort for built-in panels. It sends packets over up to four lanes. Earlier versions fixed the rate at 1.62, 2.7 or 5.4 Gb/s per lane, eDP 1.4 added more, and the 8b/10b coding means 80 % of the line rate carries data. Since eDP 1.3 it also supports panel self refresh: the panel’s timing controller holds a static image from its own memory, so the host link can sleep.
In our catalogue the 1920 × 1080 references sit on both sides: 12.8 inches on LVDS, 15.6 inches on eDP. Choose the one your processor has, and don’t add a bridge just because eDP is newer.
Worked example: does 1920 × 1080 at 60 Hz fit one LVDS link? The standard 1080p60 timing has a pixel rate of 148.5 MHz including blanking. That is above the 135 MHz limit of a single-link transmitter such as the SN75LVDS83B, so the panel needs dual-link LVDS: 74.25 MHz per link, with each pair carrying 7 × 74.25 = 519.75 Mb/s. Over eDP the same stream at 24 bits per pixel needs 148.5 × 24 = 3.564 Gb/s. One HBR (2.7 Gb/s) lane carries 2.7 × 0.8 = 2.16 Gb/s of data, so two lanes (4.32 Gb/s) are enough. The panel datasheet says which lane count and rate it accepts.
MIPI DSI, and bridges when host and panel don’t match
MIPI DSI carries pixels and commands over one to four high-speed lanes plus a clock. In our catalogue it covers 3.97 to 10.1 inches, and the host has to have DSI on its pins. The details are in our MIPI DSI interface guide.
When the processor has DSI but the panel you need is LVDS, a bridge chip closes the gap. TI’s SN65DSI83 takes one to four DSI lanes at up to 1 Gb/s each and drives a single LVDS link at 25 to 154 MHz, enough for 1920 × 1200 at 60 Hz with reduced blanking. It needs its own 1.8 V supply and configuration registers written at start-up (TI’s DSI-TUNER tool generates the values), and it is one more part that can go end-of-life; see display component obsolescence.
HDMI to LVDS converter boards: when they make sense
HDMI carries TMDS (transition-minimized differential signaling) video, so a converter board first decodes it. A two-chip version uses an HDMI or DVI receiver such as TI’s TFP401 (up to 165 MHz, which covers 1080p60) to produce parallel RGB, then an LVDS transmitter such as the SN75LVDS83B. Single-chip HDMI to LVDS receivers, such as Lontium’s LT8619C, combine both steps. Search terms often reverse the direction, so check the block diagram before buying a board.
A converter board makes sense when the host is a PC or a single-board computer with only HDMI at the edge, when volumes are low, or when you want to swap the computer later without touching the display. It is the wrong call in battery products, where the receiver and transmitter add power, and in long-life designs, where the board is a second item to keep in production. If the processor has LVDS or DSI on its pins, route that to the panel instead.
USB displays: a graphics chip plus a driver
With DisplayLink, the common approach to USB displays, a driver on the host reads the operating system’s frame buffer, encodes the pixels and sends them over USB. A chip on the display side decodes them into its own frame buffer and outputs a standard video signal, which still has to reach the panel through a converter. The image depends on that host driver, so check what the screen has to show before the operating system loads, and whether a driver exists for your OS.
Touch is a separate link either way. A PCAP (projected capacitive) touch controller such as the FT5446 on our S35001D reports over I²C, which suits an embedded board. A PC host will expect USB, so say so in the RFQ.
What to put in the RFQ
| Item | Why it matters |
|---|---|
| Processor part number and its display outputs | Decides the native interface and whether a bridge is needed |
| Resolution, refresh rate and colour depth (18 or 24 bit) | Sets the pixel clock, the lane count and single or dual-link LVDS |
| Distance between the main board and the display | Long runs favour differential links over parallel RGB |
| Touch interface: I²C or USB | Defines the touch controller and its firmware |
| Converter board, if any, and who supplies it | Adds power, configuration and a second lifecycle to manage |
| Supply rails available at the display connector | Backlight and bridge chips need their own voltages |
Our TFT module RFQ guide covers the rest of the sheet, from brightness to cover glass.
Interface FAQs
Which interface options should I require for an OEM TFT display module?
Require the native panel interface your host can drive directly: SPI or parallel RGB on small panels, MIPI DSI if the processor has DSI lanes, and LVDS or eDP on large panels. Add HDMI or USB only through a converter board, and only when the host has no other display output.
Is an LVDS to HDMI converter the same thing as an HDMI to LVDS converter?
Searches use both names, but to drive a panel you need HDMI in from the host and LVDS out to the glass. Check the direction on the block diagram, the LVDS format the panel expects and the input timings the board accepts before ordering one.
Can I drive the RIN0+ to RIN2+ pairs of an LVDS panel straight from HDMI?
No. HDMI carries TMDS-encoded video, so a receiver such as the TFP401 first decodes it to parallel RGB, and an LVDS transmitter such as the SN75LVDS83B then serializes it onto the panel pairs. Single-chip HDMI-to-LVDS receivers do both steps in one part.
Do I need eDP for a 1920 × 1080 panel?
Not necessarily. Our 12.8-inch 1920 × 1080 reference S80MHJH-04-W uses LVDS and the 15.6-inch S60MZJW-01 uses eDP. Use whichever your host outputs, and check whether the LVDS panel expects a single or a dual link.
Not sure which interface your host can drive? Send the processor part number, the panel size and resolution, and the cable length. We will point you to the references that connect without a converter, or say which bridge the project needs. Browse the TFT LCD module catalogue, see custom TFT options, or ask about interface options.
