drm_bus_flag...om_videomode(9)

📦 version 7.3.1, in nixpkgs unstable

💅 drm_bus_flags_from_videomode(9) ✨

okay so this is a page from the Kernel API Manual, bestie — yes, that Kernel API Manual — and we're about to get into some pixel-clock and DE-polarity extraction. stay with me, it's actually so good 🫶

🌸 NAME 🌸

drm_bus_flags_from_videomode — extract information about pixelclk and DE polarity from videomode and store it in a separate variable

like, the whole gig is: grab the pixelclk + DE polarity tea out of a videomode and park it in its own lil variable. slay 💅

🦋 SYNOPSIS 🦋

void drm_bus_flags_from_videomode (const struct videomode *vm , u32 *bus_flags );

🎀 ARGUMENTS 🎀

  • vm — the videomode structure to use. this is the source of the vibes, we're reading from it 💖
  • bus_flags — information about pixelclk, sync and DE polarity will be stored here. that's the destination, the little basket we drop everything into 🧺✨

🔥 DESCRIPTION 🔥

okay so here's what it actually does, no cap:

it sets DRM_BUS_FLAG_DE_(LOW|HIGH), DRM_BUS_FLAG_PIXDATA_DRIVE_(POS|NEG)EDGE and DISPLAY_FLAGS_SYNC_(POS|NEG)EDGE in bus_flags according to the DISPLAY_FLAGS found in vm.

that's it. that's the whole function. it reads the DISPLAY_FLAGS out of vm, and based on what it finds, it writes the matching DRM_BUS_FLAG_DE_*, DRM_BUS_FLAG_PIXDATA_DRIVE_* and DISPLAY_FLAGS_SYNC_* values into bus_flags. lowkey iconic that it's that tidy 😭👑

careful bestie — it's writing into bus_flags, so that pointer needs to be somewhere real to land. this is a store, not a vibe check 💀

🌈 SEE ALSO 🌈

the kernel file lives right here: ./drivers/gpu/drm/drm_modes.c — go say hi 👋

and here's the whole friend group, fr fr — every single one of them:

and that's the page, bestie 🎀✨ this lil gem comes from ./drivers/gpu/drm, dated October 2026 — so go forth, extract those flags, and remember: the vibe is immaculate, the facts are untouched 💜🦋

📦 where this page comes from