Searched full:limit (Results 1 – 25 of 373) sorted by relevance
12345678910>>...15
| /Documentation/hwmon/ |
| D | ina209.rst | 44 in0_max shunt voltage max alarm limit (mV)
45 in0_min shunt voltage min alarm limit (mV)
46 in0_crit_max shunt voltage crit max alarm limit (mV)
47 in0_crit_min shunt voltage crit min alarm limit (mV)
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
57 in1_max bus voltage max alarm limit (mV)
58 in1_min bus voltage min alarm limit (mV)
[all …]
|
| D | adm9240.rst | 52 microprocessor-based systems, providing measurement and limit comparison
56 for limit comparisons can be programmed in over the same serial bus. The
58 analog channels to ensure a fast interrupt response to any out-of-limit
90 Temperature alarm is asserted once the temperature exceeds the high limit,
102 * User sets 0 to fan_min limit
108 * User sets fan_min limit too low
124 * User sets unreasonably high low fan speed limit
126 - resolution of the low speed limit may be reduced
187 0 +2.5 V_Error high or low limit exceeded
188 1 VCCP_Error high or low limit exceeded
[all …]
|
| D | lm77.rst | 25 and lower limit values.
31 the limit and its hysteresis is always the same for all 3 limits.
35 * When setting a limit, its hysteresis will automatically follow, the
36 difference staying unchanged. For example, if the old critical limit
38 the critical limit to 90 degrees C, then the hysteresis will
|
| D | adm1026.rst | 46 an analog output and a PWM output along with limit, alarm and mask bits for
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
58 in counts of a 22.5kHz internal clock. Each fan has a high limit which
59 corresponds to a minimum fan speed. If the limit is exceeded, an interrupt
66 crossed a programmable minimum or maximum limit. Note that minimum in this
90 register. Then set the low temperature limit in the tmin values for each
|
| D | bt1-pvt.rst | 92 temp1_min RW Low limit for temp input.
93 temp1_max RW High limit for temp input.
95 temperature input went below min limit,
98 temperature input went above max limit,
109 in[0-3]_min RW Low limit for voltage input.
110 in[0-3]_max RW High limit for voltage input.
112 voltage input went below min limit,
115 voltage input went above max limit,
|
| D | max16065.rst | 72 MAX16066, MAX16070, and MAX16071 support an additional limit which is
73 configurable as either low or high secondary limit. MAX16065, MAX16066,
103 in[0-11]_min Low warning limit.
107 in[0-11]_max High warning limit.
114 in[0-11]_lcrit Low critical limit.
116 in[0-11]_crit High critical limit.
|
| D | gl518sm.rst | 44 temperature is above the over temperature limit, and has not yet dropped
45 below the hysteresis limit. The alarm always reflects the current
50 triggered if the rotation speed has dropped below a programmable limit. In
60 maximum limit. Note that minimum in this case always means 'closest to
65 reading the current voltage of any input except for VIN3; limit setting and
|
| D | w83792d.rst | 64 triggered if the rotation speed has dropped below a programmable limit. Fan
70 or maximum limit.
148 exceeds the high limit (T+tolerance), the fan will be turned on with a
152 (1) If the temperature still exceeds the high limit, PWM duty
155 (2) If the temperature goes below the high limit, but still above the low
156 limit (T-tolerance), the fan speed will be fixed at the current speed because
159 (3) If the temperature goes below the low limit, PWM duty cycle will decrease
161 limit. (The preset stop value handling is not yet implemented in driver)
|
| D | emc1403.rst | 65 difference between the limit and its hysteresis is always the same for
70 * When setting a limit, its hysteresis will automatically follow, the
71 difference staying unchanged. For example, if the old critical limit
73 the critical limit to 90 degrees C, then the hysteresis will
|
| /Documentation/devicetree/bindings/power/supply/ |
| D | gpio-charger.yaml | 42 charge-current-limit-gpios:
47 charge-current-limit-mapping:
50 current limit.
55 Current limit in uA
58 charge-current-limit-gpios property. Bit 1 second to last
70 - charge-current-limit-gpios
73 charge-current-limit-gpios: [ charge-current-limit-mapping ]
74 charge-current-limit-mapping: [ charge-current-limit-gpios ]
89 charge-current-limit-gpios = <&gpioA 11 GPIO_ACTIVE_HIGH>,
91 charge-current-limit-mapping = <2500000 0x00>, // 2.5 A => both GPIOs low
|
| D | bq25980.yaml | 41 ti,sc-ovp-limit-microvolt:
43 Minimum input voltage limit in micro volts with a when the charger is in
49 ti,sc-ocp-limit-microamp:
51 Maximum input current limit in micro amps with a 100000 micro amp step.
55 ti,bypass-ovp-limit-microvolt:
57 Minimum input voltage limit in micro volts with a when the charger is in
62 ti,bypass-ocp-limit-microamp:
64 Maximum input current limit in micro amps with a 100000 micro amp step.
108 ti,sc-ocp-limit-microamp = <2000000>;
109 ti,sc-ovp-limit-microvolt = <17800000>;
|
| D | summit,smb347-charger.yaml | 55 summit,mains-current-limit-microamp:
58 summit,usb-current-limit-microamp:
69 description: Soft temperature limit compensation method
86 summit,mains-current-limit-microamp:
90 summit,usb-current-limit-microamp:
99 summit,mains-current-limit-microamp:
103 summit,usb-current-limit-microamp:
138 summit,mains-current-limit-microamp = <2000000>;
139 summit,usb-current-limit-microamp = <500000>;
|
| D | qcom_smbb.txt | 43 - qcom,fast-charge-current-limit:
51 Description: Battery voltage limit above which fast charging may operate;
58 Description: Battery voltage limit below which fast charging may operate;
74 'qcom,fast-charge-current-limit' will be clamped by this value.
79 Description: Battery voltage limit below which auto-recharge functionality
81 limit for auto-recharge is 5% above this value.
88 - qcom,dc-current-limit:
91 Description: Default DC charge current limit
145 qcom,fast-charge-current-limit = <1000000>;
146 qcom,dc-charge-current-limit = <1000000>;
|
| D | rohm,bd99954.yaml | 89 # - precharge-upper-limit-microvolt
91 # when battery voltage exceeds this limit voltage (3 in above chart)
100 # to the point where the battery voltage drops below this limit
102 # battery is expected to be faulty if battery voltage exceeds this limit.
126 description: system specific lower limit for system voltage.
131 rohm,vbus-input-current-limit-microamp:
132 description: system specific VBUS input current limit (in microamps).
137 rohm,vcc-input-current-limit-microamp:
138 description: system specific VCC/VACP input current limit (in microamps).
160 rohm,vbus-input-current-limit-microamp = <1472000>;
[all …]
|
| /Documentation/admin-guide/cgroup-v1/ |
| D | hugetlb.rst | 24 …hugetlb.<hugepagesize>.rsvd.limit_in_bytes # set/show limit of "hugepagesize" hugetlb r…
27 ….failcnt # show the number of allocation failure due to HugeTLB reservation limit
28 …hugetlb.<hugepagesize>.limit_in_bytes # set/show limit of "hugepagesize" hugetlb f…
31 …>.failcnt # show the number of allocation failure due to HugeTLB usage limit
69 The HugeTLB controller allows users to limit the HugeTLB usage (page fault) per
70 control group and enforces the limit during page fault. Since HugeTLB
71 doesn't support page reclaim, enforcing the limit at page fault time implies
73 pages beyond its limit. Therefore the application needs to know exactly how many
86 The HugeTLB controller allows to limit the HugeTLB reservations per control
87 group and enforces the controller limit at reservation time and at the fault of
[all …]
|
| D | pids.rst | 9 new tasks from being fork()'d or clone()'d after a certain limit is reached.
11 Since it is trivial to hit the task limit without hitting any kmemcg limits in
24 to have pids.current > pids.max. This can be done by either setting the limit to
30 To set a cgroup to have no limit, set pids.max to "max". This is the default for
32 limit in the hierarchy is followed).
39 - max: Number of times fork failed because limit was hit.
58 It should be noted that attempts to overcome the set limit (2 in this case) will
67 Even if we migrate to a child cgroup (which doesn't have a set limit), we will
68 not be able to overcome the most stringent limit in the hierarchy (in this case,
82 We can set a limit that is smaller than pids.current, which will stop any new
|
| D | rdma.rst | 19 RDMA controller allows user to limit RDMA/IB specific resources that a given
40 RDMA cgroup allows limit configuration of resources. Rdma cgroup maintains
68 (a) User sets the limit and no previous resource pool exist for the device
78 User should set all the limit to max value if it intents to remove/unconfigure
96 (a) Configure resource limit::
101 (b) Query resource limit::
115 (d) Delete resource limit::
|
| /Documentation/devicetree/bindings/iio/accel/ |
| D | lis302.txt | 30 - st,click-click-time-limit: click time limit, from 0 to 127.5msec
48 upper/lower limit
51 upper/lower limit for second wakeup
61 - st,{min,max}-limit-{x,y,z} set the min/max limits for x/y/z axis
112 st,min-limit-x = <120>;
113 st,min-limit-y = <120>;
114 st,min-limit-z = <140>;
115 st,max-limit-x = <550>;
116 st,max-limit-y = <550>;
117 st,max-limit-z = <750>;
|
| /Documentation/devicetree/bindings/leds/backlight/ |
| D | qcom-wled.yaml | 56 qcom,current-limit:
58 mA; per-string current limit.
65 qcom,current-limit-microamp:
67 uA; per-string current limit.
73 qcom,current-boost-limit:
75 mA; boost current limit.
87 V; Over-voltage protection limit.
95 Over-voltage protection limit. This property is for WLED4 only.
172 qcom,current-boost-limit:
190 qcom,current-boost-limit:
[all …]
|
| /Documentation/power/regulator/ |
| D | overview.rst | 14 current limit is controllable).
44 current limit. It only needs to enable or disable its
49 current limit to meet operation demands.
101 - regulator current output limit is 20mA @ 5V but is
110 - Domain-3 current limit is 0mA -> 20mA.
113 dynamically setting voltage or current limit levels.
124 Power Domain: is the new current limit within the domain
128 Regulator Domains: is the new current limit within the
146 get/set voltage, current limit, mode, enable and disable. This should
148 limit. This also compiles out if not in use so drivers can be reused in
|
| D | consumer.rst | 103 4. Regulator Current Limit Control & Status (dynamic drivers)
107 current limit to match system operating points. e.g. LCD backlight driver can
108 change the current limit to vary the backlight brightness, USB drivers may want
109 to set the limit to 500mA when supplying power.
111 Consumers can control their supply current limit by calling::
115 Where min_uA and max_uA are the minimum and maximum acceptable current limit in
120 when enabled, then the current limit changes instantly, otherwise the current
121 limit configuration changes and the current limit is physically set when the
124 A regulators current limit can be found by calling::
129 get_current_limit() will return the current limit whether the regulator
|
| /Documentation/ABI/testing/ |
| D | sysfs-class-led-flash | 60 has exceeded the limit specific to the flash controller
73 supply has exceeded the limit specific to the flash
80 LED has been below the minimum limit specific to
84 controller is below the limit under which strobing the
89 its allowed upper limit
|
| D | sysfs-block-zram | 6 which represents the limit on the *uncompressed* worth of data
57 The limit could be changed in run time and "0" means disable
58 the limit. No limit is the initial state. Unit: bytes
131 No limit "0" is the initial state.
138 amount of writeback ZRAM can do. The limit could be changed
|
| D | sysfs-bus-iio-counter-104-quad-8 | 21 normal, range limit, non-recycle, and modulo-n. The preset value
27 Range Limit:
28 An upper or lower limit is set, mimicking limit switches
29 in the mechanical counterpart. The upper limit is set to
30 the preset value, while the lower limit is set to 0. The
|
| /Documentation/filesystems/ |
| D | devpts.rst | 27 kernel.pty.max = 4096 - global limit
31 Per-instance limit could be set by adding mount option ``max=<count>``.
36 In kernels older than 3.4 sysctl ``kernel.pty.max`` works as per-instance limit.
|
12345678910>>...15