Bringing up an LVDS panel behind an LT9211D bridge on Android 15

Kiosk hardware rarely uses the panel the SoC vendor validated. On a recent Android 15 project the device had an LVDS panel behind a Lontium LT9211D MIPI-DSI to LVDS bridge, an ILI2510 capacitive touch controller and an inverted backlight enable, on a vendor BSP where none of it worked. Here is what mattered.

Know who owns the bridge at each boot stage

The bootloader (XBL) had already configured the bridge to show a splash screen. When the kernel driver re-initialised it from scratch, the panel went dark for seconds and sometimes never came back. The fix was to detect the bridge state XBL left behind and adopt it rather than reset it, so the hand-over from bootloader to kernel is seamless. The relevant commit title in the tree reads 'adopt the LT9211D bridge XBL left running'.

Backlight sequencing is part of the display driver

The backlight unit on this board was active-low and needed to be gated and ramped on both the on and off edges, otherwise you get a white flash at boot and a visible snap at sleep. Treat backlight timing as part of the panel's power sequence in Device Tree, not as an afterthought in the HAL.

Device Tree is the spec

• Panel timings, lane configuration and the bridge's I2C address live in Device Tree, with the power and reset GPIO sequence next to them.
• Touch (ILI2510 over I2C) gets its own node with interrupt and reset lines, and the HAL maps it to the display's size and orientation.
• Keep the overlay small and documented; the next engineer should be able to swap the panel without reading the driver.

Test the way Google tests

A display that looks fine can still fail VtsHalGraphicsComposer. Run the VTS graphics suites early against the device rather than at the end, and fix the composer HAL and kernel paths they exercise. The same project shipped Google's certified GKI boot image to satisfy VTS, which is a separate story.

What this means for your project

If you have a custom panel on a Qualcomm, Rockchip or MediaTek board and the vendor BSP does not drive it, the work is usually bounded: bridge driver, Device Tree, backlight sequencing, touch HAL and the certification tests that touch them. Send the panel datasheet and the board schematic and we can quote it as a fixed first milestone.