STRUCT DRM_BRIDGE_TIMINGS(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

🌸 struct drm_bridge_timings(9) 🌸

okay so bestie, welcome to the Kernel API Manual entry for struct drm_bridge_timings β€” it's the vibe-check sheet where a DRM bridge writes down all its timing requirements. literally just timing information for the bridge. that's the whole NAME. periodt. πŸ’…


✨ SYNOPSIS ✨

struct drm_bridge_timings {
    u32 input_bus_flags;
    u32 setup_time_ps;
    u32 hold_time_ps;
    bool dual_link;
 };

like, that's the whole struct. four members, no drama, all iconic. πŸŽ€


πŸ¦‹ Members πŸ¦‹

  • input_bus_flags β€” this one tells you what extra settings the bridge needs for the pixel data on the bus, the little extras like pixel signal polarity, y'know? it's giving "custom order, please respect it". also see drm_display_info->bus_flags if you wanna go deeper. πŸ‘€
  • setup_time_ps β€” defines the time in picoseconds that the input data lines must be stable before the clock edge. so like, data has to show up early and chill there. no last-minute arrivals, bestie, that's not the vibe. ⏰
  • hold_time_ps β€” defines the time in picoseconds the bridge takes to sample the input signal after the clock edge. so the data has to stick around for a sec after, too. both of y'all stay. 🫢
  • dual_link β€” true if the bus operates in dual-link mode. and the exact meaning? lowkey depends on the bus type, so don't @ me. for LVDS buses specifically, this indicates that even- and odd-numbered pixels are received on separate links. two links, two lanes of pixels, main character energy for both. πŸ”₯
ngl, if you're setting these values, get them right β€” timing fields are not the place to be guessing. the manpage says it, so say it with me: facts only. πŸ’€

🌈 SEE ALSO 🌈

kernel file ./include/drm/drm_bridge.h πŸ“ β€” and the whole friend group:


and that's the whole page, bestie! πŸŽ€ sourced straight from ./include/drm, dated October 2026 β€” same struct drm_bridge_timings(9) energy from top to bottom. go forth and time those bridges correctly. iykyk πŸ’œπŸ¦‹βœ¨

πŸ“¦ where this page comes from