bam_tx_status(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… bam_tx_status(9) β€” a Kernel API Manual moment

Okay so bestie, we're in the kernel API manual, section 9, and today's main character is bam_tx_status. Yes it's a whole function. Yes it's iconic. Let's get into it πŸŽ€


✨ NAME ✨

bam_tx_status β€” returns status of transaction πŸ’«

Like, that's literally the whole gig. It tells you how your DMA transaction is doing. Vibe check, but for transfers πŸ”₯


🌸 SYNOPSIS 🌸

enum dma_status bam_tx_status (struct dma_chan *chan , dma_cookie_t
cookie , struct dma_tx_state *txstate );

There it is, copy it exactly, don't @ me 🫢


πŸ¦‹ ARGUMENTS πŸ¦‹

  • chan β€” dma channel πŸ’– the actual channel we're asking about, bestie
  • cookie β€” transaction cookie πŸͺ your lil ticket that identifies which transaction you mean
  • txstate β€” DMA transaction state 🌈 the struct where all the state-y details go

πŸ‘‘ DESCRIPTION πŸ‘‘

Return status of dma transaction. That's it, that's the whole thing ✨ It gives you back the status of the DMA transaction you asked about, no cap πŸ’…

Heads up: the manual is genuinely this short. It's giving "confident and concise" and honestly? Slay.

πŸ’œ SEE ALSO πŸ’œ

Kernel file ./drivers/dma/qcom/bam_dma.c 🧚 β€” and here's the whole friend group, all of them, in order, no one left out:

Nineteen besties. Go read them all, iykyk πŸ“šπŸ’€


And that's the page, bestie! 🫢 One tiny sign-off for the record: this manual page lives under ./drivers/dma/qcom and it's dated October 2026. Periodt. β­πŸ’…

πŸ“¦ where this page comes from