mfd_add_devices(9)

✨ mfd_add_devices(9) ✨

okay so bestie, welcome to the mfd_add_devices(9) glow-up 💅 this is a page from the Kernel API Manual, and it's literally the moment where you register a whole squad of child devices. it's giving "mom friend introducing her whole group chat to the party" energy, and honestly? iconic.

🌸 NAME 🌸

mfd_add_devices — register child devices 🎀

🦋 SYNOPSIS 🦋

int mfd_add_devices (struct device *parent , int id , const struct
mfd_cell *cells , int n_devs , struct resource *mem_base , int irq_base
, struct irq_domain *domain );

💖 ARGUMENTS 💖

• parent — pointer to the parent device. yeah, the main character whose children we're about to introduce 🫶
• id — can be PLATFORM_DEVID_AUTO to let the Platform API take care of device numbering, or it gets added to a device's cell_id. so like, either the platform handles the numbering for you or you're tacking this number onto the cell id — your call, no cap ✨
• cells — an array of (struct mfd_cell)s describing the child devices. this is the little roster of who's who in the group 💅
• n_devs — number of child devices to register. count 'em, bestie 🔥
• mem_base — parent register range resource for child devices.
• irq_base — base of the range of virtual interrupt numbers allocated for this MFD device. unused if domain is specified. like, it's literally sitting there doing nothing if you brought a domain along 🙈
• domain — interrupt domain to create mappings for hardware interrupts. this is the one that handles the interrupt map-making 🧚

👑 SEE ALSO 👑

• Kernel file ./drivers/mfd/mfd-core.c
• devm_mfd_add_devices(9)

lowkey reminder bestie: if you pass a domain, that irq_base argument is just vibing unused. don't come for her, she's fine, she's just not needed 💀

and that's the whole page, bestie — go register those children and slay 🌈⭐ this lil sign-off comes to you from ./drivers/mfd, dated October 2026, in mfd_add_devices(9). mwah 💋🦋🍓