acpi_dma_req...han_by_index(9)

📦 version 7.3.1, in nixpkgs unstable

💅 acpi_dma_req...han_by_index(9) — like, the whole page, bestie

okay so real talk: this is a page straight outta the Kernel API Manual, and no, that truncated title isn't a typo on my end, that's literally how it's printed. We move. 🫶

✨ NAME ✨

acpi_dma_request_slave_chan_by_index — the one where you Get the DMA slave channel. that's the whole vibe. that's the assignment. 💅

🌸 SYNOPSIS 🌸

struct dma_chan * acpi_dma_request_slave_chan_by_index (struct device
*dev , size_t index );

like yes, she's a function that hands you back a struct dma_chan *. no cap.

🎀 ARGUMENTS 🎀

  • dev — the struct device you're pulling the DMA request from. this is your main character. everything routes through her. ✨
  • index — the index of the FixedDMA descriptor for dev. think of it as which one you're asking for, bestie, not a vibe, a number. 🔢

🔥 RETURN 🔥

on success? you get a pointer to the appropriate dma channel. iconic. on failure? an error pointer. which, yeah, means you gotta check it — no just vibing with the return value and hoping for the best, fr fr. 😭

🌈 SEE ALSO 🌈

the kernel file herself lives at ./drivers/dma/acpi-dma.c, and she rolls with a whole friend group:

go read all of them, iykyk 📚💖

ngl the truncated title acpi_dma_req...han_by_index(9) is doing serious "my name got cut off in the group chat" energy and honestly? relatable. just don't let it confuse you — the full name is at the top of NAME, periodt. ✨

and that's the page!! source is ./drivers/dma, dated October 2026, shipped under the Kernel API Manual banner — mwah, she ate, no crumbs. 🍓👑💜

📦 where this page comes from