unflatten_device_tree(9)

💖 NAME 💖

okay bestie, this is unflatten_device_tree(9) from the Kernel API Manual — it creates a tree of device_nodes from a flat blob, and that's the whole name tea 🫖✨

🌸 SYNOPSIS 🌸

void unflatten_device_tree (void );

🎀 ARGUMENTS 🎀

• void — no arguments. zero. nada. the signature is literally void, and it said what it said 💅

🦋 DESCRIPTION 🦋

so here's the vibe: unflatten_device_tree unflattens the device-tree that the firmware passed in, and it creates the tree of struct device_nodes. iconic behavior, no notes 👑

it also fills the "name" and "type" pointers of those nodes, so the normal device-tree walking functions can be used. yes bestie, it's setting them up so the rest of the kernel can take a little stroll through the tree 🌳✨

🧚 SEE ALSO 🧚

Kernel file ./drivers/of/fdt.c is home base, and these are the related pages you should also peek at:

• unflatten_dt_nodes(9)
• __unflatten_device_tree(9)
• of_fdt_unflatten_tree(9)
• early_init_fdt_scan_reserved_mem(9)
• early_init_fdt_reserve_self(9)
• of_scan_flat_dt(9)
• of_scan_flat_dt_subnodes(9)
• of_get_flat_dt_subnode_by_name(9)
• of_fdt_is_compatible(9)
• of_flat_dt_is_compatible(9)
• of_flat_dt_match_machine(9)
• early_init_dt_check_for_initrd(9)
• early_init_dt_check_for_elfcorehdr(9)
• early_init_dt_check_for_usable_mem_range(9)
• early_init_dt_check_kho(9)
• unflatten_and_copy_device_tree(9)

okay that's the page, bestie 💅 source/version: ./drivers/of; date: October 2026; page: unflatten_device_tree(9). byeee 🫶🎀