Home
last modified time | relevance | path

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

12345678910>>...57

/linux/drivers/usb/storage/
H A 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> */
55 /* Reported-by: Zhihong Zhou <zhouzhihong@greatwall.com.cn> */
62 /* Reported-by: Hongling Zeng <zenghongling@kylinos.cn> */
79 /* Reported-by: Tom Hu <huxiaoying@kylinos.cn> */
86 /* Reported-by: David Webb <djw@noc.ac.uk> */
93 /* Reported-by: Oliver Neukum <oneukum@suse.com> */
100 /* Reported-by: Benjamin Tissoires <benjamin.tissoires@redhat.com> */
107 /* Reported-by: Tom Arild Naess <tanaess@gmail.com> */
[all …]
/linux/tools/testing/selftests/drivers/net/netdevsim/
H A Dhw_stats_l3.sh202 check_err $? "$type stats not reported"
205 check_err $? "$type stats reported as used before either device or netdevsim request"
209 check_err $? "$type stats reported as used before device request"
211 check_err $? "$type stats reported as requested before device request"
215 check_err $? "$type stats reported as not used after both device and netdevsim request"
217 check_err $? "$type stats reported as not requested after device request"
221 check_err $? "$type stats reported as used after netdevsim request withdrawn"
225 check_err $? "$type stats reported as not used after netdevsim request reenabled"
229 check_err $? "$type stats reported as used after device request withdrawn"
231 check_err $? "$type stats reported as requested after device request withdrawn"
[all …]
H A Dpsample.sh75 check_err $? "Sampled packets reported with wrong group number"
106 check_err $? "Sampled packets reported with wrong in-ifindex"
109 check_err $? "Sampled packets reported with wrong out-ifindex"
115 check_err $? "Sampled packets reported with wrong out-tc"
121 check_fail $? "Sampled packets reported with out-tc when should not"
128 check_err $? "Sampled packets not reported with out-tc-occ when should"
134 check_fail $? "Sampled packets reported with out-tc-occ when should not"
140 check_err $? "Sampled packets not reported with latency when should"
146 check_fail $? "Sampled packets reported with latency when should not"
/linux/Documentation/ABI/testing/
H A Dsysfs-bus-pci-devices-aer5 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 …]
H A Dsysfs-bus-css4 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
H 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
H 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
/linux/include/linux/
H A Dfanotify.h78 * Events that can be reported with data type FSNOTIFY_EVENT_PATH.
79 * Note that FAN_MODIFY can also be reported with data type
86 * Directory entry modification events - reported only to directory
102 /* Events that can be reported with event->fd */
105 /* Events that can only be reported with data type FSNOTIFY_EVENT_INODE */
109 /* Events that can only be reported with data type FSNOTIFY_EVENT_ERROR */
120 /* Extra flags that may be reported with event or control handling of events */
123 /* Events that may be reported to user */
/linux/drivers/dma-buf/
H A Dst-dma-fence-chain.c194 pr_err("Reported %d for find_seqno(0)!\n", err); in find_seqno()
203 pr_err("Reported %d for find_seqno(%d:%d)!\n", in find_seqno()
208 pr_err("Incorrect fence reported by find_seqno(%d:%d)\n", in find_seqno()
218 pr_err("Error reported for finding self\n"); in find_seqno()
222 pr_err("Incorrect fence reported by find self\n"); in find_seqno()
231 pr_err("Error not reported for future fence: find_seqno(%d:%d)!\n", in find_seqno()
241 pr_err("Error reported for previous fence!\n"); in find_seqno()
245 pr_err("Incorrect fence reported by find_seqno(%d:%d)\n", in find_seqno()
273 pr_err("Reported %d for find_seqno()!\n", err); in find_signaled()
278 pr_err("Incorrect chain-fence.seqno:%lld reported for completed seqno:1\n", in find_signaled()
[all …]
/linux/Documentation/hwmon/
H 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,
H 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.
H 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.
/linux/arch/sparc/kernel/
H A Dsbus.c279 int reported, portid; in sysio_ue_handler() local
312 reported = 0; in sysio_ue_handler()
314 reported++; in sysio_ue_handler()
318 reported++; in sysio_ue_handler()
322 reported++; in sysio_ue_handler()
325 if (!reported) in sysio_ue_handler()
353 int reported, portid; in sysio_ce_handler() local
391 reported = 0; in sysio_ce_handler()
393 reported++; in sysio_ce_handler()
397 reported++; in sysio_ce_handler()
[all …]
H A Dpci_psycho.c141 int reported; in psycho_ue_intr() local
172 reported = 0; in psycho_ue_intr()
174 reported++; in psycho_ue_intr()
178 reported++; in psycho_ue_intr()
182 reported++; in psycho_ue_intr()
185 if (!reported) in psycho_ue_intr()
220 int reported; in psycho_ce_intr() local
257 reported = 0; in psycho_ce_intr()
259 reported++; in psycho_ce_intr()
263 reported++; in psycho_ce_intr()
[all …]
/linux/drivers/net/wireless/ath/ath9k/
H A 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/tools/perf/pmu-events/arch/x86/pantherlake/
H A Dmemory.json74 "PublicDescription": "Counts randomly selected loads when the latency from first dispatch to completion is greater than 1024 cycles. Reported latency may be longer than just the memory latency. Available PDIST counters: 0,1",
87 "PublicDescription": "Counts randomly selected loads when the latency from first dispatch to completion is greater than 128 cycles. Reported latency may be longer than just the memory latency. Available PDIST counters: 0,1",
100 "PublicDescription": "Counts randomly selected loads when the latency from first dispatch to completion is greater than 16 cycles. Reported latency may be longer than just the memory latency. Available PDIST counters: 0,1",
113 "PublicDescription": "Counts randomly selected loads when the latency from first dispatch to completion is greater than 2048 cycles. Reported latency may be longer than just the memory latency. Available PDIST counters: 0,1",
126 "PublicDescription": "Counts randomly selected loads when the latency from first dispatch to completion is greater than 256 cycles. Reported latency may be longer than just the memory latency. Available PDIST counters: 0,1",
139 "PublicDescription": "Counts randomly selected loads when the latency from first dispatch to completion is greater than 32 cycles. Reported latency may be longer than just the memory latency. Available PDIST counters: 0,1",
152 "PublicDescription": "Counts randomly selected loads when the latency from first dispatch to completion is greater than 4 cycles. Reported latency may be longer than just the memory latency. Available PDIST counters: 0,1",
165 "PublicDescription": "Counts randomly selected loads when the latency from first dispatch to completion is greater than 512 cycles. Reported latency may be longer than just the memory latency. Available PDIST counters: 0,1",
178 "PublicDescription": "Counts randomly selected loads when the latency from first dispatch to completion is greater than 64 cycles. Reported latency may be longer than just the memory latency. Available PDIST counters: 0,1",
191 "PublicDescription": "Counts randomly selected loads when the latency from first dispatch to completion is greater than 8 cycles. Reported latenc
[all...]
/linux/tools/perf/pmu-events/arch/x86/tigerlake/
H A Dmemory.json28 "PublicDescription": "Counts randomly selected loads when the latency from first dispatch to completion is greater than 128 cycles. Reported latency may be longer than just the memory latency.",
40 "PublicDescription": "Counts randomly selected loads when the latency from first dispatch to completion is greater than 16 cycles. Reported latency may be longer than just the memory latency.",
52 "PublicDescription": "Counts randomly selected loads when the latency from first dispatch to completion is greater than 256 cycles. Reported latency may be longer than just the memory latency.",
64 "PublicDescription": "Counts randomly selected loads when the latency from first dispatch to completion is greater than 32 cycles. Reported latency may be longer than just the memory latency.",
76 "PublicDescription": "Counts randomly selected loads when the latency from first dispatch to completion is greater than 4 cycles. Reported latency may be longer than just the memory latency.",
88 "PublicDescription": "Counts randomly selected loads when the latency from first dispatch to completion is greater than 512 cycles. Reported latency may be longer than just the memory latency.",
100 "PublicDescription": "Counts randomly selected loads when the latency from first dispatch to completion is greater than 64 cycles. Reported latency may be longer than just the memory latency.",
112 "PublicDescription": "Counts randomly selected loads when the latency from first dispatch to completion is greater than 8 cycles. Reported latency may be longer than just the memory latency.",
/linux/drivers/misc/lkdtm/
H A Drefcount.c67 pr_warn("Weird: refcount_inc_not_zero() reported zero\n"); in lkdtm_REFCOUNT_INC_NOT_ZERO_OVERFLOW()
79 pr_warn("Weird: refcount_add_not_zero() reported zero\n"); in lkdtm_REFCOUNT_ADD_NOT_ZERO_OVERFLOW()
165 pr_warn("Weird: refcount_dec_and_test() reported zero\n"); in lkdtm_REFCOUNT_DEC_AND_TEST_NEGATIVE()
180 pr_warn("Weird: refcount_sub_and_test() reported zero\n"); in lkdtm_REFCOUNT_SUB_AND_TEST_NEGATIVE()
195 pr_warn("Weird: refcount_sub_and_test() reported zero\n"); in lkdtm_REFCOUNT_SUB_AND_TEST_ZERO()
324 pr_warn("Weird: refcount_inc_not_zero() reported zero\n"); in lkdtm_REFCOUNT_INC_NOT_ZERO_SATURATED()
336 pr_warn("Weird: refcount_add_not_zero() reported zero\n"); in lkdtm_REFCOUNT_ADD_NOT_ZERO_SATURATED()
348 pr_warn("Weird: refcount_dec_and_test() reported zero\n"); in lkdtm_REFCOUNT_DEC_AND_TEST_SATURATED()
360 pr_warn("Weird: refcount_sub_and_test() reported zero\n"); in lkdtm_REFCOUNT_SUB_AND_TEST_SATURATED()
/linux/sound/soc/sof/
H A Dipc4-fw-reg.h16 * @stream_start_offset: Stream start offset (LPIB) reported by mixin
19 * (right after creation/after reset) value "(u64)-1" is reported
20 * @stream_end_offset: Stream end offset (LPIB) reported by mixin
23 * (right after creation or after reset) value "(u64)-1" is reported.
24 * When first data is mixed then value "0"is reported.
/linux/net/wireless/
H A Dcore.h602 * @bssid: BSSID of the reported AP
603 * @ssid: SSID of the reported AP
605 * @center_freq: frequency the reported AP is on
606 * @unsolicited_probe: the reported AP is part of an ESS, where all the APs
607 * that operate in the same channel as the reported AP and that might be
610 * @oct_recommended: OCT is recommended to exchange MMPDUs with the reported AP
611 * @same_ssid: the reported AP has the same SSID as the reporting AP
612 * @multi_bss: the reported AP is part of a multiple BSSID set
613 * @transmitted_bssid: the reported AP is the transmitting BSSID
614 * @colocated_ess: all the APs that share the same ESS as the reported A
[all...]
/linux/include/uapi/linux/
H A Dv4l2-subdev.h33 * @pad: pad number, as reported by the media API
49 * @pad: pad number, as reported by the media API
74 * @pad: pad number, as reported by the media API
95 * @pad: pad number, as reported by the media API
120 * @pad: pad number, as reported by the media API
136 * @pad: pad number, as reported by the media API
162 * @pad: pad number, as reported by the media API
/linux/Documentation/devicetree/bindings/arm/tegra/
H A Dnvidia,tegra194-cbb.yaml18 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.
/linux/arch/sparc/include/asm/
H A 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/tools/testing/selftests/net/forwarding/
H A Dbridge_mdb_max.sh568 check_err $? "Max groups on $locus should be 0, but $max reported"
574 check_err $? "Max groups expected to be 100, but $max reported"
664 check_err $? "$locus0: Max groups expected to be 0, but $max reported"
668 check_err $? "$locus2: Max groups expected to be 0, but $max reported"
675 check_err $? "$locus0: Max groups expected to be 0, but $max reported"
679 check_err $? "$locus2: Max groups expected to be 100, but $max reported"
686 check_err $? "$locus0: Max groups expected to be 100, but $max reported"
690 check_err $? "$locus2: Max groups expected to be 100, but $max reported"
697 check_err $? "$locus0: Max groups expected to be 100, but $max reported"
701 check_err $? "$locus2: Max groups expected to be 100, but $max reported"
[all …]
/linux/Documentation/input/devices/
H 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

12345678910>>...57