atapi_check_dma(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸŽ€ NAME πŸŽ€

Ok bestie, this is the Kernel API Manual page for atapi_check_dma β€” manual name folded right in at the top so you’re not lost. Its whole job? Check whether ATAPI DMA can be supported. That’s it. A tiny little gatekeeper moment, and honestly? Iconic. πŸ’…


✨ SYNOPSIS ✨

int atapi_check_dma (struct ata_queued_cmd *qc );

🌸 ARGUMENTS 🌸

  • qc β€” metadata associated with the taskfile to check. It’s the context pack for the command you’re vibe-checking. 🫢

πŸ¦‹ DESCRIPTION πŸ¦‹

This lets the low-level driver filter ATA PACKET commands and hand back a status saying whether or not it’s OK to use DMA for the supplied PACKET command. No cap, it’s giving β€œdriver gets a say in whether DMA is invited to the party.” ✨

LOCKING: spin_lock_irqsave(host lock)

πŸ”₯ RETURN πŸ”₯

  • 0 when ATAPI DMA can be used
  • nonzero otherwise

So zero is the slay case, and nonzero is the nope case. πŸ’€

πŸ’– SEE ALSO πŸ’–

Kernel file: ./drivers/ata/libata-core.c β€” that’s the spot. And here’s the whole friend group, in order:


Bye bestie πŸ’– this one lives under ./drivers/ata, dated October 2026, and it’s the atapi_check_dma(9) entry. Now go forth and check that DMA. πŸŒˆπŸ‘‘

πŸ“¦ where this page comes from