Searched refs:exceeded (Results 1 – 25 of 52) sorted by relevance
123
| /Linux-v5.4/Documentation/hwmon/ |
| D | ina209.rst | 48 in0_max_alarm shunt voltage max alarm limit exceeded
49 in0_min_alarm shunt voltage min alarm limit exceeded
50 in0_crit_max_alarm shunt voltage crit max alarm limit exceeded
51 in0_crit_min_alarm shunt voltage crit min alarm limit exceeded
61 in1_max_alarm bus voltage max alarm limit exceeded
62 in1_min_alarm bus voltage min alarm limit exceeded
63 in1_crit_max_alarm bus voltage crit max alarm limit exceeded
64 in1_crit_min_alarm bus voltage crit min alarm limit exceeded
71 power1_max_alarm power max alarm limit exceeded
72 power1_crit_alarm power crit alarm limit exceeded
|
| D | adm9240.rst | 187 0 +2.5 V_Error high or low limit exceeded
188 1 VCCP_Error high or low limit exceeded
189 2 +3.3 V_Error high or low limit exceeded
190 3 +5 V_Error high or low limit exceeded
192 6 FAN1_Error fan low limit exceeded
193 7 FAN2_Error fan low limit exceeded
194 8 +12 V_Error high or low limit exceeded
195 9 VCCP2_Error high or low limit exceeded
|
| D | ina3221.rst | 38 curr[123]_crit_alarm Critical alert current limit exceeded
42 curr[123]_max_alarm Warning alert current limit exceeded
|
| D | adm1026.rst | 51 limit. If the limit is exceeded, an interrupt (#SMBALERT) can be
53 limits for each sensor. If this limit is exceeded, the #THERM output will
59 corresponds to a minimum fan speed. If the limit is exceeded, an interrupt
|
| D | xgene-hwmon.rst | 32 - An 1 would indicates on-die temperature exceeded threshold
|
| D | adt7410.rst | 54 exceeded, as well as a critical temperature (CT) pin to indicate that the
55 critical temperature set point has been exceeded. Both pins can be set up with a
|
| D | ds1621.rst | 74 stays high until the high limit is met or exceeded. On the other hand
85 The alarm bits are set when the high or low limits are met or exceeded and
91 any of the limits have ever been met or exceeded since last power-up or
|
| D | lm85.rst | 194 that can be used to signal the chipset in case a limit is exceeded or the
|
| /Linux-v5.4/fs/ceph/ |
| D | quota.c | 321 bool exceeded = false; in check_quota_exceeded() local
364 exceeded = (max && (rvalue >= max)); in check_quota_exceeded()
367 exceeded = (max && (rvalue + delta > max)); in check_quota_exceeded()
372 exceeded = true; in check_quota_exceeded()
378 exceeded = in check_quota_exceeded()
386 exceeded = true; /* Just break the loop */ in check_quota_exceeded()
392 if (exceeded || !next) in check_quota_exceeded()
402 return exceeded; in check_quota_exceeded()
|
| /Linux-v5.4/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 | 226 count has been exceeded or if the maximum time between checks has been
227 exceeded.
|
| /Linux-v5.4/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-v5.4/Documentation/media/uapi/v4l/ |
| D | ext-ctrls-flash.rst | 156 - Flash controller voltage to the flash LED has exceeded the limit
168 - Current in the LED power supply has exceeded the limit specific to
181 - The temperature of the LED has exceeded its allowed upper limit.
|
| /Linux-v5.4/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-v5.4/Documentation/driver-api/iio/ |
| D | triggers.rst | 17 based on hardware generated events (e.g. data ready or threshold exceeded) or
|
| /Linux-v5.4/Documentation/firmware-guide/acpi/apei/ |
| D | output_format.rst | 24 [primary][, containment warning][, reset][, threshold exceeded]\
|
| /Linux-v5.4/drivers/mtd/ubi/ |
| D | Kconfig | 21 of UBI devices. When this threshold is exceeded, UBI starts performing
|
| /Linux-v5.4/drivers/gpu/drm/i915/ |
| D | Kconfig.debug | 199 is exceeded, even if there isn't an actual risk of missing
|
| /Linux-v5.4/Documentation/watchdog/ |
| D | watchdog-api.rst | 178 exceeded:
|
| /Linux-v5.4/arch/powerpc/platforms/ |
| D | Kconfig | 232 to get notified the temp has exceeded a range. With this option off,
|
| /Linux-v5.4/scripts/ |
| D | spelling.txt | 534 exceded||exceeded
536 execeeded||exceeded
|
| /Linux-v5.4/Documentation/block/ |
| D | queue-sysfs.rst | 223 the target minimum read latency. If this latency is exceeded in a given
|
| /Linux-v5.4/drivers/staging/pi433/Documentation/ |
| D | pi433.txt | 181 If this value is exceeded, a reception cycle starts
|
| /Linux-v5.4/Documentation/admin-guide/laptops/ |
| D | laptop-mode.rst | 268 # exceeded, the kernel will wake flusher threads which will then reduce the
389 # exceeded, the kernel will wake flusher threads which will then reduce the
|
123
