ENUM ATH5K_DEBUG_LEVEL(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’– NAME πŸ’–

enum ath5k_debug_level β€” literally the ath5k debug level, that's it, that's the whole vibe ✨


🌸 SYNOPSIS 🌸

okay bestie, here's the whole enum, look at all these constants:

enum ath5k_debug_level {
    ATH5K_DEBUG_RESET ,
    ATH5K_DEBUG_INTR ,
    ATH5K_DEBUG_MODE ,
    ATH5K_DEBUG_XMIT ,
    ATH5K_DEBUG_BEACON ,
    ATH5K_DEBUG_CALIBRATE ,
    ATH5K_DEBUG_TXPOWER ,
    ATH5K_DEBUG_LED ,
    ATH5K_DEBUG_DUMPBANDS ,
    ATH5K_DEBUG_DMA ,
    ATH5K_DEBUG_ANI ,
    ATH5K_DEBUG_DESC ,
    ATH5K_DEBUG_ANY

};

πŸŽ€ Constants πŸŽ€

so here's what each one is giving, one by one 🫢

  • ATH5K_DEBUG_RESET β€” reset processing, the "start over era" of debug messages πŸ’…
  • ATH5K_DEBUG_INTR β€” interrupt handling, all the little interrupts doing their thing ⚑
  • ATH5K_DEBUG_MODE β€” mode init/setup, the getting-ready montage 🧚
  • ATH5K_DEBUG_XMIT β€” basic xmit operation, the actual sending of packets, main character behavior πŸ‘‘
  • ATH5K_DEBUG_BEACON β€” beacon handling, beacons be beaconing 🌈
  • ATH5K_DEBUG_CALIBRATE β€” periodic calibration, the little tune-ups on the reg πŸŽ€
  • ATH5K_DEBUG_TXPOWER β€” transmit power setting, how loud we're yelling πŸ”₯
  • ATH5K_DEBUG_LED β€” led management, the blinkenlights, iconic honestly ✨
  • ATH5K_DEBUG_DUMPBANDS β€” dump bands, yeah it dumps the bands, no notes πŸ’€
  • ATH5K_DEBUG_DMA β€” debug dma start/stop, the DMA getting its own little spotlight πŸ¦‹
  • ATH5K_DEBUG_ANI β€” debug Adaptive Noise Immunity, capital letters because it's That Girl πŸ’œ
  • ATH5K_DEBUG_DESC β€” descriptor setup, descriptors being set up, we love a setup 🌸
  • ATH5K_DEBUG_ANY β€” show at any debug level, the "all of the above" option, the people's champ ⭐

✨ Description ✨

okay so here's the whole point, bestie: this debug level controls how much debugging output you get and what type of it you see. that's the entire serve πŸ’…

when the code calls ATH5K_DBG, it passes the debug level in, and that's how it knows where the message should appear. and you, the user, get to control which debugging messages you actually want to see β€” either by the module parameter 'debug' when you load the module, or dynamically at runtime using debugfs 'ath5k/phyX/debug'. slay, options ✨

and the actual big-brain bit: these levels can be combined together by bitwise OR. so you're not stuck picking just one, you can stack them fr fr 🫢

πŸ¦‹ SEE ALSO πŸ¦‹

  • Kernel file ./drivers/net/wireless/ath/ath5k/debug.h β€” go read it, iykyk πŸ“–

that's the whole page bestie, no cap πŸ’– this lil masterpiece dropped in October 2026, lives in ./drivers/net/wireless/ath/ath5k, and it's brought to you by enum ath5k_debug_level(9) β€” periodt πŸ‘‘βœ¨

πŸ“¦ where this page comes from