Searched full:reported (Results 1 – 25 of 284) sorted by relevance
12345678910>>...12
| /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/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
38 Description: List of uncorrectable fatal errors seen and reported by this
40 be reported using a single ERR_FATAL message, thus
69 Description: List of uncorrectable nonfatal errors seen and reported by this
71 may be reported using a single ERR_FATAL message, thus
101 "reported to" the rootport. Please note that the rootports also transmit
110 Description: Total number of ERR_COR messages reported to rootport.
[all …]
|
| D | sysfs-bus-css | 5 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
30 Description: Contains the PIM/PAM/POM values, as reported by the
|
| D | sysfs-class-regulator | 24 the reported state is invalid.
324 This will be one of the same strings reported by
337 This will be one of the same strings reported by
350 This will be one of the same strings reported by
372 the reported state is invalid.
|
| /Documentation/devicetree/bindings/input/touchscreen/ |
| D | touchscreen.txt | 4 - touchscreen-min-x : minimum x coordinate reported (0 if not set)
5 - touchscreen-min-y : minimum y coordinate reported (0 if not set)
7 (maximum x coordinate reported + 1)
9 (maximum y coordinate reported + 1)
10 - touchscreen-max-pressure : maximum reported pressure (arbitrary range
|
| /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 | 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
|
| D | nct6683.rst | 31 Fan rotation speeds are reported in RPM (rotations per minute).
55 The driver has been reported to work with the following boards and
|
| D | nct6775.rst | 113 Fan rotation speeds are reported in RPM (rotations per minute). An alarm is
275 temperature measurement device. As a result, the temperature reported on CPUTIN
277 temperatures, and in some cases the reported temperature declines if the actual
280 boards. The CPU temperature on ASUS boards is reported from PECI 0.
|
| /Documentation/devicetree/bindings/serial/ |
| D | snps-dw-apb-uart.yaml | 73 always be reported as active instead of being obtained from the modem
80 always be reported as active instead of being obtained from the modem
87 always be reported as active instead of being obtained from the modem
94 be reported as inactive instead of being obtained from the modem status
|
| /Documentation/dev-tools/ |
| D | kmemleak.rst | 8 reported via /sys/kernel/debug/kmemleak. A similar method is used by the
40 objects to be reported as orphan.
62 marking all current reported unreferenced objects grey,
109 4. the remaining white objects are considered orphan and reported via
124 'clear' command to clear all reported unreferenced objects from the
185 reported by kmemleak because values found during the memory scanning
191 The false positives are objects wrongly reported as being memory leaks
197 Some of the reported leaks are only transient, especially on SMP
200 the minimum age of an object to be reported as a memory leak.
|
| /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
|
| D | bh1770glc.txt | 102 i.e. when proximity on has been reported.
106 i.e. when proximity off has been reported.
|
| /Documentation/admin-guide/ |
| D | rtc.rst | 14 the Gregorian calendar and 24 hour time, as reported by gmtime(3).
49 are reported by interrupt number 8. (Oh! So *that* is what IRQ 8 is
57 The interrupts are reported via /dev/rtc (major 10, minor 135, read only
61 the last read. Status information is reported through the pseudo-file
|
| /Documentation/devicetree/bindings/input/ |
| D | gpio-decoder.txt | 9 - decoder-max-value: Maximum possible value that can be reported by
|
| D | max77650-onkey.txt | 14 - linux,code: The key-code to be reported when the key is pressed.
|
| /Documentation/ABI/removed/ |
| D | sysfs-bus-nfit | 12 range. One of the capabilities that is reported is the 'Clear
|
| /Documentation/x86/x86_64/ |
| D | machinecheck.rst | 31 subevent will not be reported.
47 check errors (but some corrected errors might be still reported
|
12345678910>>...12