Searched refs:debugging (Results 1 – 25 of 97) sorted by relevance
1234
| /drivers/infiniband/ulp/ipoib/ |
| D | Kconfig | 28 bool "IP-over-InfiniBand debugging" if EXPERT
32 This option causes debugging code to be compiled into the
38 debugfs, which contains files that expose debugging
43 bool "IP-over-InfiniBand data path debugging"
46 This option compiles debugging code into the data path
49 turned off, this debugging code will have some performance
|
| /drivers/gpu/drm/i915/ |
| D | Kconfig.debug | 21 bool "Enable additional driver debugging"
41 Choose this option to turn on extra driver debugging that may affect
91 Enable additional and verbose debugging output that will spam
92 ordinary tests, but may be vital for post-mortem debugging when
105 Enable additional and verbose debugging output that will spam
106 ordinary tests, but may be vital for post-mortem debugging when
114 bool "Enable additional driver debugging for fence objects"
119 Choose this option to turn on extra driver debugging that may affect
127 bool "Enable additional driver debugging for detecting dependency cycles"
131 Choose this option to turn on extra driver debugging that may affect
[all …]
|
| /drivers/atm/ |
| D | Kconfig | 55 bool "Enable extended debugging"
58 Extended debugging records various events and displays that list
61 Note that extended debugging may create certain race conditions
170 bool "Enable extended debugging"
173 Extended debugging records various events and displays that list
176 Note that extended debugging may create certain race conditions
222 bool "Enable debugging messages"
225 Somewhat useful debugging messages are available. The choice of
240 for debugging or special applications only, so the safe answer is N.
257 bool "Enable debugging messages"
[all …]
|
| /drivers/memstick/ |
| D | Kconfig | 17 bool "MemoryStick debugging"
20 say N here. This enables MemoryStick core and driver debugging.
|
| /drivers/infiniband/hw/mthca/ |
| D | Kconfig | 11 bool "Verbose debugging output" if EXPERT
15 This option causes debugging code to be compiled into the
|
| /drivers/net/wireless/zydas/zd1211rw/ |
| D | Kconfig | 14 bool "ZyDAS ZD1211 debugging"
17 ZD1211 debugging messages. Choosing Y will result in additional debug
|
| /drivers/net/wireless/ath/ath5k/ |
| D | Kconfig | 26 bool "Atheros 5xxx debugging"
29 Atheros 5xxx debugging messages.
51 option if you are interested in debugging the driver.
|
| /drivers/usb/dwc2/ |
| D | Kconfig | 69 Say Y here to enable debugging messages in the DWC2 Driver.
75 Say Y here to enable verbose debugging messages in the DWC2 Driver.
91 Say N here to disable (verbose) debugging messages to be
92 logged for periodic transfers. This allows better debugging of
|
| /drivers/md/bcache/ |
| D | Kconfig | 13 bool "Bcache debugging"
18 Enables extra debugging tools, allows expensive runtime checks to be
|
| /drivers/misc/cb710/ |
| D | Kconfig | 16 bool "Enable driver debugging"
20 say N here. This adds a lot of debugging output to dmesg.
|
| /drivers/ntb/test/ |
| D | Kconfig | 14 This is a simple debugging driver that enables the doorbell and
16 enables more complicated debugging to be scripted from user space.
|
| /drivers/net/ethernet/mellanox/mlx4/ |
| D | Kconfig | 34 bool "Verbose debugging output" if (MLX4_CORE && EXPERT)
38 This option causes debugging code to be compiled into the
|
| /drivers/net/wireless/intel/ipw2x00/ |
| D | Kconfig | 21 and for tips for debugging issues and problems.
51 bool "Enable full debugging output in IPW2100 module."
83 driver and for tips for debugging issues and problems.
145 bool "Enable full debugging output in IPW2200 module."
179 bool "Full debugging output for the LIBIPW component"
|
| /drivers/hwtracing/intel_th/ |
| D | Kconfig | 10 full system debugging.
81 bool "Intel(R) Trace Hub debugging"
84 Say Y here to enable debugging.
|
| /drivers/pnp/ |
| D | Kconfig | 26 bool "PNP debugging messages"
29 Say Y here if you want the PNP layer to be able to produce debugging
|
| /drivers/net/wireless/broadcom/b43/ |
| D | Kconfig | 175 bool "Broadcom 43xx debugging"
178 Broadcom 43xx debugging.
185 Do not enable this, unless you are debugging the driver.
189 Only say Y, if you are debugging a problem in the b43 driver sourcecode.
|
| /drivers/net/wireless/ath/wil6210/ |
| D | Kconfig | 41 option if you are interested in debugging the driver.
53 option if you are interested in debugging the driver.
|
| /drivers/staging/isdn/gigaset/ |
| D | Kconfig | 57 bool "Gigaset debugging"
59 This enables debugging code in the Gigaset drivers.
|
| /drivers/acpi/apei/ |
| D | Kconfig | 60 mainly used for debugging and testing the other parts of
69 if you want to debugging and testing the ERST kernel support
|
| /drivers/bcma/ |
| D | Kconfig | 112 bool "BCMA debugging"
114 This turns on additional debugging messages.
|
| /drivers/pcmcia/ |
| D | Kconfig | 222 bool "Enable debugging"
225 Say Y here to enable debugging for the SoC PCMCIA layer.
226 You will need to choose the debugging level either via the
236 In all the above examples, N is the debugging verbosity
|
| /drivers/i2c/ |
| D | Kconfig | 125 bool "I2C Core debugging messages"
132 bool "I2C Algorithm debugging messages"
140 bool "I2C Bus debugging messages"
|
| /drivers/vlynq/ |
| D | Kconfig | 19 Turn on VLYNQ bus debugging.
|
| /drivers/net/wireless/marvell/libertas_tf/ |
| D | Kconfig | 10 bool "Enable full debugging output in the Libertas thin firmware module."
|
| /drivers/scsi/ |
| D | st.c | 69 #define DEBC(a) if (debugging) { a ; }
161 static int debugging = DEBUG; variable
319 if (debugging) { st_printk(ST_DEB_MSG, t, fmt, ##a ); }
379 if (debugging) { in st_chk_result()
388 if (!debugging) { /* Abnormal conditions for tape */ in st_chk_result()
433 if (debugging) { in st_chk_result()
716 DEB(if (debugging && retval) in write_behind_check()
1124 if ( DEB( debugging || ) !STp->inited) in check_tape()
2131 if (debugging && STps->eof != ST_NOEOF) in st_read()
2183 if (debugging && STps->eof != ST_NOEOF) in st_read()
[all …]
|
1234