fsl_mc_portal_allocate(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’– fsl_mc_portal_allocate(9) πŸ’–

okay bestie, welcome to the Kernel API Manual page for fsl_mc_portal_allocate(9) β€” yes, the manual name is folded in right here because we are not copying the header line, we are living it ✨

πŸ’– NAME πŸ’–

fsl_mc_portal_allocate - Allocates an MC portal. that's the whole name, no cap πŸ’…

✨ SYNOPSIS ✨

int fsl_mc_portal_allocate (struct fsl_mc_device *mc_dev , u16
       mc_io_flags , struct fsl_mc_io **new_mc_io );

πŸŽ€ ARGUMENTS πŸŽ€

  • mc_dev β€” MC device for which the MC portal is to be allocated. like, the device that's getting its portal moment πŸ’…
  • mc_io_flags β€” Flags for the fsl_mc_io object that wraps the allocated MC portal. flags for the wrapper, because the wrapper matters too 🫢
  • new_mc_io β€” Pointer to area where the pointer to the fsl_mc_io object that wraps the allocated MC portal is to be returned. yes, a pointer to an area where a pointer gets returned β€” pointerception, but make it slay 😭

πŸ¦‹ DESCRIPTION πŸ¦‹

okay so here's the tea: this function allocates an MC portal from the device's parent DPRC, from the corresponding MC bus' pool of MC portals and wraps it in a new fsl_mc_io object. iconic behavior, honestly.

and if 'mc_dev' is a DPRC itself, the portal is allocated from its own MC bus. periodt. that's the whole description, no extra lore added by me 🌸

🌈 SEE ALSO 🌈


mwah πŸ’‹ β€” source/version ./drivers/bus/fsl-mc, date October 2026, page fsl_mc_portal_allocate(9). okay bye, slay your kernel adventures 🌟

πŸ“¦ where this page comes from