Home
last modified time | relevance | path

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

12345678910>>...16

/linux/arch/sparc/kernel/
A Dsbus.c311 reported = 0; in sysio_ue_handler()
313 reported++; in sysio_ue_handler()
317 reported++; in sysio_ue_handler()
321 reported++; in sysio_ue_handler()
390 reported = 0; in sysio_ce_handler()
392 reported++; in sysio_ce_handler()
396 reported++; in sysio_ce_handler()
400 reported++; in sysio_ce_handler()
465 reported++; in sysio_sbus_error_handler()
469 reported++; in sysio_sbus_error_handler()
[all …]
A 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 …]
A 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 …]
A Dpci_schizo.c424 reported = 0; in schizo_ue_intr()
426 reported++; in schizo_ue_intr()
430 reported++; in schizo_ue_intr()
518 reported++; in schizo_ce_intr()
522 reported++; in schizo_ce_intr()
695 reported++; in schizo_pcierr_intr()
699 reported++; in schizo_pcierr_intr()
703 reported++; in schizo_pcierr_intr()
707 reported++; in schizo_pcierr_intr()
711 reported++; in schizo_pcierr_intr()
[all …]
A 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/Documentation/ABI/testing/
A 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
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.
113 Description: Total number of ERR_FATAL messages reported to rootport.
[all …]
A 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
A 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
A 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
A 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:
A Dsysfs-bus-iio-dma-buffer11 multiple of the number reported by this file.
17 the alignment requirement reported in bytes by this property
/linux/Documentation/input/
A 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
136 both are reported.
138 - Digital buttons are reported as:
142 - Analog buttons are reported as:
151 reported as ABS_RX, ABS_RY. Zero, one or two sticks may be present.
164 or ABS_HAT1Y (left). Lower trigger buttons are reported as BTN_TR2 or
168 reported as "right" triggers (BTN_TR/ABS_HAT1X).
[all …]
/linux/Documentation/hwmon/
A 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,
A 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.
A 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.
A 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/Documentation/devicetree/bindings/input/touchscreen/
A 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/drivers/acpi/apei/
A 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/lib/
A DKconfig.kcsan165 int "Duration in milliseconds, in which any given race is only reported once"
168 Any given race is only reported once in the defined time window.
174 # The main purpose of the below options is to control reported data races, and
184 reported if it was only possible to infer a race due to a data value
213 aligned writes up to word size will not be reported as data races;
215 will also not be reported.
223 writes will never be reported as a data race, however, will cause
227 reported.
231 be reported as data races; however, unlike that option, data races
232 due to two conflicting plain writes will be reported (aligned and
[all …]
/linux/Documentation/devicetree/bindings/serial/
A Dsnps-dw-apb-uart.yaml76 always be reported as active instead of being obtained from the modem
83 always be reported as active instead of being obtained from the modem
90 always be reported as active instead of being obtained from the modem
97 be reported as inactive instead of being obtained from the modem status
/linux/Documentation/input/devices/
A 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/Documentation/dev-tools/
A 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
184 reported by kmemleak because values found during the memory scanning
190 The false positives are objects wrongly reported as being memory leaks
196 Some of the reported leaks are only transient, especially on SMP
199 the minimum age of an object to be reported as a memory leak.
/linux/Documentation/networking/devlink/
A 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
/linux/Documentation/devicetree/bindings/input/
A Diqs269a.yaml164 increasing or decreasing counts, thereby permitting events to be reported
282 Inverts the polarity of the states reported for proximity, touch and
374 Represents a proximity event reported by the channel in response to
379 that only events corresponding to a decrease in counts are reported
384 can be reported. Alternatively, specify 'azoteq,invert-enable' to in-
385 vert the polarity of the states reported by the channel.
407 description: Represents a touch event reported by the channel.
432 description: Represents a deep-touch event reported by the channel.
/linux/Documentation/devicetree/bindings/dma/
A Dimg-mdc-dma.txt14 The maximum burst size is this value multiplied by the hardware-reported bus
24 the number reported by the hardware is used.

Completed in 40 milliseconds

12345678910>>...16