fdt_fixup_reserved_mem_node(9)

💖 fdt_fixup_reserved_mem_node(9) — a Kernel API Manual moment 💖

okay so bestie, welcome to the Kernel API Manual ✨ we're looking at fdt_fixup_reserved_mem_node(9) today and honestly it's giving "small function, big responsibilities" 🎀

---

✨ NAME ✨

fdt_fixup_reserved_mem_node — call the fixup function for a reserved memory node 🫶

---

🌸 SYNOPSIS 🌸

int fdt_fixup_reserved_mem_node (unsigned long node , phys_addr_t base ,
phys_addr_t size );

---

🦋 ARGUMENTS 🦋

• node — the FDT node that needs fixing up, like it's getting a lil glow-up 💅
• base — the base address of the reserved memory region (the starting point, the origin story, iykyk)
• size — how big the reserved memory region is 💖

---

🧚 DESCRIPTION 🧚

okay so here's the vibe: this function iterates through the reserved memory drivers 🔥 and calls the node_fixup callback for the compatible entry that matches node. that's it. that's the whole personality. lowkey iconic of it, tbh ⭐

---

💜 RETURN 💜

• 0 on success — slay, we ate 💅
• -ENODEV if no compatible match was found — not me getting rejected by the driver table 😭💀

---

🌈 SEE ALSO 🌈

the kernel file itself lives at ./drivers/of/of_reserved_mem.c — go say hi bestie 🫶

and the whole friend group:

• fdt_scan_reserved_mem_late(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)

---

no cap, if you're gonna go poke around, poke around ./drivers/of first 🌸

okay that's the whole page, mwah 💋 — sourced from ./drivers/of, dated October 2026, and yeah, it's fdt_fixup_reserved_mem_node(9) all the way down, periodt 👑🎀✨