fsl_mc_object_allocate(9)

💅 fsl_mc_object_allocate 💅

okay bestie, welcome to the Kernel API Manual moment — this page is all about fsl_mc_object_allocate(9), and it's lowkey iconic. let's get into it 🦋✨

🌸 NAME 🌸

fsl_mc_object_allocate — allocates an fsl-mc object of the given pool type from a given fsl-mc bus instance.

🦋 SYNOPSIS 🦋

       int fsl_mc_object_allocate (struct fsl_mc_device *mc_dev , enum
       fsl_mc_pool_type pool_type , struct fsl_mc_device **new_mc_adev );

🎀 ARGUMENTS 🎀

• mc_dev — the fsl-mc device that is used in conjunction with the allocated object. bestie, they're a package deal 🫶
• pool_type — the pool type. that's it, that's the whole vibe 💅
• new_mc_adev — pointer to the area where the pointer to the allocated device is to be returned. yes, pointer-to-pointer realness 😭

🔥 DESCRIPTION 🔥

okay so here's the tea: allocatable objects are always used in conjunction with some functional device — no solo main character energy for them, periodt. this function allocates an object of the specified type from the DPRC containing the functional device. slay 💖

⚠️ NOTE ⚠️

bestie, important: pool_type must be different from FSL_MC_POOL_MCP, since MC portals are allocated using fsl_mc_portal_allocate, instead of this function. this is not a drill 🙈

🌈 SEE ALSO 🌈

• Kernel file ./drivers/bus/fsl-mc/fsl-mc-allocator.c
• fsl_mc_resource_pool_add_device(9)
• fsl_mc_resource_pool_remove_device(9)
• fsl_mc_object_free(9)

this cutie came from ./drivers/bus/fsl-mc, dated October 2026, and it's the fsl_mc_object_allocate(9) page — mwah, bye bestie 💖🎀✨