drm_crtc_check_viewport(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… drm_crtc_check_viewport ✨

okay so bestie, welcome to the kernel API manual β€” this one's drm_crtc_check_viewport(9), and honestly? it's giving "tiny bouncer at the door of the display pipeline." πŸŽ€ let's get into it.


🌸 NAME 🌸

drm_crtc_check_viewport β€” literally just checks that your framebuffer is big enough for the CRTC viewport. that's it. that's the whole vibe check. ✨


πŸ¦‹ SYNOPSIS πŸ¦‹

int drm_crtc_check_viewport (const struct drm_crtc *crtc , int x , int y
, const struct drm_display_mode *mode , const struct drm_framebuffer *fb
);

yeah she takes five args and returns an int, no cap. πŸ’…


πŸŽ€ ARGUMENTS πŸŽ€

  • crtc β€” the CRTC that the framebuffer is gonna be displayed on. main character energy, obviously. πŸ‘‘
  • x β€” x panning. yes, the letter. yes, lowercase. πŸ™ˆ
  • y β€” y panning. matching set with x, they're a duo. 🫢
  • mode β€” the mode that the framebuffer will be displayed under. the whole aesthetic it's being styled for. 🌈
  • fb β€” the framebuffer we're checking the size of. this is the one getting the vibe check. πŸ”₯

πŸ’œ SEE ALSO πŸ’œ

like, read those if you want the full lore. iykyk. πŸ“šβœ¨


ngl bestie, that's genuinely everything on this page β€” no extra flags, no hidden defaults, no sneaky return-value section. what you see is what you get. πŸ’€

okay that's the whole page, mwah πŸ“ β€” brought to you by the ./drivers/gpu/drm girlies, version dated October 2026, and the manual name is drm_crtc_check_viewport(9) in case you forgot already (you didn't, you're doing amazing). πŸ§šπŸ’–

πŸ“¦ where this page comes from