| /openbmc/linux/drivers/usb/storage/ |
| H A 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 …]
|
| H A 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 …]
|
| /openbmc/linux/tools/testing/selftests/drivers/net/netdevsim/ |
| H A 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 …]
|
| H A 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"
|
| /openbmc/linux/Documentation/ABI/testing/ |
| H A 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 …]
|
| H A D | sysfs-bus-css | 4 Description: Contains the subchannel type, as reported by the hardware.
10 Description: Contains the module alias as reported with uevents.
18 subchannel, as reported by the channel subsystem
27 Description: Contains the PIM/PAM/POM values, as reported by the
|
| H A D | sysfs-class-fc_host | 6 events recorded by the F_Port, reported using fabric
14 events recorded by the F_Port/Nx_Port, reported using fabric
22 recorded by the F_Port/Nx_Port, reported using fabric
|
| /openbmc/linux/Documentation/input/ |
| H A 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 …]
|
| /openbmc/linux/include/linux/ |
| H A 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 */
|
| /openbmc/linux/lib/ |
| H A 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 …]
|
| /openbmc/linux/Documentation/hwmon/ |
| H A 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,
|
| H A 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.
|
| H A D | ltc2945.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.
|
| /openbmc/linux/drivers/dma-buf/ |
| H A 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 …]
|
| /openbmc/bmcweb/redfish-core/include/registries/ |
| H A D | telemetry_message_registry.hpp | 51 "Check the condition of the metric that reported the trigger.",
66 "Check the condition of the metric that reported the trigger.",
81 "Check the condition of the metric that reported the trigger.",
96 "Check the condition of the metric that reported the trigger.",
111 "Check the condition of the metric that reported the trigger.",
126 "Check the condition of the metric that reported the trigger.",
141 "Check the condition of the metric that reported the trigger.",
|
| /openbmc/linux/drivers/net/wireless/ath/ath9k/ |
| H A 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
|
| /openbmc/linux/tools/perf/pmu-events/arch/x86/graniterapids/ |
| H A 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…
|
| /openbmc/linux/arch/sparc/kernel/ |
| H A 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 …]
|
| /openbmc/linux/tools/perf/pmu-events/arch/x86/tigerlake/ |
| H A D | memory.json | 26 … latency from first dispatch to completion is greater than 128 cycles. Reported latency may be lo…
38 …e latency from first dispatch to completion is greater than 16 cycles. Reported latency may be lo…
50 … latency from first dispatch to completion is greater than 256 cycles. Reported latency may be lo…
62 …e latency from first dispatch to completion is greater than 32 cycles. Reported latency may be lo…
74 …he latency from first dispatch to completion is greater than 4 cycles. Reported latency may be lo…
86 … latency from first dispatch to completion is greater than 512 cycles. Reported latency may be lo…
98 …e latency from first dispatch to completion is greater than 64 cycles. Reported latency may be lo…
110 …he latency from first dispatch to completion is greater than 8 cycles. Reported latency may be lo…
|
| /openbmc/linux/drivers/acpi/apei/ |
| H A D | Kconfig | 30 errors are reported to firmware firstly, then reported to
40 PCIe AER errors may be reported via APEI firmware first mode.
52 Memory errors may be reported via APEI firmware first mode.
|
| /openbmc/linux/Documentation/devicetree/bindings/input/touchscreen/ |
| H A D | touchscreen.yaml | 21 description: minimum x coordinate reported
26 description: minimum y coordinate reported
31 description: horizontal resolution of touchscreen (maximum x coordinate reported + 1)
35 description: vertical resolution of touchscreen (maximum y coordinate reported + 1)
39 description: maximum reported pressure (arbitrary range dependent on the controller)
|
| /openbmc/linux/mm/ |
| H A D | page_reporting.c | 106 struct scatterlist *sgl, unsigned int nents, bool reported) in page_reporting_drain() argument
111 * Drain the now reported pages back into their respective in page_reporting_drain()
121 /* If the pages were not reported due to error skip flagging */ in page_reporting_drain()
122 if (!reported) in page_reporting_drain()
127 * consider the result to be "reported" since the page in page_reporting_drain()
184 /* We are going to skip over the reported pages. */ in page_reporting_cycle()
214 * Make the first non-reported page in the free list in page_reporting_cycle()
227 /* reset offset since the full list was reported */ in page_reporting_cycle()
236 /* flush reported pages from the sg list */ in page_reporting_cycle()
324 /* allocate scatterlist to store pages being reported on */ in page_reporting_process()
|
| /openbmc/linux/tools/perf/pmu-events/arch/x86/meteorlake/ |
| H A D | memory.json | 131 …latency from first dispatch to completion is greater than 1024 cycles. Reported latency may be lo…
144 … latency from first dispatch to completion is greater than 128 cycles. Reported latency may be lo…
157 …e latency from first dispatch to completion is greater than 16 cycles. Reported latency may be lo…
170 …latency from first dispatch to completion is greater than 2048 cycles. Reported latency may be lo…
183 … latency from first dispatch to completion is greater than 256 cycles. Reported latency may be lo…
196 …e latency from first dispatch to completion is greater than 32 cycles. Reported latency may be lo…
209 …he latency from first dispatch to completion is greater than 4 cycles. Reported latency may be lo…
222 … latency from first dispatch to completion is greater than 512 cycles. Reported latency may be lo…
235 …e latency from first dispatch to completion is greater than 64 cycles. Reported latency may be lo…
248 …he latency from first dispatch to completion is greater than 8 cycles. Reported latency may be lo…
|
| /openbmc/qemu/include/crypto/ |
| H A D | akcipher.h | 63 * @in_len: length of plaintext, less or equal to the size reported
66 * @out_len: length of ciphertext, less or equal to the size reported
83 * @in_len: the length of ciphertext, less or equal to the size reported
87 * reported by a call to qcrypto_akcipher_max_plaintext_len()
103 * @in_len: the length of data, less or equal to the size reported
123 * @in_len: length of signature, ess or equal to the size reported
|
| /openbmc/linux/Documentation/dev-tools/ |
| H A D | kmemleak.rst | 8 reported via /sys/kernel/debug/kmemleak. A similar method is used by the
39 objects to be reported as orphan.
61 marking all current reported unreferenced objects grey,
108 4. the remaining white objects are considered orphan and reported via
123 'clear' command to clear all reported unreferenced objects from the
183 reported by kmemleak because values found during the memory scanning
189 The false positives are objects wrongly reported as being memory leaks
195 Some of the reported leaks are only transient, especially on SMP
198 the minimum age of an object to be reported as a memory leak.
|