ath5k_hw_get_txdp(9)

💖 ath5k_hw_get_txdp(9) 💖

okay so real talk, this is a page straight out of the Kernel API Manual, and it's all about grabbing the TX descriptor address for a specific queue. bestie, it's giving "one tiny function, huge main character energy" ✨

---

🌸 NAME 🌸

ath5k_hw_get_txdp — get the TX Descriptor's address for a specific queue 🎀

---

🦋 SYNOPSIS 🦋

u32 ath5k_hw_get_txdp (struct ath5k_hw *ah , unsigned int queue );

---

💅 ARGUMENTS 💅

• ah — the struct ath5k_hw, literally the whole hardware vibe 🫶
• queue — the hw queue number, iykyk 🔥

---

✨ DESCRIPTION ✨

So what does it do? It gets the TX descriptor's address for a specific queue, periodt. 💅

For 5210 we straight up ignore the queue number and use the tx queue type instead, because we only have 2 queues — that's the whole situation, no cap. We use TXDP0 for the normal data queue and TXDP1 for the beacon queue 🎀. For newer chips with QCU/DCU we just read the corresponding TXDP register. slay. ✨

XXX: Is TXDP read and clear ? 👀 (yes bestie, the original page really does leave that question hanging, and we're not about to invent an answer 🙈)

---

🌈 SEE ALSO 🌈

Kernel file ./drivers/net/wireless/ath/ath5k/dma.c DMA and interrupt masking functions(9) — plus the whole friend group:

• ath5k_hw_start_rx_dma(9)
• ath5k_hw_stop_rx_dma(9)
• ath5k_hw_get_rxdp(9)
• ath5k_hw_set_rxdp(9)
• ath5k_hw_start_tx_dma(9)
• ath5k_hw_stop_tx_dma(9)
• ath5k_hw_stop_beacon_queue(9)
• ath5k_hw_set_txdp(9)
• ath5k_hw_update_tx_triglevel(9)
• ath5k_hw_is_intr_pending(9)
• ath5k_hw_get_isr(9)
• ath5k_hw_set_imr(9)
• ath5k_hw_dma_init(9)
• ath5k_hw_dma_stop(9)

---

and that's the whole page, bestie 🫶 this little icon lives at ./drivers/net/wireless/ath/ath5k, dated October 2026, and the page itself is ath5k_hw_get_txdp(9) — go read it again whenever you need the vibe check 💖🎀🦋