Searched +full:current +full:- +full:limit (Results 1 – 25 of 197) sorted by relevance
12345678
| /Documentation/devicetree/bindings/power/supply/ |
| D | gpio-charger.yaml | 1 # SPDX-License-Identifier: GPL-2.0
3 ---
4 $id: http://devicetree.org/schemas/power/supply/gpio-charger.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Sebastian Reichel <sre@kernel.org>
19 const: gpio-charger
21 charger-type:
23 - unknown
24 - battery
25 - ups
[all …]
|
| D | summit,smb347-charger.yaml | 1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
4 $id: "http://devicetree.org/schemas/power/supply/summit,smb347-charger.yaml#"
5 $schema: "http://devicetree.org/meta-schemas/core.yaml#"
10 - David Heidelberg <david@ixit.cz>
11 - Dmitry Osipenko <digetx@gmail.com>
16 - summit,smb345
17 - summit,smb347
18 - summit,smb358
26 monitored-battery:
[all …]
|
| D | rohm,bd99954.yaml | 1 # SPDX-License-Identifier: GPL-2.0-only OR BSD-2-Clause
3 ---
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Matti Vaittinen <matti.vaittinen@fi.rohmeurope.com>
11 - Markus Laine <markus.laine@fi.rohmeurope.com>
12 - Mikko Mutanen <mikko.mutanen@fi.rohmeurope.com>
15 The ROHM BD99954 is a Battery Management LSI for 1-4 cell Lithium-Ion
16 secondary battery intended to be used in space-constraint equipment such
18 provides a Dual-source Battery Charger, two port BC1.2 detection and a
28 # Curve (1) represents charging current.
[all …]
|
| D | bq25980.yaml | 1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
4 ---
6 $schema: "http://devicetree.org/meta-schemas/core.yaml#"
11 - Dan Murphy <dmurphy@ti.com>
12 - Ricardo Rivera-Matos <r-rivera-matos@ti.com>
16 for use in high-power density portable electronics. These inductorless
21 - $ref: power-supply.yaml#
26 - ti,bq25980
27 - ti,bq25975
28 - ti,bq25960
[all …]
|
| D | qcom_smbb.txt | 1 Qualcomm Switch-Mode Battery Charger and Boost
4 - compatible:
8 - "qcom,pm8941-charger"
10 - reg:
12 Value type: <prop-encoded-array>
15 - interrupts:
17 Value type: <prop-encoded-array>
21 - charge done
22 - charge fast mode
23 - charge trickle mode
[all …]
|
| D | bq24257.txt | 1 Binding for TI bq24250/bq24251/bq24257 Li-Ion Charger
4 - compatible: Should contain one of the following:
8 - reg: integer, i2c address of the device.
9 - interrupts: Interrupt mapping for GPIO IRQ (configure for both edges). Use in
10 conjunction with "interrupt-parent".
11 - ti,battery-regulation-voltage: integer, maximum charging voltage in uV.
12 - ti,charge-current: integer, maximum charging current in uA.
13 - ti,termination-current: integer, charge will be terminated when current in
14 constant-voltage phase drops below this value (in uA).
17 - pg-gpios: GPIO used for connecting the bq2425x device PG (Power Good) pin.
[all …]
|
| D | bq2415x.txt | 1 Binding for TI bq2415x Li-Ion Charger
4 - compatible: Should contain one of the following:
17 - reg: integer, i2c address of the device.
18 - ti,current-limit: integer, initial maximum current charger can pull
20 - ti,weak-battery-voltage: integer, weak battery voltage threshold in mV.
23 - ti,battery-regulation-voltage: integer, maximum charging voltage in mV.
24 - ti,charge-current: integer, maximum charging current in mA.
25 - ti,termination-current: integer, charge will be terminated when current in
26 constant-voltage phase drops below this value (in mA).
27 - ti,resistor-sense: integer, value of sensing resistor in milliohm.
[all …]
|
| D | battery.yaml | 1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Sebastian Reichel <sre@kernel.org>
14 In smart batteries, these are typically stored in non-volatile memory
16 no appropriate non-volatile memory, or it is unprogrammed/incorrect.
27 Batteries must be referenced by chargers and/or fuel-gauges using a phandle.
28 The phandle's property should be named "monitored-battery".
32 const: simple-battery
34 over-voltage-threshold-microvolt:
[all …]
|
| D | max77650-charger.yaml | 1 # SPDX-License-Identifier: GPL-2.0
3 ---
4 $id: http://devicetree.org/schemas/power/supply/max77650-charger.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Bartosz Golaszewski <bgolaszewski@baylibre.com>
16 The charger is represented as a sub-node of the PMIC node on the device tree.
20 const: maxim,max77650-charger
22 input-voltage-min-microvolt:
28 input-current-limit-microamp:
30 CHGIN input current limit (in microamps).
[all …]
|
| /Documentation/admin-guide/cgroup-v1/ |
| D | pids.rst | 6 --------
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
17 -----
21 number of processes currently in the cgroup is given by pids.current.
24 to have pids.current > pids.max. This can be done by either setting the limit to
25 be smaller than pids.current, or attaching enough processes to the cgroup such
26 that pids.current > pids.max. However, it is not possible to violate a cgroup
27 policy through fork() or clone(). fork() and clone() will return -EAGAIN if the
30 To set a cgroup to have no limit, set pids.max to "max". This is the default for
[all …]
|
| D | hugetlb.rst | 7 # mount -t cgroup -o hugetlb none /sys/fs/cgroup
19 The above steps create a new group g1 and move the current shell
24 …hugetlb.<hugepagesize>.rsvd.limit_in_bytes # set/show limit of "hugepagesize" hugetlb r…
25 …rsvd.max_usage_in_bytes # show max "hugepagesize" hugetlb reservations and no-reserve faults
26 …hugetlb.<hugepagesize>.rsvd.usage_in_bytes # show current reservations and no-reserve f…
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…
30 …hugetlb.<hugepagesize>.usage_in_bytes # show current usage for "hugepagesize" huge…
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
[all …]
|
| /Documentation/power/regulator/ |
| D | overview.rst | 2 Linux voltage and current regulator framework
9 voltage and current regulators.
13 regulators (where voltage output is controllable) and current sinks (where
14 current limit is controllable).
26 - Regulator
27 - Electronic device that supplies power to other devices.
29 some can control their output voltage and or current.
31 Input Voltage -> Regulator -> Output Voltage
34 - PMIC
35 - Power Management IC. An IC that contains numerous
[all …]
|
| 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
[all …]
|
| /Documentation/devicetree/bindings/leds/backlight/ |
| D | qcom-wled.yaml | 1 # SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/leds/backlight/qcom-wled.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Bjorn Andersson <bjorn.andersson@linaro.org>
11 - Kiran Gunda <kgunda@codeaurora.org>
21 - qcom,pm8941-wled
22 - qcom,pmi8998-wled
23 - qcom,pm660l-wled
24 - qcom,pm8150l-wled
[all …]
|
| D | sky81452-backlight.txt | 1 SKY81452-backlight bindings
4 - compatible : Must be "skyworks,sky81452-backlight"
7 - name : Name of backlight device. Default is 'lcd-backlight'.
8 - gpios : GPIO to use to EN pin.
10 - led-sources : List of enabled channels from 0 to 5.
12 - skyworks,ignore-pwm : Ignore both PWM input
13 - skyworks,dpwm-mode : Enable DPWM dimming mode, otherwise Analog dimming.
14 - skyworks,phase-shift : Enable phase shift mode
15 - skyworks,short-detection-threshold-volt
17 - skyworks,current-limit-mA
[all …]
|
| /Documentation/hwmon/ |
| D | ina209.rst | 6 * Burr-Brown / Texas Instruments INA209
10 Addresses scanned: -
16 - Paul Hays <Paul.Hays@cattail.ca>
17 - Ira W. Snyder <iws@ovro.caltech.edu>
18 - Guenter Roeck <linux@roeck-us.net>
22 -----------
24 The TI / Burr-Brown INA209 monitors voltage, current, and power on the high side
27 calibration multiplier to scale the displayed current and power values.
31 -------------
44 in0_max shunt voltage max alarm limit (mV)
[all …]
|
| D | max16065.rst | 11 Addresses scanned: -
15 http://datasheets.maxim-ic.com/en/ds/MAX16065-MAX16066.pdf
21 Addresses scanned: -
25 http://datasheets.maxim-ic.com/en/ds/MAX16067.pdf
31 Addresses scanned: -
35 http://datasheets.maxim-ic.com/en/ds/MAX16068.pdf
41 Addresses scanned: -
45 http://datasheets.maxim-ic.com/en/ds/MAX16070-MAX16071.pdf
47 Author: Guenter Roeck <linux@roeck-us.net>
51 -----------
[all …]
|
| D | ina3221.rst | 10 Addresses: I2C 0x40 - 0x43
19 -----------
21 The Texas Instruments INA3221 monitors voltage, current, and power on the high
23 and supply voltage, with programmable conversion times and averaging, current
24 and power are calculated host-side from these.
27 -------------
33 curr[123]_input Current(mA) measurement channels
35 curr[123]_crit Critical alert current(mA) setting, activates the
36 corresponding alarm when the respective current
38 curr[123]_crit_alarm Critical alert current limit exceeded
[all …]
|
| D | gl518sm.rst | 21 - Frodo Looijaard <frodol@dds.nl>,
22 - Kyösti Mälkki <kmalkki@cc.hut.fi>
23 - Hong-Gunn Chew <hglinux@gunnet.org>
24 - Jean Delvare <jdelvare@suse.de>
27 -----------
44 temperature is above the over temperature limit, and has not yet dropped
45 below the hysteresis limit. The alarm always reflects the current
46 situation. Measurements are guaranteed between -10 degrees and +110
47 degrees, with a accuracy of +/-3 degrees.
50 triggered if the rotation speed has dropped below a programmable limit. In
[all …]
|
| D | adm1026.rst | 16 - Philip Pokorny <ppokorny@penguincomputing.com> for Penguin Computing
17 - Justin Thiessen <jthiessen@penguincomputing.com>
20 -----------------
23 List of GPIO pins (0-16) to program as inputs
26 List of GPIO pins (0-16) to program as outputs
29 List of GPIO pins (0-16) to program as inverted
32 List of GPIO pins (0-16) to program as normal/non-inverted
35 List of GPIO pins (0-7) to program as fan tachs
39 -----------
45 16 general purpose digital I/O lines, eight (8) fan speed sensors (8-bit),
[all …]
|
| D | inspur-ipsps1.rst | 1 Kernel driver inspur-ipsps1
11 -----------
17 -----------
19 This driver does not auto-detect devices. You will have to instantiate the
20 devices explicitly. Please see Documentation/i2c/instantiating-devices.rst for
24 -------------
29 curr1_input Measured input current
31 curr1_max Maximum current
32 curr1_max_alarm Current high alarm
33 curr2_input Measured output current in mA.
[all …]
|
| /Documentation/ABI/testing/ |
| D | sysfs-class-led-flash | 55 Flash faults are re-read after strobing the flash. Possible
58 * led-over-voltage
60 has exceeded the limit specific to the flash controller
61 * flash-timeout-exceeded
65 * controller-over-temperature
68 * controller-short-circuit
71 * led-power-supply-over-current
72 current in the LED power
73 supply has exceeded the limit specific to the flash
75 * indicator-led-fault
[all …]
|
| D | sysfs-class-power | 5 Contact: linux-pm@vger.kernel.org
14 Contact: linux-pm@vger.kernel.org
23 Contact: linux-pm@vger.kernel.org
32 Contact: linux-pm@vger.kernel.org
43 Contact: linux-pm@vger.kernel.org
47 Reports an average IBAT current reading for the battery, over
54 Reports an average IBUS current reading over a fixed period.
62 batteries and for USB IBUS current.
66 Contact: linux-pm@vger.kernel.org
70 Reports the maximum IBAT current allowed into the battery.
[all …]
|
| D | sysfs-class-regulator | 20 supplying power to the system (unless some non-Linux
33 "status". This reports the current regulator status, for
38 - off
39 - on
40 - error
41 - fast
42 - normal
43 - idle
44 - standby
52 "error" indicates an out-of-regulation status such as being
[all …]
|
| /Documentation/power/ |
| D | power_supply_class.rst | 8 properties to user-space.
60 +--------------------------------------------------------------------------+
61 | **Charge/Energy/Capacity - how to not confuse** |
62 +--------------------------------------------------------------------------+
66 | - `CHARGE_*` |
68 | - `ENERGY_*` |
70 | - `CAPACITY` |
72 +--------------------------------------------------------------------------+
122 Reports the current measured during boot
140 the current charge counter (in µAh). This could easily
[all …]
|
12345678