Searched refs:uA (Results 1 – 17 of 17) sorted by relevance
| /linux-4.4.14/drivers/leds/ |
| D | leds-wm8350.c | 145 int uA; in led_work() local
163 uA = (led->max_uA_index * led->value) / LED_FULL; in led_work()
165 BUG_ON(uA >= ARRAY_SIZE(isink_cur)); in led_work()
167 ret = regulator_set_current_limit(led->isink, isink_cur[uA], in led_work()
168 isink_cur[uA]); in led_work()
171 isink_cur[uA], ret); in led_work()
|
| /linux-4.4.14/Documentation/devicetree/bindings/power/ |
| D | bq25890.txt | 8 - ti,charge-current: integer, maximum charging current (in uA);
10 constant-voltage phase drops below this value (in uA);
12 phase (in uA);
18 (in uA).
|
| D | rt9455_charger.txt | 12 battery, in uA.
28 - richtek,avg-input-current-regulation: integer, input current value in uA drained by the
30 Default: 500000 uA (500mA)
|
| D | bq24257.txt | 14 - ti,charge-current: integer, maximum charging current in uA.
16 constant-voltage phase drops below this value (in uA).
25 (in uA). If this property is not specified, the input limit current is
|
| /linux-4.4.14/Documentation/devicetree/bindings/pinctrl/ |
| D | qcom,pmic-gpio.txt | 119 1: 30uA (PMIC_GPIO_PULL_UP_30)
120 2: 1.5uA (PMIC_GPIO_PULL_UP_1P5)
121 3: 31.5uA (PMIC_GPIO_PULL_UP_31P5)
122 4: 1.5uA + 30uA boost (PMIC_GPIO_PULL_UP_1P5_30)
123 If this property is ommited 30uA strength will be used if
|
| /linux-4.4.14/Documentation/devicetree/bindings/mfd/ |
| D | as3711.txt | 15 - su1-max-uA : maximum current
20 - su1-max-uA : maximum current
66 su2-max-uA = <36000>;
|
| D | max14577.txt | 23 - maxim,fast-charge-uamp : Current in uA for Fast Charge;
27 - maxim,eoc-uamp : Current in uA for End-Of-Charge mode;
|
| D | max77693.txt | 68 in uA (current from battery to system).
|
| /linux-4.4.14/Documentation/devicetree/bindings/regulator/ |
| D | qcom,spmi-regulator.txt | 149 0 = 0.05 uA
150 1 = 0.25 uA
151 2 = 0.55 uA
152 3 = 0.75 uA
|
| D | max77802.txt | 61 3: Low Power which reduces the quiescent current down to only 1uA
|
| D | regulator.txt | 43 - regulator-system-load: Load in uA present on regulator that is not captured by
|
| /linux-4.4.14/Documentation/devicetree/bindings/power_supply/ |
| D | qcom_smbb.txt | 45 Value type: <u32>; uA; range [100mA : 3A]
71 Value type: <u32>; uA; range [100mA : 3A]
90 Value type: <u32>; uA; range [100mA : 2.5A]
|
| /linux-4.4.14/drivers/staging/iio/Documentation/dac/ |
| D | max517 | 39 of the chip is activated, reducing the supply current to 4uA.
|
| /linux-4.4.14/drivers/regulator/ |
| D | wm8350-regulator.c | 907 static unsigned int get_mode(int uA, const struct wm8350_dcdc_efficiency *eff) in get_mode() argument
912 if (uA >= eff[i].uA_load_min && uA <= eff[i].uA_load_max) in get_mode()
|
| D | core.c | 530 int uA = 0; in regulator_total_uA_show() local
534 uA += regulator->uA_load; in regulator_total_uA_show()
536 return sprintf(buf, "%d\n", uA); in regulator_total_uA_show()
|
| /linux-4.4.14/Documentation/ABI/testing/ |
| D | sysfs-class-power | 129 than 1uA. Note that on some devices/systems this disconnects the battery
|
| /linux-4.4.14/arch/arm/boot/dts/ |
| D | imx6qdl-cubox-i.dtsi | 195 * leaving it as a pull-up, even if it is just 10uA.
|