Searched refs:exceeded (Results 1 – 25 of 58) sorted by relevance
123
| /kernel/linux/linux-5.10/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
54 curr4_crit_alarm Critical alert current limit exceeded for sum of
|
| 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
|
| /kernel/linux/linux-5.10/Documentation/filesystems/ |
| D | quota.rst | 46 - type of quota being exceeded (one of USRQUOTA, GRPQUOTA)
49 is being exceeded.
53 - what kind of limit is exceeded:
58 inode softlimit is exceeded longer
65 space (block) softlimit is exceeded
|
| D | ext2.rst | 230 count has been exceeded or if the maximum time between checks has been
231 exceeded.
|
| /kernel/linux/linux-5.10/fs/ceph/ |
| D | quota.c | 321 bool exceeded = false; in check_quota_exceeded() local
365 exceeded = (max && (rvalue + delta > max)); in check_quota_exceeded()
370 exceeded = true; in check_quota_exceeded()
376 exceeded = in check_quota_exceeded()
384 exceeded = true; /* Just break the loop */ in check_quota_exceeded()
390 if (exceeded || !next) in check_quota_exceeded()
400 return exceeded; in check_quota_exceeded()
|
| /kernel/linux/linux-5.10/Documentation/ABI/testing/ |
| D | sysfs-class-led-flash | 60 has exceeded the limit specific to the flash controller
61 * flash-timeout-exceeded
73 supply has exceeded the limit specific to the flash
88 the temperature of the LED has exceeded
|
| /kernel/linux/linux-5.10/Documentation/userspace-api/media/v4l/ |
| D | ext-ctrls-flash.rst | 149 - Flash controller voltage to the flash LED has exceeded the limit
161 - Current in the LED power supply has exceeded the limit specific to
174 - The temperature of the LED has exceeded its allowed upper limit.
|
| /kernel/linux/linux-5.10/Documentation/networking/ |
| D | xfrm_sync.rst | 102 when the replay sequence is exceeded.
172 is exceeded.
174 In such a case either XFRM_AE_CR (replay exceeded) or XFRM_AE_CE (timeout
|
| D | kcm.rst | 103 error when it is exceeded.
|
| /kernel/linux/linux-5.10/Documentation/driver-api/iio/ |
| D | triggers.rst | 15 based on hardware generated events (e.g. data ready or threshold exceeded) or
|
| /kernel/linux/patches/linux-5.10/imx8mm_patch/patches/drivers/ |
| D | 0026_linux_drivers_mailbox.patch | 285 - dev_err(priv->dev, "Maximal message size (%zu bytes) exceeded on TX; got: %i bytes\n", sizeof(*…
286 + dev_err(priv->dev, "Maximal message size (%u bytes) exceeded on TX; got: %i bytes\n", max_size,…
347 - dev_err(priv->dev, "Maximal message size (%zu bytes) exceeded on RX; got: %i bytes\n", sizeof(ms…
349 + dev_err(priv->dev, "Maximal message size (%u bytes) exceeded on RX; got: %i bytes\n", max_size, …
|
| /kernel/linux/linux-5.10/Documentation/firmware-guide/acpi/apei/ |
| D | output_format.rst | 24 [primary][, containment warning][, reset][, threshold exceeded]\
|
| /kernel/linux/linux-5.10/drivers/mtd/ubi/ |
| D | Kconfig | 21 of UBI devices. When this threshold is exceeded, UBI starts performing
|
| /kernel/linux/linux-5.10/kernel/sched/ |
| D | rt.c | 1048 int exceeded; in update_curr_rt() local
1053 exceeded = sched_rt_runtime_exceeded(rt_rq); in update_curr_rt()
1054 if (exceeded) in update_curr_rt()
1057 if (exceeded) in update_curr_rt()
|
| /kernel/linux/linux-5.10/drivers/gpu/drm/i915/ |
| D | Kconfig.debug | 200 is exceeded, even if there isn't an actual risk of missing
|
| /kernel/linux/linux-5.10/arch/powerpc/platforms/ |
| D | Kconfig | 220 to get notified the temp has exceeded a range. With this option off,
|
| /kernel/linux/linux-5.10/Documentation/watchdog/ |
| D | watchdog-api.rst | 178 exceeded:
|
| /kernel/linux/linux-5.10/scripts/ |
| D | spelling.txt | 570 exceded||exceeded
574 execeeded||exceeded
|
| /kernel/linux/linux-5.10/drivers/staging/pi433/Documentation/ |
| D | pi433.txt | 181 If this value is exceeded, a reception cycle starts
|
123