Searched full:reported (Results 1 – 25 of 399) sorted by relevance
12345678910>>...16
| /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 …]
|
| 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
|
| D | sysfs-class-fc_remote_ports | 6 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
|
| 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
|
| D | sysfs-bus-iio-dma-buffer | 11 multiple of the number reported by this file.
17 the alignment requirement reported in bytes by this property
|
| D | sysfs-bus-papr-pmem | 12 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:
|
| D | sysfs-mce | 31 subevent will not be reported.
53 (but some corrected errors might be still reported
88 All reported corrected errors will be cleared silently.
|
| D | sysfs-class-power-ltc4162l | 5 Detailed charge status information as reported by the chip.
57 seconds, even when running on battery (as reported by the online
|
| /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 …]
|
| /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.
|
| 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.
|
| D | ltc4151.rst | 42 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
|
| D | smpro-hwmon.rst | 55 temp2_input millicelsius RO Max temperature reported among SoC VRDs
57 temp3_input millicelsius RO Max temperature reported among DIMM VRDs
58 temp4_input millicelsius RO Max temperature reported among Core VRDs
75 temp13_input millicelsius RO Max temperature reported among RCA VRDs
|
| D | adc128d818.rst | 41 caches the alarm status for each sensor until it is at least reported
42 once, to ensure that alarms are reported to user space.
|
| D | asb100.rst | 35 Temperatures are measured and reported in degrees Celsius.
37 Fan speeds are reported in RPM (rotations per minute). An alarm is
|
| /Documentation/devicetree/bindings/input/touchscreen/ |
| 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)
|
| /Documentation/devicetree/bindings/arm/tegra/ |
| D | nvidia,tegra194-cbb.yaml | 18 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.
|
| /Documentation/dev-tools/ |
| 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.
|
| /Documentation/networking/devlink/ |
| D | devlink-info.rst | 44 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
|
| /Documentation/devicetree/bindings/serial/ |
| D | snps-dw-apb-uart.yaml | 109 always be reported as active instead of being obtained from the modem
116 always be reported as active instead of being obtained from the modem
123 always be reported as active instead of being obtained from the modem
130 be reported as inactive instead of being obtained from the modem status
|
| /Documentation/input/devices/ |
| D | ntrig.rst | 16 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
|
| /Documentation/devicetree/bindings/dma/ |
| D | img-mdc-dma.txt | 14 The maximum burst size is this value multiplied by the hardware-reported bus
24 the number reported by the hardware is used.
|
| /Documentation/sound/designs/ |
| D | timestamping.rst | 33 When timestamps are enabled, the avail/delay information is reported
74 audio time it wants reported by selecting the relevant settings in
104 or reported as is (the latter being useful to compare progress of
115 The accuracy is reported in nanosecond units (using an unsigned 32-bit
127 The ALSA API only allows for a single audio timestamp to be reported
132 timestamp is reported. Applications that need different timestamps
|
| /Documentation/misc-devices/ |
| D | lis3lv02d.rst | 25 /sys/devices/platform/lis3lv02d. Reported values are scaled
74 For better compatibility between the various laptops. The values reported by
78 * When the laptop is horizontal the position reported is about 0 for X and Y
|
12345678910>>...16