acpi_dma_pa...source_group(9)

✨ NAME ✨

acpi_dma_parse_resource_group — bestie, this is the little function that matches your device and parses the resource group 💅

---

🌸 SYNOPSIS 🌸

int acpi_dma_parse_resource_group (const struct acpi_csrt_group *grp ,
struct acpi_device *adev , struct acpi_dma *adma );

Ok so it takes three things and hands you back an int, no cap ✨

---

🎀 ARGUMENTS 🎀

• grp — the CSRT resource group 🫶 this is the group thing you're parsing, periodt.
• adev — the ACPI device to match with 🔥 like, the one you're trying to pair up.
• adma — the struct acpi_dma of the given DMA controller 💖 the controller's whole vibe, basically.

---

🦋 DESCRIPTION 🦋

So here's the situation, bestie: to match a device from the DSDT table to the corresponding CSRT device, we use the MMIO address and the IRQ 👑 that's literally the whole trick, iykyk.

---

⭐ RETURN ⭐

• 1 on success 🎉 slay
• 0 when no information is available 🙈
• or the appropriate errno value on error 😭

---

💜 SEE ALSO 💜

Kernel file ./drivers/dma/acpi-dma.c, plus all these icons:

• acpi_dma_parse_csrt(9)
• acpi_dma_controller_register(9)
• acpi_dma_controller_free(9)
• devm_acpi_dma_controller_register(9)
• acpi_dma_update_dma_spec(9)
• acpi_dma_parse_fixed_dma(9)
• acpi_dma_request_slave_chan_by_index(9)
• acpi_dma_request_slave_chan_by_name(9)
• acpi_dma_simple_xlate(9)

---

okay that's the whole page, you ate that 💅 this little beauty lives in ./drivers/dma and it's stamped October 2026 — go off, queen 👑💖

(also the manual itself is acpi_dma_pa...source_group(9), in case you were wondering — the truncated name is not a typo, it's just how she's filed ✨)