fsl_mc_reso...l_add_device(9)

🌸 fsl_mc_resource_pool_add_device — NAME 💅

okay so bestie, this page is from the Kernel API Manual, section 9, and the title got cut off in the header as fsl_mc_reso...l_add_device(9) — tragic, I know, but it's literally fsl_mc_resource_pool_add_device.

What does it do? It adds an allocatable object to a resource pool of a given fsl-mc bus. That's it, that's the whole vibe. 🦋

✨ SYNOPSIS ✨

int fsl_mc_resource_pool_add_device (struct fsl_mc_bus *mc_bus , enum
       fsl_mc_pool_type pool_type , struct fsl_mc_device *mc_dev );

Returns an int, takes three args. Iconic signature, no notes. 👑

🎀 ARGUMENTS 🎀

• mc_bus — pointer to the fsl-mc bus. like, the bus in question, she's the main character here 💖
• pool_type — pool type. yes bestie, that's the type of the pool 🌸
• mc_dev — pointer to allocatable fsl-mc device. the actual device you're adding to the pool, periodt ✨

🔥 SEE ALSO 🔥

• Kernel file ./drivers/bus/fsl-mc/fsl-mc-allocator.c — go read the source, iykyk 📖
• fsl_mc_resource_pool_remove_device(9) — the reverse move, the breakup arc 💔
• fsl_mc_object_allocate(9) — get yourself an object 🎁
• fsl_mc_object_free(9) — and give it back, be responsible 🫶

ngl this one's short and sweet — no options, no env vars, no exit status drama, just three args and a dream 💀

anyway bestie, this ✨ iconic ✨ page came from ./drivers/bus/fsl-mc, dated October 2026 — mwah, go forth and pool those resources 💅🎀🌈