ath5k_hw_stop_tx_dma(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

✨ 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 β€” The struct 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 πŸ”₯


mwah πŸ’‹ this cutie lives in ./drivers/net/wireless/ath/ath5k, and the date on it is October 2026 πŸ—“οΈβœ¨ slay.

πŸ“¦ where this page comes from