Searched full:limit (Results  1 – 25 of 464) sorted by relevance
12345678910>>...19
| /Documentation/devicetree/bindings/regulator/ | 
| D | regulator.yaml | 34   regulator-input-current-limit-microamp: 127     description: Set over current protection limit. This is a limit where 130       limit setting can be omitted. 133     description: Set over current error limit. This is a limit where part of 136       that detection should be enabled but limit setting can be omitted. 139     description: Set over current warning limit. This is a limit where hardware 140       is assumed still to be functional but approaching limit where it gets 143       be enabled but limit setting can be omitted. 146     description: Set over voltage protection limit. This is a limit where 149       limit setting can be omitted. Limit is given as microvolt offset from [all …] 
 | 
| /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
  | 
| /Documentation/ABI/testing/ | 
| D | sysfs-driver-intel-xe-hwmon | 5 Description:	RW. Card reactive sustained  (PL1) power limit in microwatts. 9 		exceeds this limit. A read value of 0 means that the PL1 10 		power limit is disabled, writing 0 disables the 11 		limit. Writing values > 0 and <= TDP will enable the power limit. 19 Description:	RO. Card default power limit (default TDP setting). 36 Description:	RW. Card sustained power limit interval (Tau in PL1/Tau) in 45 Description:	RW. Package reactive sustained  (PL1) power limit in microwatts. 49 		exceeds this limit. A read value of 0 means that the PL1 50 		power limit is disabled, writing 0 disables the 51 		limit. Writing values > 0 and <= TDP will enable the power limit. [all …] 
 | 
| D | sysfs-driver-intel-i915-hwmon | 13 Description:	RW. Card reactive sustained  (PL1/Tau) power limit in microwatts. 17 		exceeds this limit. A read value of 0 means that the PL1 18 		power limit is disabled, writing 0 disables the 19 		limit. Writing values > 0 will enable the power limit. 27 Description:	RO. Card default power limit (default TDP setting). 35 Description:	RW. Sustained power limit interval (Tau in PL1/Tau) in 44 Description:	RW. Card reactive critical (I1) power limit in microwatts. 46 		Card reactive critical (I1) power limit in microwatts is exposed 49 		this limit. 57 Description:	RW. Card reactive critical (I1) power limit in milliamperes. [all …] 
 | 
| 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
  | 
| /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 | 40   ti,sc-ovp-limit-microvolt: 42       Minimum input voltage limit in micro volts with a when the charger is in 48   ti,sc-ocp-limit-microamp: 50       Maximum input current limit in micro amps with a 100000 micro amp step. 54   ti,bypass-ovp-limit-microvolt: 56       Minimum input voltage limit in micro volts with a when the charger is in 61   ti,bypass-ocp-limit-microamp: 63       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 | x-powers,axp20x-usb-power-supply.yaml | 32   input-current-limit-microamp: 34       Optional value to clamp the maximum input current limit to for 53         input-current-limit-microamp: 65         input-current-limit-microamp: 76         input-current-limit-microamp: 87         input-current-limit-microamp: 100         input-current-limit-microamp:
  | 
| D | qcom,pm8941-charger.yaml | 43   qcom,fast-charge-current-limit: 54       Battery voltage limit in uV above which fast charging may operate; Defaults to 3.2V 62       Battery voltage limit in uV below which fast charging may operate; Defaults to 4.2V 81       setting this will harmlessly fail. The property 'qcom,fast-charge-current-limit' 89       Battery voltage limit in uV below which auto-recharge functionality will restart charging 90       after end-of-charge; The high cutoff limit for auto-recharge is 5% above this value. 100   qcom,dc-current-limit: 105       Default DC charge current limit in uA. Defaults to 100mA. 120   usb-charge-current-limit: 125       Default USB charge current limit in uA. [all …] 
 | 
| D | summit,smb347-charger.yaml | 55   summit,mains-current-limit-microamp: 58   summit,usb-current-limit-microamp: 69     description: Soft temperature limit compensation method 106         summit,mains-current-limit-microamp: 110         summit,usb-current-limit-microamp: 119         summit,mains-current-limit-microamp: 123         summit,usb-current-limit-microamp: 159             summit,mains-current-limit-microamp = <2000000>; 160             summit,usb-current-limit-microamp = <500000>;
  | 
| D | rohm,bd99954.yaml | 90 # - precharge-upper-limit-microvolt 92 #     when battery voltage exceeds this limit voltage (3 in above chart) 101 #     to the point where the battery voltage drops below this limit 103 #     battery is expected to be faulty if battery voltage exceeds this limit. 127     description: system specific lower limit for system voltage. 132   rohm,vbus-input-current-limit-microamp: 133     description: system specific VBUS input current limit (in microamps). 138   rohm,vcc-input-current-limit-microamp: 139     description: system specific VCC/VACP input current limit (in microamps). 161             rohm,vbus-input-current-limit-microamp = <1472000>; [all …] 
 | 
| D | bq256xx.yaml | 49   input-voltage-limit-microvolt: 51        Minimum input voltage limit in µV with a 100000 µV step 55   input-current-limit-microamp: 57        Maximum input current limit in µA with a 100000 µA step 123         input-voltage-limit-microvolt = <4500000>; 124         input-current-limit-microamp = <2400000>;
  | 
| /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 75 The HugeTLB controller allows users to limit the HugeTLB usage (page fault) per 76 control group and enforces the limit during page fault. Since HugeTLB 77 doesn't support page reclaim, enforcing the limit at page fault time implies 79 pages beyond its limit. Therefore the application needs to know exactly how many 94 The HugeTLB controller allows to limit the HugeTLB reservations per control 95 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 in the cgroup because limit was hit in 59 It should be noted that attempts to overcome the set limit (2 in this case) will 68 Even if we migrate to a child cgroup (which doesn't have a set limit), we will 69 not be able to overcome the most stringent limit in the hierarchy (in this case, 83 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 | 60   qcom,current-limit: 62       mA; per-string current limit. 69   qcom,current-limit-microamp: 71       uA; per-string current limit. 77   qcom,current-boost-limit: 79       mA; boost current limit. 91       V; Over-voltage protection limit. 99       Over-voltage protection limit. This property is for WLED4 only. 179         qcom,current-boost-limit: 200         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
  | 
        12345678910>>...19