Home
last modified time | relevance | path

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

12345678910>>...108

/kernel/linux/linux-4.19/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.h31 /* Reported-by: Till Dörges <doerges@pre-sense.de> */
38 /* Reported-by: Julian Groß <julian.g@posteo.de> */
55 /* Reported-by: David Webb <djw@noc.ac.uk> */
62 /* Reported-by: Benjamin Tissoires <benjamin.tissoires@redhat.com> */
69 /* Reported-by: Tom Arild Naess <tanaess@gmail.com> */
76 /* Reported-by: Claudio Bizzarri <claudio.bizzarri@gmail.com> */
83 /* Reported-by: David Kozub <zub@linux.fjfi.cvut.cz> */
90 /* Reported-by: Thinh Nguyen <thinhn@synopsys.com> */
97 /* Reported-by: Hans de Goede <hdegoede@redhat.com> */
104 /* Reported-by: Icenowy Zheng <icenowy@aosc.io> */
[all …]
/kernel/linux/linux-5.10/drivers/usb/storage/
Dunusual_uas.h31 /* Reported-by: Till Dörges <doerges@pre-sense.de> */
39 * Initially Reported-by: Julian Groß <julian.g@posteo.de>
48 /* Reported-by: Julian Sikorski <belegdol@gmail.com> */
65 /* Reported-by: David Webb <djw@noc.ac.uk> */
72 /* Reported-by: Benjamin Tissoires <benjamin.tissoires@redhat.com> */
79 /* Reported-by: Tom Arild Naess <tanaess@gmail.com> */
86 /* Reported-by: Claudio Bizzarri <claudio.bizzarri@gmail.com> */
93 /* Reported-by: David Kozub <zub@linux.fjfi.cvut.cz> */
100 /* Reported-by: Thinh Nguyen <thinhn@synopsys.com> */
107 /* Reported-by: Thinh Nguyen <thinhn@synopsys.com> */
[all …]
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 …]
/kernel/linux/linux-5.10/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 …]
/kernel/linux/linux-4.19/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 …]
/kernel/linux/linux-5.10/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 …]
/kernel/linux/linux-4.19/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
/kernel/linux/linux-5.10/include/linux/
Dfanotify.h41 * Events that can be reported with data type FSNOTIFY_EVENT_PATH.
42 * Note that FAN_MODIFY can also be reported with data type
49 * Directory entry modification events - reported only to directory
54 /* Events that can only be reported with data type FSNOTIFY_EVENT_INODE */
66 /* Extra flags that may be reported with event or control handling of events */
69 /* Events that may be reported to user */
/kernel/linux/linux-4.19/Documentation/hwmon/
Dltc426137 Voltage readings provided by this driver are reported as obtained from the ADC
39 real voltage by multiplying the reported value with (R1+R2)/R2, where R1 is the
43 Current reading provided by this driver is reported as obtained from the ADC
44 Current Sense register. The reported value assumes that a 1 mOhm sense resistor
46 current by dividing the reported value by the sense resistor value in mOhm.
51 on all chip variants. To ensure that the alarm condition is reported to the user,
Dltc426037 Voltage readings provided by this driver are reported as obtained from the ADC
39 real voltage by multiplying the reported value with (R1+R2)/R2, where R1 is the
43 Current reading provided by this driver is reported as obtained from the ADC
44 Current Sense register. The reported value assumes that a 1 mOhm sense resistor
46 current by dividing the reported value by the sense resistor value in mOhm.
Dltc294537 Voltage readings provided by this driver are reported as obtained from the ADC
39 real voltage by multiplying the reported value with (R1+R2)/R2, where R1 is the
43 Current reading provided by this driver is reported as obtained from the ADC
44 Current Sense register. The reported value assumes that a 1 mOhm sense resistor
46 current by dividing the reported value by the sense resistor value in mOhm.
/kernel/linux/linux-5.10/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.
Dk10temp.rst123 the reported temperature (Tctl). Tdie is the real measured temperature, and
132 Core Complex Die (CCD) temperatures. Up to 8 such temperatures are reported
137 information. The following attributes may be reported.
147 Current values are raw (unscaled) as reported by the CPU. Core current is
148 reported as multiples of 1A / LSB. SoC is reported as multiples of 0.25A
149 / LSB. The real current is board specific. Reported currents should be seen
/kernel/linux/linux-5.10/lib/
DKconfig.kcsan162 int "Duration in milliseconds, in which any given race is only reported once"
165 Any given race is only reported once in the defined time window.
171 # The main purpose of the below options is to control reported data races (e.g.
185 reported if it was only possible to infer a race due to a data value
205 aligned writes up to word size will not be reported as data races;
207 will also not be reported.
214 writes will never be reported as a data race, however, will cause
218 reported.
222 be reported as data races; however, unlike that option, data races
223 due to two conflicting plain writes will be reported (aligned and
/kernel/linux/linux-5.10/drivers/dma-buf/
Dst-dma-fence-chain.c200 pr_err("Reported %d for find_seqno(0)!\n", err); in find_seqno()
209 pr_err("Reported %d for find_seqno(%d:%d)!\n", in find_seqno()
214 pr_err("Incorrect fence reported by find_seqno(%d:%d)\n", in find_seqno()
224 pr_err("Error reported for finding self\n"); in find_seqno()
228 pr_err("Incorrect fence reported by find self\n"); in find_seqno()
237 pr_err("Error not reported for future fence: find_seqno(%d:%d)!\n", in find_seqno()
247 pr_err("Error reported for previous fence!\n"); in find_seqno()
251 pr_err("Incorrect fence reported by find_seqno(%d:%d)\n", in find_seqno()
279 pr_err("Reported %d for find_seqno()!\n", err); in find_signaled()
284 pr_err("Incorrect chain-fence.seqno:%lld reported for completed seqno:1\n", in find_signaled()
[all …]
/kernel/linux/linux-4.19/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
/kernel/linux/linux-5.10/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
/kernel/linux/linux-4.19/arch/sparc/kernel/
Dsbus.c277 int reported, portid; in sysio_ue_handler() local
310 reported = 0; in sysio_ue_handler()
312 reported++; in sysio_ue_handler()
316 reported++; in sysio_ue_handler()
320 reported++; in sysio_ue_handler()
323 if (!reported) in sysio_ue_handler()
351 int reported, portid; in sysio_ce_handler() local
389 reported = 0; in sysio_ce_handler()
391 reported++; in sysio_ce_handler()
395 reported++; in sysio_ce_handler()
[all …]
/kernel/linux/linux-5.10/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 …]
/kernel/linux/linux-5.10/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)
/kernel/linux/linux-4.19/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
/kernel/linux/linux-5.10/mm/
Dpage_reporting.c69 struct scatterlist *sgl, unsigned int nents, bool reported) in page_reporting_drain() argument
74 * Drain the now reported pages back into their respective in page_reporting_drain()
84 /* If the pages were not reported due to error skip flagging */ in page_reporting_drain()
85 if (!reported) in page_reporting_drain()
90 * consider the result to be "reported" since the page in page_reporting_drain()
147 /* We are going to skip over the reported pages. */ in page_reporting_cycle()
177 * Make the first non-reported page in the free list in page_reporting_cycle()
190 /* reset offset since the full list was reported */ in page_reporting_cycle()
199 /* flush reported pages from the sg list */ in page_reporting_cycle()
287 /* allocate scatterlist to store pages being reported on */ in page_reporting_process()

12345678910>>...108