devm_mfd_add_devices(9)

📦 version 7.3.1, in nixpkgs unstable

💅 devm_mfd_add_devices(9)

okay so bestie, welcome to the Kernel API Manual — today's main character is devm_mfd_add_devices, and honestly? she's giving "resource manager energy" and we're obsessed ✨

🌸 NAME

devm_mfd_add_devices — the resource managed version of mfd_add_devices() 🎀

like, same vibes as the original, but the kernel cleans up after you so you don't have to. no cap.

🦋 SYNOPSIS

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

✨ ARGUMENTS

  • dev — pointer to the parent device. the momager of this whole situation 👑
  • id — can be PLATFORM_DEVID_AUTO to let the Platform API take care of device numbering for you (slay, delegation), or it gets added to a device's cell_id. your call, bestie 💅
  • cells — array of (struct mfd_cell)s describing the child devices. every child gets a little description card 📇
  • n_devs — the number of child devices to register. count 'em 🔢
  • mem_base — parent register range resource for the child devices 🗺️
  • irq_base — base of the range of virtual interrupt numbers allocated for this MFD device. unused if domain is specified ⚠️ so like, don't bother, iykyk
  • domain — the interrupt domain to create mappings for hardware interrupts for 🧚‍♀️

🔥 DESCRIPTION

Returns 0 on success, or an appropriate negative error number on failure. that's it, that's the vibe check 💀

And the iconic part: all child devices of the MFD will automatically be removed when it gets unbinded 🫶 literally no manual cleanup, the devm_ prefix is doing the work for you, periodt.

🌈 SEE ALSO

and that's the whole page, bestie!! 🍓 source/version: ./drivers/mfd · dated October 2026 · devm_mfd_add_devices(9) — go forth and register those child devices 💖✨

📦 where this page comes from