fdt_scan_reserved_mem_late(9)

✨ fdt_scan_reserved_mem_late(9) ✨

okay so bestie, welcome to the fdt_scan_reserved_mem_late page from the Kernel API Manual — yes that whole manual name goes right here at the top, i'm not hiding it from you 🫶

---

🌸 NAME 🌸

fdt_scan_reserved_mem_late — the late-night glow-up scan of the FDT that also initializes whatever reserved memory regions are still waiting around 💅

---

🎀 SYNOPSIS 🎀

void fdt_scan_reserved_mem_late (void );

---

🦋 ARGUMENTS 🦋

• void — bestie it takes no arguments. zero. none. it's giving self-sufficient main character energy ✨

---

👑 DESCRIPTION 👑

so here's the vibe: this function goes and scans the DT again — yes, a second lap, we're doing the re-read 💖 — and this time it's specifically to initialize the "static" reserved memory regions, the ones that get defined with the "reg" property.

every single one of those regions then gets hooked up with its own specific init function, and gets stored in the global reserved_mem array. that's the whole slay. it scans, it inits, it stashes. no cap 🧚

---

🌈 SEE ALSO 🌈

go read the actual source, it's right here:

• Kernel file ./drivers/of/of_reserved_mem.c

and then the whole friend group of related functions, all of them, in order, because we don't gatekeep here:

• fdt_fixup_reserved_mem_node(9)
• fdt_validate_reserved_mem_node(9)
• __reserved_mem_init_node(9)
• fdt_init_reserved_mem_node(9)
• of_reserved_mem_device_init_by_idx(9)
• of_reserved_mem_device_init_by_name(9)
• of_reserved_mem_device_release(9)
• devm_of_reserved_mem_device_init(9)
• of_reserved_mem_lookup(9)
• of_reserved_mem_region_to_resource(9)
• of_reserved_mem_region_to_resource_byname(9)
• of_reserved_mem_region_count(9)

---

and that's a wrap bestie 💖✨ this little page lives in ./drivers/of, dated October 2026, and it's literally all yours now. go init something iconic 🎀💅🔥