acpi_dma_update_dma_spec(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… 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 β€” the struct acpi_dma of 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 πŸ“


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