ath5k_hw_stop_tx_dma(9)
β¨ ath5k_hw_stop_tx_dma(9) β¨
okay so bestie, this is a Kernel API Manual page and it's literally all about putting one specific transmit queue to bed π΄π
β no pending frames allowed, periodt.
πΈ NAME πΈ
ath5k_hw_stop_tx_dma β Stop DMA transmit on a specific queue ππ€
π¦ SYNOPSIS π¦
int ath5k_hw_stop_tx_dma (struct ath5k_hw *ah , unsigned int queue );
π ARGUMENTS π
ahβ Thestruct ath5k_hwπ this is the hardware struct, the main character fr.queueβ The hw queue number π§Ί like, which hardware queue are we stopping?
π DESCRIPTION π
Stop DMA transmit on a specific hw queue and drain queue so we don't have any pending frames. π«π¨β¨
Returns -EBUSY if we still have pending frames π β like bestie, the queue is not empty yet. Returns -EINVAL if queue number is out of range or inactive π β invalid queue vibes, not it.
lowkey important: those return values are the whole vibe check here.-EBUSY= still pending frames,-EINVAL= queue number out of range or inactive. no cap. π
π₯ SEE ALSO π₯
- Kernel file
./drivers/net/wireless/ath/ath5k/dma.cβ DMA and interrupt masking functions(9) π 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_beacon_queue(9)ath5k_hw_get_txdp(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)
mwah π this cutie lives in ./drivers/net/wireless/ath/ath5k, and the date on it is October 2026 ποΈβ¨ slay.
π¦ 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