acpi_dma_update_dma_spec(9)
π acpi_dma_update_dma_spec(9)
ok so this is a page from the Kernel API Manual, and bestie, it's a little function with one very specific job. let's get into it π«Ά
β¨ NAME β¨
acpi_dma_update_dma_spec β get your dma specifier all prepped and cute so it can be handed off to the translation function π
πΈ SYNOPSIS πΈ
int acpi_dma_update_dma_spec (struct acpi_dma *adma , struct
acpi_dma_spec *dma_spec );
literally two args, one int coming back at you. slay.
π ARGUMENTS π
admaβ thestruct acpi_dmaof the DMA controller. like, the controller in question, bestie π¦dma_specβ the dma specifier that's about to get updated β¨
π DESCRIPTION π
ok so per the ACPI 5.0 Specification Table 6-170 "Fixed DMA Resource Descriptor", the DMA Request Line bits are a platform-relative number that uniquely identifies the request line that got assigned. iykyk π
and the request line-to-Controller mapping? that whole situation is handled in a controller-specific OS driver. so basically, because that mapping lives over there, we can safely adjust slave_id once the appropriate controller has been found. no cap, that's the whole reason this is safe π
π₯ RETURN π₯
0β if no information is available-1β on mismatch π1β otherwise β¨
π SEE ALSO π
Kernel file ./drivers/dma/acpi-dma.c β go look, it's right there π
acpi_dma_parse_resource_group(9)acpi_dma_parse_csrt(9)acpi_dma_controller_register(9)acpi_dma_controller_free(9)devm_acpi_dma_controller_register(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)
and that's the whole page, bestie π
this one lives in ./drivers/dma and it's stamped October 2026 β so like, go forth and translate those dma specifiers, mwah π§π
π¦ where this page comes from
- nixpkgs unstable: linux-manual 7.3.1
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash-1017 on : a language model's rewrite of the original, under its terms