drm_mode_config_cleanup(9)

💖 NAME 💖

drm_mode_config_cleanup — free up DRM mode_config info. Welcome to drm_mode_config_cleanup(9) from the Kernel API Manual, bestie — this is the cleanup era and we’re gonna understand it fr fr ✨

🦋 SYNOPSIS 🦋

void drm_mode_config_cleanup (struct drm_device *dev );

🌸 ARGUMENTS 🌸

• dev — the DRM device. That’s the main character of this whole teardown arc 💅

🎀 DESCRIPTION 🎀

Okay so picture this: drm_mode_config_cleanup frees up all the connectors and CRTCs associated with this DRM device, and then it frees up the framebuffers and associated buffer objects. Like, full cleanup, no crumbs left, periodt 🧹✨

Note that since this should happen single-threaded at driver/device teardown time, no locking is required. It’s the driver’s job to make sure that guarantee actually holds true. No cap — if that single-threaded promise isn’t real, that’s a driver problem, not a “maybe add a lock” vibe 🙈

FIXME: With the managed drmm_mode_config_init it is no longer necessary for drivers to explicitly call this function. So yeah, this is one of those “still here, but managed init changed the game” situations 💀

🔥 SEE ALSO 🔥

• Kernel file ./drivers/gpu/drm/drm_mode_config.c
• drm_mode_getresources(9)
• drm_mode_config_reset(9)
• drm_mode_config_create_initial_state(9)
• drmm_mode_config_init(9)

Signing off from ./drivers/gpu/drm, October 2026 — stay clean, stay single-threaded, and slay the teardown 💖🎀🫶