Home
last modified time | relevance | path

Searched full:reported (Results 1 – 25 of 1443) sorted by relevance

12345678910>>...58

/Linux-v5.4/drivers/usb/storage/
Dunusual_devs.h62 /* 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 …]
Dunusual_uas.h41 /* Reported-by: David Webb <djw@noc.ac.uk> */
48 /* Reported-by: Benjamin Tissoires <benjamin.tissoires@redhat.com> */
55 /* Reported-by: Tom Arild Naess <tanaess@gmail.com> */
62 /* Reported-by: Claudio Bizzarri <claudio.bizzarri@gmail.com> */
69 /* Reported-by: David Kozub <zub@linux.fjfi.cvut.cz> */
76 /* Reported-by: Hans de Goede <hdegoede@redhat.com> */
83 /* Reported-by: Icenowy Zheng <icenowy@aosc.io> */
90 /* Reported-by: Takeo Nakayama <javhera@gmx.com> */
97 /* Reported-by: Hans de Goede <hdegoede@redhat.com> */
104 /* Reported-by: Richard Henderson <rth@redhat.com> */
/Linux-v5.4/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-v5.4/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
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 …]
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
30 Description: Contains the PIM/PAM/POM values, as reported by the
/Linux-v5.4/include/linux/
Dfanotify.h39 * Events that can be reported with data type FSNOTIFY_EVENT_PATH.
40 * Note that FAN_MODIFY can also be reported with data type
47 * Directory entry modification events - reported only to directory
52 /* Events that can only be reported with data type FSNOTIFY_EVENT_INODE */
64 /* Extra flags that may be reported with event or control handling of events */
67 /* Events that may be reported to user */
Drmi.h25 * @clip_x_low - reported X coordinates below this setting will be clipped to
27 * @clip_x_high - reported X coordinates above this setting will be clipped to
29 * @clip_y_low - reported Y coordinates below this setting will be clipped to
31 * @clip_y_high - reported Y coordinates above this setting will be clipped to
33 * @offset_x - this value will be added to all reported X coordinates
34 * @offset_y - this value will be added to all reported Y coordinates
77 * @disable_report_mask - Force data to not be reported even if it is supported
/Linux-v5.4/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-v5.4/Documentation/devicetree/bindings/input/touchscreen/
Dtouchscreen.txt4 - 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
/Linux-v5.4/drivers/net/wireless/ath/ath9k/
Ddfs_debug.h28 * @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
/Linux-v5.4/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_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_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 …]
/Linux-v5.4/include/uapi/linux/
Dv4l2-subdev.h45 * @pad: pad number, as reported by the media API
58 * @pad: pad number, as reported by the media API
70 * @pad: pad number, as reported by the media API
85 * @pad: pad number, as reported by the media API
104 * @pad: pad number, as reported by the media API
115 * @pad: pad number, as reported by the media API
138 * @pad: pad number, as reported by the media API
/Linux-v5.4/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-v5.4/Documentation/dev-tools/
Dkmemleak.rst8 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.
/Linux-v5.4/drivers/misc/lkdtm/
Drefcount.c75 pr_warn("Weird: refcount_inc_not_zero() reported zero\n"); in lkdtm_REFCOUNT_INC_NOT_ZERO_OVERFLOW()
87 pr_warn("Weird: refcount_add_not_zero() reported zero\n"); in lkdtm_REFCOUNT_ADD_NOT_ZERO_OVERFLOW()
173 pr_warn("Weird: refcount_dec_and_test() reported zero\n"); in lkdtm_REFCOUNT_DEC_AND_TEST_NEGATIVE()
188 pr_warn("Weird: refcount_sub_and_test() reported zero\n"); in lkdtm_REFCOUNT_SUB_AND_TEST_NEGATIVE()
318 pr_warn("Weird: refcount_inc_not_zero() reported zero\n"); in lkdtm_REFCOUNT_INC_NOT_ZERO_SATURATED()
330 pr_warn("Weird: refcount_add_not_zero() reported zero\n"); in lkdtm_REFCOUNT_ADD_NOT_ZERO_SATURATED()
342 pr_warn("Weird: refcount_dec_and_test() reported zero\n"); in lkdtm_REFCOUNT_DEC_AND_TEST_SATURATED()
354 pr_warn("Weird: refcount_sub_and_test() reported zero\n"); in lkdtm_REFCOUNT_SUB_AND_TEST_SATURATED()
/Linux-v5.4/Documentation/devicetree/bindings/serial/
Dsnps-dw-apb-uart.yaml73 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
/Linux-v5.4/arch/sparc/include/asm/
Dbbc.h129 #define BBC_PSRC_FE0 0x0100 /* CPU 0 reported Fatal_Error */
130 #define BBC_PSRC_FE1 0x0200 /* CPU 1 reported Fatal_Error */
131 #define BBC_PSRC_FE2 0x0400 /* CPU 2 reported Fatal_Error */
132 #define BBC_PSRC_FE3 0x0800 /* CPU 3 reported Fatal_Error */
133 #define BBC_PSRC_FE4 0x1000 /* Schizo reported Fatal_Error */
134 #define BBC_PSRC_FE5 0x2000 /* Safari device 5 reported Fatal_Error */
135 #define BBC_PSRC_FE6 0x4000 /* CPMS reported Fatal_Error */
/Linux-v5.4/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-v5.4/drivers/input/rmi4/
Drmi_2d_sensor.h31 * @max_x - The maximum X coordinate that will be reported by this sensor.
32 * @max_y - The maximum Y coordinate that will be reported by this sensor.
34 * @data_pkt - buffer for data reported by this sensor.
/Linux-v5.4/tools/testing/selftests/kvm/x86_64/
Dvmx_dirty_log_test.c139 TEST_ASSERT(test_bit(0, bmap), "Page 0 incorrectly reported clean\n"); in main()
142 TEST_ASSERT(!test_bit(0, bmap), "Page 0 incorrectly reported dirty\n"); in main()
146 TEST_ASSERT(!test_bit(1, bmap), "Page 1 incorrectly reported dirty\n"); in main()
148 TEST_ASSERT(!test_bit(2, bmap), "Page 2 incorrectly reported dirty\n"); in main()

12345678910>>...58