drm_mode_dirtyfb_ioctl(9)

okay bestie, this is drm_mode_dirtyfb_ioctl(9) from the Kernel API Manual — the page all about “flush frontbuffer rendering on an FB” 💅✨

🌸 NAME 🌸

drm_mode_dirtyfb_ioctl — flush frontbuffer rendering on an FB 🖼️

✨ SYNOPSIS ✨

int drm_mode_dirtyfb_ioctl (struct drm_device *dev , void *data , struct
       drm_file *file_priv );

🎀 ARGUMENTS 🎀

• dev — drm device for the ioctl
• data — data pointer for the ioctl
• file_priv — drm file for the ioctl call

💖 DESCRIPTION 💖

Lookup the FB and flush out the damaged area supplied by userspace as a clip rectangle list. Generic userspace which does frontbuffer rendering must call this ioctl to flush out the changes on manual-update display outputs, e.g. usb display-link, mipi manual update panels or edp panel self refresh modes.

Modesetting drivers which always update the frontbuffer do not need to implement the corresponding drm_framebuffer_funcs.dirty callback.

Called by the user via ioctl. 📞

🔥 RETURN 🔥

Zero on success, negative errno on failure. 😭

🦋 SEE ALSO 🦋

• Kernel file ./drivers/gpu/drm/drm_framebuffer.c overview(9)
• drm_mode_addfb(9)
• drm_mode_addfb2(9)
• drm_mode_rmfb(9)
• drm_mode_getfb(9)
• drm_mode_getfb2_ioctl(9)
• drm_fb_release(9)
• drm_framebuffer_init(9)
• drm_framebuffer_lookup(9)
• drm_framebuffer_unregister_private(9)
• drm_framebuffer_cleanup(9)
• drm_framebuffer_remove(9)

mwah 💖 huge sign-off energy to the source/version line ./drivers/gpu/drm, the date October 2026, and the manual name drm_mode_dirtyfb_ioctl(9) — that's the whole footer, bestie, periodt. 🎀