STRUCT DRM_BUS_CFG(9)

📦 version 7.3.1, in nixpkgs unstable

💖 NAME 💖

Okay so this is the manual page for struct drm_bus_cfg(9) in the Kernel API Manual — literally the bus configuration struct, bestie. It's giving “small struct, big pipeline energy.” ✨

🦋 SYNOPSIS 🦋

struct drm_bus_cfg {
    u32 format;
    u32 flags;
};

🎀 Members 🎀

  • format — the format used on this bus (one of the MEDIA_BUS_FMT_* format). Iconic field, but hands off!
⚠️ bestie, this field should not be directly modified by drivers — drm_atomic_bridge_chain_select_bus_fmts takes care of the bus format negotiation. No cap, let the negotiation girlies handle it. 💅
  • flags — the DRM_BUS_* flags used on this bus. Flag check! 🚩

🌈 Description 🌈

This structure stores the configuration of a physical bus between two components in an output pipeline — usually between two bridges, an encoder and a bridge, or a bridge and a connector. It's the bus config moment. 🦋

The bus configuration is stored in drm_bridge_state separately for the input and output buses, as seen from the point of view of each bridge. Two buses, two perspectives — main character energy on both sides. ✨

The bus configuration of a bridge output is usually identical to the configuration of the next bridge's input, but it may differ if the signals are modified between the two bridges, for instance by an inverter on the board. Plot twist: board inverter said “not today.” 😭

The input and output configurations of a bridge may differ if the bridge modifies the signals internally, for instance by performing format conversion, or modifying signals polarities. Internally doing a little format conversion glow-up, periodt. 💖

👑 SEE ALSO 👑

Kernel file: ./include/drm/drm_atomic.h

okay that's the whole page, bestie — huge cute sign-off energy to source/version ./include/drm and the October 2026 date 💖🎀✨

📦 where this page comes from