Go back –> ath5k kerneldoc
If you see nothing its because there is no kdoc yet for this file.
enum ath5k_debug_level
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_DUMP_RX,
ATH5K_DEBUG_DUMP_TX,
ATH5K_DEBUG_DUMPBANDS,
ATH5K_DEBUG_TRACE,
ATH5K_DEBUG_ANY
};
Constants
- ATH5K_DEBUG_RESET
- reset processing
- ATH5K_DEBUG_INTR
- interrupt handling
- ATH5K_DEBUG_MODE
- mode init/setup
- ATH5K_DEBUG_XMIT
- basic xmit operation
- ATH5K_DEBUG_BEACON
- beacon handling
- ATH5K_DEBUG_CALIBRATE
- periodic calibration
- ATH5K_DEBUG_TXPOWER
- transmit power setting
- ATH5K_DEBUG_LED
- led management
- ATH5K_DEBUG_DUMP_RX
- print received skb content
- ATH5K_DEBUG_DUMP_TX
- print transmit skb content
- ATH5K_DEBUG_DUMPBANDS
- dump bands
- ATH5K_DEBUG_TRACE
- trace function calls
- ATH5K_DEBUG_ANY
- show at any debug level
Description
The debug level is used to control the amount and type of debugging output we want to see. The debug level is given in calls to ATH5K_DBG to specify where the message should appear, and the user can control the debugging messages he wants to see, either by the module parameter 'debug' on module load, or dynamically by using debugfs 'ath5k/phyX/debug'. these levels can be combined together by bitwise OR.