firmware_map_add_hotplug(9)

🌸 NAME 🌸

Okay bestie, this is the firmware_map_add_hotplug(9) page from the Kernel API Manual — and the name itself is firmware_map_add_hotplug, which adds a firmware mapping entry when we do memory hotplug. Iconic. 💅

✨ SYNOPSIS ✨

int firmware_map_add_hotplug (u64 start , u64 end , const char *type );

🎀 ARGUMENTS 🎀

• start — start of the memory range. 🫶
• end — end of the memory range (exclusive). Yes, exclusive, bestie — keep that in mind 💀
• type — type of the memory range. 💖

🦋 DESCRIPTION 🦋

So this function adds a firmware mapping entry. It's for memory hotplug, and it's similar to the function firmware_map_add_early. The only difference? It will create the syfs entry dynamically. Slay. ✨

💜 RETURN 💜

It returns 0 on success, or -ENOMEM if no memory could be allocated. That's the whole return vibe, no cap. 😭

🔥 SEE ALSO 🔥

• Kernel file ./drivers/firmware/memmap.c
• firmware_map_add_entry(9)
• firmware_map_remove_entry(9)
• firmware_map_find_entry_in_list(9)
• firmware_map_find_entry(9)
• firmware_map_find_entry_bootmem(9)
• firmware_map_add_early(9)
• firmware_map_remove(9)

Sign-off time, bestie: source/version is ./drivers/firmware, date is October 2026, and the page is firmware_map_add_hotplug(9). Byeee, go be iconic with your firmware maps 💖🦋🌈