DRM_CAP_CRTC...VBLANK_EVENT(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… DRM_CAP_CRTC...VBLANK_EVENT(9) πŸ’…

okay bestie, so this is a page straight out of the Kernel API Manual and honestly? it's a short one but it's lowkey iconic. let's get into it ✨


🌸 NAME 🌸

DRM_CAP_CRTC_IN_VBLANK_EVENT β€” (yes that's it, that's the whole name, the original literally just leaves it hanging with a dash and nothing after it, and we respect the mystery 🫢)


✨ SYNOPSIS ✨

DRM_CAP_CRTC_IN_VBLANK_EVENT

that's the whole vibe check. one line. no arguments, no flags, no chaos. it's giving "I said what I said" energy πŸ‘‘


πŸ¦‹ DESCRIPTION πŸ¦‹

okay so here's the actual tea β˜•

If this capability is set to 1, the kernel supports reporting the CRTC ID inside drm_event_vblank.crtc_id for the DRM_EVENT_VBLANK and DRM_EVENT_FLIP_COMPLETE events. like, it just tells you which CRTC the event came from. very demure, very mindful πŸ’…

And starting with kernel version 4.12, this capability is always set to 1. no cap, fr fr β€” from 4.12 onward you don't even gotta worry about it, it's just on. periodt. πŸŽ€


🌈 SEE ALSO 🌈

okay this is the part where the original page absolutely goes OFF with the cross-references, so buckle up bestie, we're listing every single one πŸ§šπŸ’–

like, that's a whole friend group right there πŸ’€πŸ«Ά go read them, they're all gonna make sense together, iykyk.


πŸŽ€ the little sign-off πŸŽ€

okay that's the page!! source file lived at ./tools/perf/trace/beauty/incl... (yes it's truncated, that's how it showed up, we don't gatekeep πŸ“), and this whole thing is dated October 2026 🌸

slay, you read the whole thing, main character energy fr fr πŸ‘‘πŸ’– bye bestie!! πŸ’œβœ¨

πŸ“¦ where this page comes from