Home
last modified time | relevance | path

Searched refs:reported (Results 1 – 25 of 416) sorted by relevance

12345678910>>...17

/linux-6.1.9/arch/sparc/kernel/
Dsbus.c278 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 …]
Dpci_sabre.c203 int reported; in sabre_ue_intr() local
234 reported = 0; in sabre_ue_intr()
236 reported++; in sabre_ue_intr()
240 reported++; in sabre_ue_intr()
244 reported++; in sabre_ue_intr()
247 if (!reported) in sabre_ue_intr()
263 int reported; in sabre_ce_intr() local
297 reported = 0; in sabre_ce_intr()
299 reported++; in sabre_ce_intr()
303 reported++; in sabre_ce_intr()
[all …]
Dpci_psycho.c139 int reported; in psycho_ue_intr() local
170 reported = 0; in psycho_ue_intr()
172 reported++; in psycho_ue_intr()
176 reported++; in psycho_ue_intr()
180 reported++; in psycho_ue_intr()
183 if (!reported) in psycho_ue_intr()
218 int reported; in psycho_ce_intr() local
255 reported = 0; in psycho_ce_intr()
257 reported++; in psycho_ce_intr()
261 reported++; in psycho_ce_intr()
[all …]
Dpci_schizo.c379 int reported, limit; in schizo_ue_intr() local
424 reported = 0; in schizo_ue_intr()
426 reported++; in schizo_ue_intr()
430 reported++; in schizo_ue_intr()
433 if (!reported) in schizo_ue_intr()
467 int reported, limit; in schizo_ce_intr() local
516 reported = 0; in schizo_ce_intr()
518 reported++; in schizo_ce_intr()
522 reported++; in schizo_ce_intr()
525 if (!reported) in schizo_ce_intr()
[all …]
Dpsycho_common.c309 int reported; in psycho_pcierr_intr() local
338 reported = 0; in psycho_pcierr_intr()
340 reported++; in psycho_pcierr_intr()
344 reported++; in psycho_pcierr_intr()
348 reported++; in psycho_pcierr_intr()
352 reported++; in psycho_pcierr_intr()
355 if (!reported) in psycho_pcierr_intr()
/linux-6.1.9/Documentation/ABI/testing/
Dsysfs-bus-pci-devices-aer_stats5 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 …]
Dsysfs-class-fc_host6 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
Dsysfs-class-fc_remote_ports6 events recorded by the F_Port/Nx_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
Dsysfs-bus-css5 Description: Contains the subchannel type, as reported by the hardware.
12 Description: Contains the module alias as reported with uevents.
21 subchannel, as reported by the channel subsystem
31 Description: Contains the PIM/PAM/POM values, as reported by the
Dsysfs-bus-iio-dma-buffer11 multiple of the number reported by this file.
17 the alignment requirement reported in bytes by this property
Dsysfs-bus-papr-pmem12 the flags reported in this sysfs file:
44 reported on a new line with each line composed of a
46 dimm performance stats which are reported:
Dsysfs-mce31 subevent will not be reported.
53 (but some corrected errors might be still reported
88 All reported corrected errors will be cleared silently.
/linux-6.1.9/Documentation/hwmon/
Dltc4261.rst43 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,
Dltc4260.rst43 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.
Dltc2945.rst43 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.
Dltc4151.rst42 Voltage readings provided by this driver are reported as obtained from the ADIN
45 Current reading provided by this driver is reported as obtained from the Current
46 Sense register. The reported value assumes that a 1 mOhm sense resistor is
/linux-6.1.9/Documentation/input/
Dgamepad.rst88 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 …]
/linux-6.1.9/Documentation/devicetree/bindings/input/touchscreen/
Dtouchscreen.yaml14 description: minimum x coordinate reported
19 description: minimum y coordinate reported
24 description: horizontal resolution of touchscreen (maximum x coordinate reported + 1)
28 description: vertical resolution of touchscreen (maximum y coordinate reported + 1)
32 description: maximum reported pressure (arbitrary range dependent on the controller)
/linux-6.1.9/drivers/acpi/apei/
DKconfig30 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.
/linux-6.1.9/lib/
DKconfig.kcsan154 int "Duration in milliseconds, in which any given race is only reported once"
157 Any given race is only reported once in the defined time window.
163 # The main purpose of the below options is to control reported data races, and
173 reported if it was only possible to infer a race due to a data value
224 aligned writes up to word size will not be reported as data races;
226 will also not be reported.
234 writes will never be reported as a data race, however, will cause
238 reported.
242 be reported as data races; however, unlike that option, data races
243 due to two conflicting plain writes will be reported (aligned and
[all …]
/linux-6.1.9/Documentation/devicetree/bindings/serial/
Dsnps-dw-apb-uart.yaml84 always be reported as active instead of being obtained from the modem
91 always be reported as active instead of being obtained from the modem
98 always be reported as active instead of being obtained from the modem
105 be reported as inactive instead of being obtained from the modem status
/linux-6.1.9/Documentation/devicetree/bindings/arm/tegra/
Dnvidia,tegra194-cbb.yaml18 This driver handles errors due to illegal register accesses reported
26 SError or Data Abort is masked and the error is reported with interrupt.
29 errors due to illegal accesses from CCPLEX are reported by interrupts.
30 If ERD is not set, then error is reported by SError.
/linux-6.1.9/Documentation/input/devices/
Dntrig.rst16 This driver has been reported to work properly with multiple N-Trig devices
52 These nodes just provide easy access to the ranges reported by the device.
55 |sensor_logical_height, | the range for positions reported during activity |
77 obvious that these sensors were prone to erroneous events. Users reported
78 seeing both inappropriately dropped contact and ghosts, contacts reported
97 Time is measured in terms of the number of fingers reported, not frames since
/linux-6.1.9/Documentation/dev-tools/
Dkmemleak.rst8 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.
/linux-6.1.9/Documentation/networking/devlink/
Ddevlink-info.rst44 reported for two ports of the same device or on two hosts of
58 component identifiers or the board version reported in the PCI VPD.
62 should be reported as separate items.
81 Each version can be reported at most once in each version group. Firmware
86 ``/lib/firmware``) only the running version should be reported via
120 but it must not be reported if any of the components covered by the

12345678910>>...17