| /kernel/linux/linux-6.6/drivers/usb/storage/ |
| D | unusual_uas.h | 31 /* Reported-by: Till Dörges <doerges@pre-sense.de> */
39 * Initially Reported-by: Julian Groß <julian.g@posteo.de>
48 /* Reported-by: Julian Sikorski <belegdol@gmail.com> */
55 /* Reported-by: Zhihong Zhou <zhouzhihong@greatwall.com.cn> */
62 /* Reported-by: Hongling Zeng <zenghongling@kylinos.cn> */
79 /* Reported-by: Tom Hu <huxiaoying@kylinos.cn> */
86 /* Reported-by: David Webb <djw@noc.ac.uk> */
93 /* Reported-by: Oliver Neukum <oneukum@suse.com> */
100 /* Reported-by: Benjamin Tissoires <benjamin.tissoires@redhat.com> */
107 /* Reported-by: Tom Arild Naess <tanaess@gmail.com> */
[all …]
|
| D | unusual_devs.h | 62 /* Reported by Rodolfo Quesada <rquesada@roqz.net> */
74 /* Reported by Ben Efros <ben@pc-doctor.com> */
82 * Reported by Grant Grundler <grundler@parisc-linux.org>
97 * Reported by Sebastian Kapfer <sebastian_kapfer@gmx.net>
132 /* Reported by Orgad Shaneh <orgads@gmail.com> */
138 /* Reported by Christian Leber <christian@leber.de> */
145 /* Reported by Stefan Werner <dustbln@gmx.de> */
152 /* Reported by Pete Zaitcev <zaitcev@redhat.com>, bz#176584 */
159 * Reported by Andrew Nayenko <relan@bk.ru>
168 /* Reported by Mario Rettig <mariorettig@web.de> */
[all …]
|
| /kernel/linux/linux-5.10/drivers/usb/storage/ |
| D | unusual_uas.h | 31 /* Reported-by: Till Dörges <doerges@pre-sense.de> */
39 * Initially Reported-by: Julian Groß <julian.g@posteo.de>
48 /* Reported-by: Julian Sikorski <belegdol@gmail.com> */
55 /* Reported-by: Hongling Zeng <zenghongling@kylinos.cn> */
72 /* Reported-by: Tom Hu <huxiaoying@kylinos.cn> */
79 /* Reported-by: David Webb <djw@noc.ac.uk> */
86 /* Reported-by: Benjamin Tissoires <benjamin.tissoires@redhat.com> */
93 /* Reported-by: Tom Arild Naess <tanaess@gmail.com> */
100 /* Reported-by: Claudio Bizzarri <claudio.bizzarri@gmail.com> */
107 /* Reported-by: David Kozub <zub@linux.fjfi.cvut.cz> */
[all …]
|
| D | unusual_devs.h | 62 /* Reported by Rodolfo Quesada <rquesada@roqz.net> */
74 /* Reported by Ben Efros <ben@pc-doctor.com> */
82 * Reported by Grant Grundler <grundler@parisc-linux.org>
97 * Reported by Sebastian Kapfer <sebastian_kapfer@gmx.net>
132 /* Reported by Orgad Shaneh <orgads@gmail.com> */
138 /* Reported by Christian Leber <christian@leber.de> */
145 /* Reported by Stefan Werner <dustbln@gmx.de> */
152 /* Reported by Pete Zaitcev <zaitcev@redhat.com>, bz#176584 */
159 * Reported by Andrew Nayenko <relan@bk.ru>
168 /* Reported by Mario Rettig <mariorettig@web.de> */
[all …]
|
| /kernel/linux/linux-6.6/tools/testing/selftests/drivers/net/netdevsim/ |
| D | hw_stats_l3.sh | 202 check_err $? "$type stats not reported"
205 check_err $? "$type stats reported as used before either device or netdevsim request"
209 check_err $? "$type stats reported as used before device request"
211 check_err $? "$type stats reported as requested before device request"
215 check_err $? "$type stats reported as not used after both device and netdevsim request"
217 check_err $? "$type stats reported as not requested after device request"
221 check_err $? "$type stats reported as used after netdevsim request withdrawn"
225 check_err $? "$type stats reported as not used after netdevsim request reenabled"
229 check_err $? "$type stats reported as used after device request withdrawn"
231 check_err $? "$type stats reported as requested after device request withdrawn"
[all …]
|
| D | psample.sh | 75 check_err $? "Sampled packets reported with wrong group number"
106 check_err $? "Sampled packets reported with wrong in-ifindex"
109 check_err $? "Sampled packets reported with wrong out-ifindex"
115 check_err $? "Sampled packets reported with wrong out-tc"
121 check_fail $? "Sampled packets reported with out-tc when should not"
128 check_err $? "Sampled packets not reported with out-tc-occ when should"
134 check_fail $? "Sampled packets reported with out-tc-occ when should not"
140 check_err $? "Sampled packets not reported with latency when should"
146 check_fail $? "Sampled packets reported with latency when should not"
|
| /kernel/linux/linux-5.10/Documentation/ABI/testing/ |
| D | sysfs-bus-pci-devices-aer_stats | 5 statistical counters indicate the errors "as seen/reported by the device".
8 errors may be "seen" / reported by the link partner and not the
16 Description: List of correctable errors seen and reported by this
18 be reported using a single ERR_COR message, thus
37 Description: List of uncorrectable fatal errors seen and reported by this
39 be reported using a single ERR_FATAL message, thus
67 Description: List of uncorrectable nonfatal errors seen and reported by this
69 may be reported using a single ERR_FATAL message, thus
98 "reported to" the rootport. Please note that the rootports also transmit
107 Description: Total number of ERR_COR messages reported to rootport.
[all …]
|
| /kernel/linux/linux-6.6/Documentation/ABI/testing/ |
| D | sysfs-bus-pci-devices-aer_stats | 5 statistical counters indicate the errors "as seen/reported by the device".
8 errors may be "seen" / reported by the link partner and not the
16 Description: List of correctable errors seen and reported by this
18 be reported using a single ERR_COR message, thus
37 Description: List of uncorrectable fatal errors seen and reported by this
39 be reported using a single ERR_FATAL message, thus
67 Description: List of uncorrectable nonfatal errors seen and reported by this
69 may be reported using a single ERR_FATAL message, thus
98 "reported to" the rootport. Please note that the rootports also transmit
107 Description: Total number of ERR_COR messages reported to rootport.
[all …]
|
| /kernel/linux/linux-6.6/Documentation/input/ |
| D | gamepad.rst | 88 devices for _all_ reported events that you need. Otherwise, you will also get
111 If only 2 action-buttons are present, they are reported as BTN_SOUTH and
117 If only 3 action-buttons are present, they are reported as (from left
119 If the buttons are aligned perfectly vertically, they are reported as
125 different formations. If diamond-shaped, they are reported as BTN_NORTH,
136 both are reported.
138 - Digital buttons are reported as:
142 - Analog buttons are reported as:
150 The left analog-stick is reported as ABS_X, ABS_Y. The right analog stick is
151 reported as ABS_RX, ABS_RY. Zero, one or two sticks may be present.
[all …]
|
| /kernel/linux/linux-5.10/Documentation/input/ |
| D | gamepad.rst | 88 devices for _all_ reported events that you need. Otherwise, you will also get
111 If only 2 action-buttons are present, they are reported as BTN_SOUTH and
117 If only 3 action-buttons are present, they are reported as (from left
119 If the buttons are aligned perfectly vertically, they are reported as
125 different formations. If diamond-shaped, they are reported as BTN_NORTH,
136 both are reported.
138 - Digital buttons are reported as:
142 - Analog buttons are reported as:
150 The left analog-stick is reported as ABS_X, ABS_Y. The right analog stick is
151 reported as ABS_RX, ABS_RY. Zero, one or two sticks may be present.
[all …]
|
| /kernel/linux/linux-6.6/include/linux/ |
| D | fanotify.h | 78 * Events that can be reported with data type FSNOTIFY_EVENT_PATH.
79 * Note that FAN_MODIFY can also be reported with data type
86 * Directory entry modification events - reported only to directory
92 /* Events that can be reported with event->fd */
95 /* Events that can only be reported with data type FSNOTIFY_EVENT_INODE */
99 /* Events that can only be reported with data type FSNOTIFY_EVENT_ERROR */
111 /* Extra flags that may be reported with event or control handling of events */
114 /* Events that may be reported to user */
|
| /kernel/linux/linux-5.10/include/linux/ |
| D | fanotify.h | 41 * Events that can be reported with data type FSNOTIFY_EVENT_PATH.
42 * Note that FAN_MODIFY can also be reported with data type
49 * Directory entry modification events - reported only to directory
54 /* Events that can only be reported with data type FSNOTIFY_EVENT_INODE */
66 /* Extra flags that may be reported with event or control handling of events */
69 /* Events that may be reported to user */
|
| /kernel/linux/linux-6.6/lib/ |
| D | Kconfig.kcsan | 155 int "Duration in milliseconds, in which any given race is only reported once"
158 Any given race is only reported once in the defined time window.
164 # The main purpose of the below options is to control reported data races, and
174 reported if it was only possible to infer a race due to a data value
225 aligned writes up to word size will not be reported as data races;
227 will also not be reported.
235 writes will never be reported as a data race, however, will cause
239 reported.
243 be reported as data races; however, unlike that option, data races
244 due to two conflicting plain writes will be reported (aligned and
[all …]
|
| /kernel/linux/linux-5.10/Documentation/hwmon/ |
| D | ltc4261.rst | 43 Voltage readings provided by this driver are reported as obtained from the ADC
45 real voltage by multiplying the reported value with (R1+R2)/R2, where R1 is the
49 Current reading provided by this driver is reported as obtained from the ADC
50 Current Sense register. The reported value assumes that a 1 mOhm sense resistor
52 current by dividing the reported value by the sense resistor value in mOhm.
57 on all chip variants. To ensure that the alarm condition is reported to the user,
|
| D | ltc4260.rst | 43 Voltage readings provided by this driver are reported as obtained from the ADC
45 real voltage by multiplying the reported value with (R1+R2)/R2, where R1 is the
49 Current reading provided by this driver is reported as obtained from the ADC
50 Current Sense register. The reported value assumes that a 1 mOhm sense resistor
52 current by dividing the reported value by the sense resistor value in mOhm.
|
| /kernel/linux/linux-6.6/Documentation/hwmon/ |
| D | ltc4261.rst | 43 Voltage readings provided by this driver are reported as obtained from the ADC
45 real voltage by multiplying the reported value with (R1+R2)/R2, where R1 is the
49 Current reading provided by this driver is reported as obtained from the ADC
50 Current Sense register. The reported value assumes that a 1 mOhm sense resistor
52 current by dividing the reported value by the sense resistor value in mOhm.
57 on all chip variants. To ensure that the alarm condition is reported to the user,
|
| D | ltc4260.rst | 43 Voltage readings provided by this driver are reported as obtained from the ADC
45 real voltage by multiplying the reported value with (R1+R2)/R2, where R1 is the
49 Current reading provided by this driver is reported as obtained from the ADC
50 Current Sense register. The reported value assumes that a 1 mOhm sense resistor
52 current by dividing the reported value by the sense resistor value in mOhm.
|
| /kernel/linux/linux-5.10/lib/ |
| D | Kconfig.kcsan | 162 int "Duration in milliseconds, in which any given race is only reported once"
165 Any given race is only reported once in the defined time window.
171 # The main purpose of the below options is to control reported data races (e.g.
185 reported if it was only possible to infer a race due to a data value
205 aligned writes up to word size will not be reported as data races;
207 will also not be reported.
214 writes will never be reported as a data race, however, will cause
218 reported.
222 be reported as data races; however, unlike that option, data races
223 due to two conflicting plain writes will be reported (aligned and
|
| /kernel/linux/linux-5.10/drivers/dma-buf/ |
| D | st-dma-fence-chain.c | 200 pr_err("Reported %d for find_seqno(0)!\n", err); in find_seqno()
209 pr_err("Reported %d for find_seqno(%d:%d)!\n", in find_seqno()
214 pr_err("Incorrect fence reported by find_seqno(%d:%d)\n", in find_seqno()
224 pr_err("Error reported for finding self\n"); in find_seqno()
228 pr_err("Incorrect fence reported by find self\n"); in find_seqno()
237 pr_err("Error not reported for future fence: find_seqno(%d:%d)!\n", in find_seqno()
247 pr_err("Error reported for previous fence!\n"); in find_seqno()
251 pr_err("Incorrect fence reported by find_seqno(%d:%d)\n", in find_seqno()
279 pr_err("Reported %d for find_seqno()!\n", err); in find_signaled()
284 pr_err("Incorrect chain-fence.seqno:%lld reported for completed seqno:1\n", in find_signaled()
[all …]
|
| /kernel/linux/linux-6.6/drivers/dma-buf/ |
| D | st-dma-fence-chain.c | 196 pr_err("Reported %d for find_seqno(0)!\n", err); in find_seqno()
205 pr_err("Reported %d for find_seqno(%d:%d)!\n", in find_seqno()
210 pr_err("Incorrect fence reported by find_seqno(%d:%d)\n", in find_seqno()
220 pr_err("Error reported for finding self\n"); in find_seqno()
224 pr_err("Incorrect fence reported by find self\n"); in find_seqno()
233 pr_err("Error not reported for future fence: find_seqno(%d:%d)!\n", in find_seqno()
243 pr_err("Error reported for previous fence!\n"); in find_seqno()
247 pr_err("Incorrect fence reported by find_seqno(%d:%d)\n", in find_seqno()
275 pr_err("Reported %d for find_seqno()!\n", err); in find_signaled()
280 pr_err("Incorrect chain-fence.seqno:%lld reported for completed seqno:1\n", in find_signaled()
[all …]
|
| /kernel/linux/linux-5.10/drivers/net/wireless/ath/ath9k/ |
| D | dfs_debug.h | 28 * @pulses_total: pulses reported by HW
29 * @pulses_no_dfs: pulses wrongly reported as DFS
34 * @pri_phy_errors: pulses reported for primary channel
35 * @ext_phy_errors: pulses reported for extension channel
36 * @dc_phy_errors: pulses reported for primary + extension channel
|
| /kernel/linux/linux-6.6/drivers/net/wireless/ath/ath9k/ |
| D | dfs_debug.h | 28 * @pulses_total: pulses reported by HW
29 * @pulses_no_dfs: pulses wrongly reported as DFS
34 * @pri_phy_errors: pulses reported for primary channel
35 * @ext_phy_errors: pulses reported for extension channel
36 * @dc_phy_errors: pulses reported for primary + extension channel
|
| /kernel/linux/linux-6.6/tools/perf/pmu-events/arch/x86/graniterapids/ |
| D | memory.json | 10 … latency from first dispatch to completion is greater than 128 cycles. Reported latency may be lo…
22 …e latency from first dispatch to completion is greater than 16 cycles. Reported latency may be lo…
34 … latency from first dispatch to completion is greater than 256 cycles. Reported latency may be lo…
46 …e latency from first dispatch to completion is greater than 32 cycles. Reported latency may be lo…
58 …he latency from first dispatch to completion is greater than 4 cycles. Reported latency may be lo…
70 … latency from first dispatch to completion is greater than 512 cycles. Reported latency may be lo…
82 …e latency from first dispatch to completion is greater than 64 cycles. Reported latency may be lo…
94 …he latency from first dispatch to completion is greater than 8 cycles. Reported latency may be lo…
|
| /kernel/linux/linux-6.6/arch/sparc/kernel/ |
| D | sbus.c | 279 int reported, portid; in sysio_ue_handler() local
312 reported = 0; in sysio_ue_handler()
314 reported++; in sysio_ue_handler()
318 reported++; in sysio_ue_handler()
322 reported++; in sysio_ue_handler()
325 if (!reported) in sysio_ue_handler()
353 int reported, portid; in sysio_ce_handler() local
391 reported = 0; in sysio_ce_handler()
393 reported++; in sysio_ce_handler()
397 reported++; in sysio_ce_handler()
[all …]
|
| /kernel/linux/linux-5.10/arch/sparc/kernel/ |
| D | sbus.c | 278 int reported, portid; in sysio_ue_handler() local
311 reported = 0; in sysio_ue_handler()
313 reported++; in sysio_ue_handler()
317 reported++; in sysio_ue_handler()
321 reported++; in sysio_ue_handler()
324 if (!reported) in sysio_ue_handler()
352 int reported, portid; in sysio_ce_handler() local
390 reported = 0; in sysio_ce_handler()
392 reported++; in sysio_ce_handler()
396 reported++; in sysio_ce_handler()
[all …]
|