Searched refs:exceeded (Results 1 – 25 of 53) sorted by relevance
123
| /Linux-v4.19/Documentation/hwmon/ |
| D | ina209 | 43 in0_max_alarm shunt voltage max alarm limit exceeded
44 in0_min_alarm shunt voltage min alarm limit exceeded
45 in0_crit_max_alarm shunt voltage crit max alarm limit exceeded
46 in0_crit_min_alarm shunt voltage crit min alarm limit exceeded
56 in1_max_alarm bus voltage max alarm limit exceeded
57 in1_min_alarm bus voltage min alarm limit exceeded
58 in1_crit_max_alarm bus voltage crit max alarm limit exceeded
59 in1_crit_min_alarm bus voltage crit min alarm limit exceeded
66 power1_max_alarm power max alarm limit exceeded
67 power1_crit_alarm power crit alarm limit exceeded
|
| D | adm9240 | 164 0 +2.5 V_Error high or low limit exceeded
165 1 VCCP_Error high or low limit exceeded
166 2 +3.3 V_Error high or low limit exceeded
167 3 +5 V_Error high or low limit exceeded
169 6 FAN1_Error fan low limit exceeded
170 7 FAN2_Error fan low limit exceeded
171 8 +12 V_Error high or low limit exceeded
172 9 VCCP2_Error high or low limit exceeded
|
| D | ina3221 | 30 curr[123]_crit_alarm Critical alert current limit exceeded
34 curr[123]_max_alarm Warning alert current limit exceeded
|
| D | adm1026 | 43 limit. If the limit is exceeded, an interrupt (#SMBALERT) can be
45 limits for each sensor. If this limit is exceeded, the #THERM output will
51 corresponds to a minimum fan speed. If the limit is exceeded, an interrupt
|
| D | xgene-hwmon | 28 temp0_critical_alarm - An 1 would indicates on-die temperature exceeded threshold
|
| D | adt7410 | 35 exceeded, as well as a critical temperature (CT) pin to indicate that the
36 critical temperature set point has been exceeded. Both pins can be set up with a
|
| D | ds1621 | 55 stays high until the high limit is met or exceeded. On the other hand
66 The alarm bits are set when the high or low limits are met or exceeded and
72 any of the limits have ever been met or exceeded since last power-up or
|
| D | lm85 | 151 that can be used to signal the chipset in case a limit is exceeded or the
|
| /Linux-v4.19/fs/ceph/ |
| D | quota.c | 176 bool exceeded = false; in check_quota_exceeded() local
207 exceeded = (max && (rvalue >= max)); in check_quota_exceeded()
210 exceeded = (max && (rvalue + delta > max)); in check_quota_exceeded()
215 exceeded = true; in check_quota_exceeded()
221 exceeded = in check_quota_exceeded()
229 exceeded = true; /* Just break the loop */ in check_quota_exceeded()
234 if (exceeded || !next) in check_quota_exceeded()
243 return exceeded; in check_quota_exceeded()
|
| /Linux-v4.19/Documentation/filesystems/ |
| D | quota.txt | 43 - type of quota being exceeded (one of USRQUOTA, GRPQUOTA)
46 is being exceeded.
50 - what kind of limit is exceeded:
52 QUOTA_NL_ISOFTLONGWARN - inode softlimit is exceeded longer
56 QUOTA_NL_BSOFTLONGWARN - space (block) softlimit is exceeded
|
| D | ext2.txt | 220 count has been exceeded or if the maximum time between checks has been
221 exceeded.
|
| /Linux-v4.19/Documentation/ABI/testing/ |
| D | sysfs-class-led-flash | 59 has exceeded the limit specific to the flash controller
60 * flash-timeout-exceeded - the flash strobe was still on when
68 supply has exceeded the limit specific to the flash
79 * led-over-temperature - the temperature of the LED has exceeded
|
| /Linux-v4.19/Documentation/networking/ |
| D | xfrm_sync.txt | 92 when the replay sequence is exceeded.
153 is exceeded.
154 In such a case either XFRM_AE_CR (replay exceeded) or XFRM_AE_CE (timeout
|
| D | kcm.txt | 100 error when it is exceeded.
|
| /Linux-v4.19/Documentation/driver-api/iio/ |
| D | triggers.rst | 17 based on hardware generated events (e.g. data ready or threshold exceeded) or
|
| /Linux-v4.19/Documentation/acpi/apei/ |
| D | output_format.txt | 21 [primary][, containment warning][, reset][, threshold exceeded]\
|
| /Linux-v4.19/Documentation/filesystems/pohmelfs/ |
| D | info.txt | 26 If this timeout is exceeded, reading returns an error.
|
| /Linux-v4.19/drivers/gpu/drm/i915/ |
| D | Kconfig.debug | 166 is exceeded, even if there isn't an actual risk of missing
|
| /Linux-v4.19/drivers/mtd/ubi/ |
| D | Kconfig | 20 of UBI devices. When this threshold is exceeded, UBI starts performing
|
| /Linux-v4.19/Documentation/block/ |
| D | queue-sysfs.txt | 184 the target minimum read latency. If this latency is exceeded in a given
|
| /Linux-v4.19/Documentation/watchdog/ |
| D | watchdog-api.txt | 163 exceeded
|
| /Linux-v4.19/arch/powerpc/platforms/ |
| D | Kconfig | 251 to get notified the temp has exceeded a range. With this option off,
|
| /Linux-v4.19/drivers/staging/pi433/Documentation/ |
| D | pi433.txt | 181 If this value is exceeded, a reception cycle starts
|
| /Linux-v4.19/Documentation/laptops/ |
| D | laptop-mode.txt | 265 # exceeded, the kernel will wake flusher threads which will then reduce the
387 # exceeded, the kernel will wake flusher threads which will then reduce the
|
| /Linux-v4.19/Documentation/media/uapi/v4l/ |
| D | dev-overlay.rst | 232 exceeded are undefined. [#f3]_
|
123
