How To Support Multiple Display Controllers With Different Interfaces on One SoC
summary
Shows Linux DRM support for the AM62P SoC with two display controllers and interfaces DSI, DPI/HDMI and OLDI, comparing a single-card model vs a dual card approach (chosen for separate genpd control and parallel DRM masters). Device tree uses an assign-clock property so device manager firmware sets PLL/mux (M) for pixel and OLDI clocks. OLDI becomes its own DRM bridge; DSI enable is moved into bridge pre-enable, a change merged in 6.17 RC1 to avoid FIFO corruption. Triple-display demo (DSI, LVDS, HDMI) runs; OLDI clone mode remains WIP.
AI-written summary · about
chapters (11)
- 0:00Multi-controller display support
- 3:41DRM KMS single display
- 7:16Modeling two controllers
- 10:30Dual DRM card approach
- 12:19Shared clocks and muxes
- 13:43Reuse driver structures
- 15:58Shared interfaces and LVDS
- 23:22DSI pipeline fixes
- 26:52References and next steps
- 28:20Triple display demo
- 28:40Q&A on DSI pre-enable
related talks
42mDemystifying Linux MIPI DSI Subsystem
42mDisplay Sharing in Heterogeneous Systems Using Linux as High...
27mStandardizing Linux DRM drivers implementations by interfacing DRM Bridge as a single...
38mMainline Linux on AmLogic SoCs
46mLinux DRM: New Picture Processing API
44mA Current Overview of the DRM KMS Driver-Side APIs
29mSecure and Dynamic Hardware Partitioning Management on Heterogeneous SoC
55mI + I2C = I3C: What's in this Additional 'I'?