Home
last modified time | relevance | path

Searched +full:current +full:- +full:regulated (Results 1 – 19 of 19) sorted by relevance

/kernel/linux/linux-5.10/Documentation/devicetree/bindings/power/supply/
Dbq24190.txt1 TI BQ24190 Li-Ion Battery Charger
4 - compatible: contains one of the following:
9 - reg: integer, I2C address of the charger.
10 - interrupts[-extended]: configuration for charger INT pin.
13 - monitored-battery: phandle of battery characteristics devicetree node
15 + precharge-current-microamp: maximum charge current during precharge
17 + charge-term-current-microamp: a charge cycle terminates when the
18 battery voltage is above recharge threshold, and the current is below
21 - ti,system-minimum-microvolt: when power is connected and the battery is below
22 minimum system voltage, the system will be regulated above this setting.
[all …]
Dbq25890.txt1 Binding for TI bq25890 Li-Ion Charger
7 - compatible: Should contain one of the following:
12 - reg: integer, i2c address of the device.
13 - interrupts: interrupt line;
14 - ti,battery-regulation-voltage: integer, maximum charging voltage (in uV);
15 - ti,charge-current: integer, maximum charging current (in uA);
16 - ti,termination-current: integer, charge will be terminated when current in
17 constant-voltage phase drops below this value (in uA);
18 - ti,precharge-current: integer, maximum charge current during precharge
20 - ti,minimum-sys-voltage: integer, when battery is charging and it is below
[all …]
/kernel/linux/linux-5.10/Documentation/devicetree/bindings/leds/
Dleds-sgm3140.yaml1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/leds/leds-sgm3140.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Luca Weiss <luca@z3ntu.xyz>
13 The SGM3140 is a current-regulated charge pump which can regulate two current
17 http://www.sg-micro.com/uploads/soft/20190626/1561535688.pdf
23 enable-gpios:
27 flash-gpios:
31 vin-supply:
[all …]
/kernel/linux/linux-6.6/Documentation/devicetree/bindings/leds/
Dleds-sgm3140.yaml1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/leds/leds-sgm3140.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Luca Weiss <luca@z3ntu.xyz>
13 The SGM3140 is a current-regulated charge pump which can regulate two current
17 http://www.sg-micro.com/uploads/soft/20190626/1561535688.pdf
22 - ocs,ocp8110
23 - richtek,rt5033-led
24 - sgmicro,sgm3140
[all …]
/kernel/linux/linux-6.6/Documentation/devicetree/bindings/power/supply/
Dbq24190.yaml1 # SPDX-License-Identifier: GPL-2.0
4 ---
6 $schema: http://devicetree.org/meta-schemas/core.yaml#
8 title: TI BQ2419x Li-Ion Battery Charger
11 - Sebastian Reichel <sre@kernel.org>
14 - $ref: power-supply.yaml#
19 - ti,bq24190
20 - ti,bq24192
21 - ti,bq24192i
22 - ti,bq24196
[all …]
Drichtek,rt9467.yaml1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - ChiYuan Huang <cy_huang@richtek.com>
11 - ChiaEn Wu <chiaen_wu@richtek.com>
14 RT9467 is a switch-mode single cell Li-Ion/Li-Polymer battery charger for
16 MOSFETs, input current sensing and regulation, high-accuracy voltage
17 regulation, and charge termination. The charge current is regulated through
20 The RT9467 also features USB On-The-Go (OTG) support. It also integrates
21 D+/D- pin for USB host/charging port detection.
[all …]
Dbq25890.yaml1 # SPDX-License-Identifier: GPL-2.0
4 ---
6 $schema: http://devicetree.org/meta-schemas/core.yaml#
8 title: Bq25890, bq25892, bq25895 and bq25896 Li-Ion Charger
11 - Sebastian Reichel <sre@kernel.org>
14 - $ref: power-supply.yaml#
19 - enum:
20 - ti,bq25890
21 - items:
22 - enum:
[all …]
Dmediatek,mt6370-charger.yaml1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/power/supply/mediatek,mt6370-charger.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - ChiaEn Wu <chiaen_wu@richtek.com>
18 const: mediatek,mt6370-charger
34 - description: irq of "USB is plugged in"
35 - description: irq of "BC1.2 is done"
36 - description: irq of "Minimum Input Voltage Regulation loop is active"
38 interrupt-names:
[all …]
/kernel/linux/linux-6.6/Documentation/ABI/testing/
Dsysfs-bus-iio-chemical-sunrise-co222 - 'error_fatal': Analog front-end initialization error
23 - 'error_i2c': Read/write to non-existing register
24 - 'error_algorithm': Corrupted parameters
25 - 'error_calibration': Calibration has failed
26 - 'error_self_diagnostic': Internal interface failure
27 - 'error_out_of_range': Measured concentration out of scale
28 - 'error_memory': Error during memory operations
29 - 'error_no_measurement': Cleared at first measurement
30 - 'error_low_voltage': Sensor regulated voltage too low
31 - 'error_measurement_timeout': Unable to complete measurement
[all …]
/kernel/linux/linux-6.6/Documentation/hwmon/
Dq54sj108a2.rst1 .. SPDX-License-Identifier: GPL-2.0-or-later
12 Addresses scanned: -
14 …Datasheet: https://filecenter.delta-china.com.cn/products/download/01/0102/datasheet/DS_Q54SJ108A2…
21 -----------
24 Q54SJ108A2NCPG, and Q54SJ108A2NCPH 1/4 Brick DC/DC Regulated Power Module
32 -----------
34 This driver does not auto-detect devices. You will have to instantiate the
35 devices explicitly. Please see Documentation/i2c/instantiating-devices.rst for
40 -------------
43 curr1_alarm RO Output current alarm
[all …]
/kernel/linux/linux-6.6/Documentation/devicetree/bindings/regulator/
Dgpio-regulator.yaml1 # SPDX-License-Identifier: GPL-2.0
3 ---
4 $id: http://devicetree.org/schemas/regulator/gpio-regulator.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Liam Girdwood <lgirdwood@gmail.com>
11 - Mark Brown <broonie@kernel.org>
18 - $ref: regulator.yaml#
22 const: regulator-gpio
24 regulator-name: true
26 enable-gpios:
[all …]
/kernel/linux/linux-5.10/Documentation/devicetree/bindings/regulator/
Dgpio-regulator.yaml1 # SPDX-License-Identifier: GPL-2.0
3 ---
4 $id: http://devicetree.org/schemas/regulator/gpio-regulator.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Liam Girdwood <lgirdwood@gmail.com>
11 - Mark Brown <broonie@kernel.org>
18 - $ref: "regulator.yaml#"
22 const: regulator-gpio
24 regulator-name: true
26 enable-gpios:
[all …]
/kernel/linux/linux-5.10/Documentation/core-api/
Dworkqueue.rst33 thread system-wide. A single MT wq needed to keep around the same
60 * Use per-CPU unified worker pools shared by all wq to provide
83 called worker-pools.
85 The cmwq design differentiates between the user-facing workqueues that
87 which manages worker-pools and processes the queued work items.
89 There are two worker-pools, one for normal work items and the other
91 worker-pools to serve work items queued on unbound workqueues - the
102 When a work item is queued to a workqueue, the target worker-pool is
104 and appended on the shared worklist of the worker-pool. For example,
106 be queued on the worklist of either normal or highpri worker-pool that
[all …]
/kernel/linux/linux-6.6/Documentation/core-api/
Dworkqueue.rst33 thread system-wide. A single MT wq needed to keep around the same
60 * Use per-CPU unified worker pools shared by all wq to provide
83 called worker-pools.
85 The cmwq design differentiates between the user-facing workqueues that
87 which manages worker-pools and processes the queued work items.
89 There are two worker-pools, one for normal work items and the other
91 worker-pools to serve work items queued on unbound workqueues - the
102 When a work item is queued to a workqueue, the target worker-pool is
104 and appended on the shared worklist of the worker-pool. For example,
106 be queued on the worklist of either normal or highpri worker-pool that
[all …]
/kernel/linux/linux-5.10/Documentation/block/
Dqueue-sysfs.rst11 read-write.
14 ---------------
19 ------------------
21 For a RAID device (dm-raid), chunk_sectors indicates the size in 512B sectors
22 of the RAID volume stripe segment. For a zoned block device, either host-aware
23 or host-managed, chunk_sectors indicates the size in 512B sectors of the zones
28 --------
30 used by CPU-addressable storage to bypass the pagecache. It shows '1'
34 ------------------------
40 -------------------------
[all …]
/kernel/linux/linux-6.6/drivers/power/supply/
DKconfig1 # SPDX-License-Identifier: GPL-2.0-only
25 power supply device (current, voltage, temperature) to be
104 tristate "Active-semi ACT8945A charger driver"
108 Active-semi ActivePath ACT8945A charger.
158 tristate "DS2782/DS2786 standalone gas-gauge"
162 gas-gauge.
199 tristate "Sharp SL-5500 (collie) battery"
203 SL-5500 (collie) models.
214 called ingenic-battery.
233 Say Y to include support for SBS battery driver for SBS-compliant
[all …]
/kernel/linux/linux-6.6/Documentation/ABI/stable/
Dsysfs-block7 with 4KB physical sectors exposing 512-byte logical
58 integrity metadata. Set if the device is T10 PI-capable.
66 E.g. T10-DIF-TYPE1-CRC.
110 scanning is enabled, or "0" if not. The value type is a 32-bit
120 with 4KB physical sectors exposing 512-byte logical
149 Contact: linux-block@vger.kernel.org
160 of the disk. For a RAID device (dm-raid), chunk_sectors
162 segment. For a zoned block device, either host-aware or
163 host-managed, chunk_sectors indicates the size in 512B sectors
170 Contact: linux-block@vger.kernel.org
[all …]
/kernel/linux/linux-5.10/kernel/sched/
Dfair.c1 // SPDX-License-Identifier: GPL-2.0
55 * Targeted preemption latency for CPU-bound tasks:
58 * 'timeslice length' - timeslices in CFS are of variable length
59 * and have no persistent notion like in traditional, time-slice
63 * run vmstat and monitor the context-switches (cs) field)
71 * The initial- and re-scaling of tunables is configurable
75 * SCHED_TUNABLESCALING_NONE - unscaled, always *1
76 * SCHED_TUNABLESCALING_LOG - scaled logarithmical, *1+ilog(ncpus)
77 * SCHED_TUNABLESCALING_LINEAR - scaled linear, *ncpus
84 * Minimal preemption granularity for CPU-bound tasks:
[all …]
/kernel/linux/linux-6.6/kernel/sched/
Dfair.c1 // SPDX-License-Identifier: GPL-2.0
43 #include <linux/memory-tiers.h>
93 * Targeted preemption latency for CPU-bound tasks:
96 * 'timeslice length' - timeslices in CFS are of variable length
97 * and have no persistent notion like in traditional, time-slice
101 * run vmstat and monitor the context-switches (cs) field)
109 * The initial- and re-scaling of tunables is configurable
113 * SCHED_TUNABLESCALING_NONE - unscaled, always *1
114 * SCHED_TUNABLESCALING_LOG - scaled logarithmical, *1+ilog(ncpus)
115 * SCHED_TUNABLESCALING_LINEAR - scaled linear, *ncpus
[all …]