rio_request_mport_dma(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… rio_request_mport_dma(9) πŸ’…

okay bestie, welcome to the Kernel API Manual β€” yes, the Kernel API Manual, the one you keep hearing about at parties. this page is literally about rio_request_mport_dma, and it's short, it's sweet, and it's gonna slay. let's go πŸŽ€


✨ NAME ✨

rio_request_mport_dma β€” request a RapidIO capable DMA channel that's associated with the specified local RapidIO mport device. that's it, that's the whole vibe πŸ¦‹


✨ SYNOPSIS ✨

struct dma_chan * rio_request_mport_dma (struct rio_mport *mport );

like, look at that signature. no cap, it's giving main character energy πŸ‘‘


✨ ARGUMENTS ✨

  • mport β€” the RIO mport that's gonna perform the DMA data transfers. this is the port, the one doing the heavy lifting, the moment πŸ’ͺ

✨ DESCRIPTION ✨

so here's the tea: it returns a pointer to the allocated DMA channel. or NULL if it failed. like, if it didn't work out, you get NULL. that's the entire plot twist 😭


✨ SEE ALSO ✨

okay so this is the part where the whole friend group shows up. brace yourself, bestie, there are so many of them and they're all iconic in their own way πŸ’œ

and yes, they all live in the kernel file ./drivers/rapidio/rio.c β€” that's the group chat, iykyk 🫢

like… that's the whole roster. every single one. no skips, no cuts, we don't do that here πŸ’…βœ¨


pro tip from your girl: this page lives under ./drivers/rapidio, dated October 2026, and it's rio_request_mport_dma(9) forever and always. mwah πŸ“

stay hydrated, read your manpages, and remember: NULL is a valid answer bestie 🌈⭐🧚

πŸ“¦ where this page comes from