Standardizing Linux DRM drivers implementations by interfacing DRM Bridge as a single...
summary
Argues that encoder logic migrates into DRM bridges to create a single bridge API so host drivers can remove encoder ops and register one dummy encoder for userspace; demonstrates this by converting Samsung DSI/DSM drivers and examples from Mediatek/Rockchip to a common bridge implementation that drops component bind complexity. Notes API tweaks for pre-enable/post-disable ordering when chaining bridges and shows a non-upstream bridge switch prototype that routes one input to multiple outputs at runtime; prototypes work but switch isn’t yet upstream.
AI-written summary · about
chapters (6)
- 0:00Introduction to DRM Bridge
- 2:33DRM Bridge Basics
- 8:16Standardizing Bridge API
- 16:43Benefits of Standard Bridge
- 19:59Potential Bridge Enhancements
- 25:19Summary and Future Work
related talks
50mHotplug of Non-discoverable Hardware: Status and Future Directions
44mA Current Overview of the DRM KMS Driver-Side APIs
32mHow To Support Multiple Display Controllers With Different Interfaces on One SoC
42mDisplay Sharing in Heterogeneous Systems Using Linux as High...
35mIdentifying and Supporting 'X-compatible' Hardware Blocks
46mLinux DRM: New Picture Processing API
39mOverview of a Modern DRM Driver
46mDemystifying Graphics and Media Work Synchronisation