drm_mm_initialized(9)

✨ drm_mm_initialized ✨

okay bestie, welcome to this little slice of the Kernel API Manual — it's drm_mm_initialized, and it's literally exactly what it sounds like 💅

🌸 NAME 🌸

drm_mm_initialized — the vibe check that tells you whether an allocator is, in fact, initialized 🫶

🎀 SYNOPSIS 🎀

bool drm_mm_initialized (const struct drm_mm *mm );

🦋 ARGUMENTS 🦋

• mm — the drm_mm you wanna check, bestie. that's it. that's the whole argument 🎀

💖 DESCRIPTION 💖

so here's the tea: drivers should clear the struct drm_mm prior to initialisation if they want to use this function. like, actually clear it — don't be out here with stale garbage and then ask this helper if things are initialized, that's not giving what you think it's giving 😭

also, drivers should use this helper for proper encapsulation of drm_mm internals. yes queen, encapsulate! don't go poking at the guts of drm_mm yourself, that's not main character behaviour, that's just asking for a bad time 🧚

⭐ RETURN ⭐

True if the mm is initialized. no cap, that's the whole return value 💀✨

🔥 SEE ALSO 🔥

Kernel file ./include/drm/drm_mm.h, plus the whole friend group:

• enum drm_mm_insert_mode(9)
• struct drm_mm_node(9)
• struct drm_mm(9)
• struct drm_mm_scan(9)
• drm_mm_node_allocated(9)
• drm_mm_hole_follows(9)
• drm_mm_hole_node_start(9)
• drm_mm_hole_node_end(9)
• drm_mm_nodes(9)
• drm_mm_for_each_node(9)
• drm_mm_for_each_node_safe(9)
• drm_mm_for_each_hole(9)
• drm_mm_insert_node_generic(9)
• drm_mm_insert_node(9)
• drm_mm_clean(9)
• drm_mm_for_each_node_in_range(9)
• drm_mm_scan_init(9)

okay that's the whole page, you ate that 🍓 mwah 💜 this little gem lives in ./include/drm and it's stamped October 2026 — catch you in the next one, bestie! 🌈👑