Home
last modified time | relevance | path

Searched +full:fuel +full:- +full:gauge (Results 1 – 25 of 91) sorted by relevance

1234

/linux/drivers/power/supply/
H A DKconfig1 # SPDX-License-Identifier: GPL-2.0-only
104 tristate "Active-semi ACT8945A charger driver"
108 Active-semi ActivePath ACT8945A charger.
124 battery fuel gauge (used in the Pinebook Pro & others)
158 tristate "DS2782/DS2786 standalone gas-gauge"
162 gas-gauge.
208 tristate "Sharp SL-5500 (collie) battery"
212 SL-5500 (collie) models.
223 called ingenic-battery.
239 tristate "SBS Compliant gas gauge"
[all …]
H A Dab8500-bm.h1 /* SPDX-License-Identifier: GPL-2.0-only */
71 * Gas Gauge register offsets
215 /* Fuel Gauge constants */
267 * struct ab8500_fg_parameters - Fuel gauge algorithm parameters, in seconds
317 * struct ab8500_charger_maximization - struct used by the board config.
331 * struct ab8500_bm_capacity_levels - ab8500 capacity level data
347 * struct ab8500_bm_charger_parameters - Charger specific parameters
361 * struct ab8500_bm_data - ab8500 battery management data
381 * @fg_params fuel gauge parameters
H A Drt5033_battery.c1 // SPDX-License-Identifier: GPL-2.0-only
3 * Fuel gauge driver for Richtek RT5033
14 #include <linux/mfd/rt5033-private.h>
28 ret = power_supply_get_property_from_supplier(battery->psy, in rt5033_battery_get_status()
42 regmap_read(battery->regmap, RT5033_FUEL_REG_SOC_H, &msb); in rt5033_battery_get_capacity()
52 regmap_read(battery->regmap, RT5033_FUEL_REG_CONFIG_L, &val); in rt5033_battery_get_present()
79 return -EINVAL; in rt5033_battery_get_watt_prop()
82 regmap_read(battery->regmap, regh, &msb); in rt5033_battery_get_watt_prop()
83 regmap_read(battery->regmap, regl, &lsb); in rt5033_battery_get_watt_prop()
100 val->intval = rt5033_battery_get_watt_prop(battery->client, in rt5033_battery_get_property()
[all …]
H A Drn5t618_power.c1 // SPDX-License-Identifier: GPL-2.0+
54 #define TO_CUR_REG(x) ((x) / 100000 - 1)
116 ret = regmap_bulk_read(info->rn5t618->regmap, in rn5t618_battery_read_doublereg()
161 ret = regmap_read(info->rn5t618->regmap, RN5T618_CHGSTATE, &v); in rn5t618_battery_status()
165 val->intval = POWER_SUPPLY_STATUS_UNKNOWN; in rn5t618_battery_status()
168 val->intval = rn5t618_decode_status(v); in rn5t618_battery_status()
170 val->intval = POWER_SUPPLY_STATUS_DISCHARGING; in rn5t618_battery_status()
181 ret = regmap_read(info->rn5t618->regmap, RN5T618_CHGSTATE, &v); in rn5t618_battery_present()
187 val->intval = 0; in rn5t618_battery_present()
189 val->intval = 1; in rn5t618_battery_present()
[all …]
H A Dda9150-fg.c1 // SPDX-License-Identifier: GPL-2.0-or-later
3 * DA9150 Fuel-Gauge Driver
22 #include <linux/devm-helpers.h>
99 da9150_read_qif(fg->da9150, read_addr, size, buf); in da9150_fg_read_attr()
121 da9150_write_qif(fg->da9150, write_addr, size, buf); in da9150_fg_write_attr()
130 mutex_lock(&fg->io_lock); in da9150_fg_read_sync_start()
150 dev_err(fg->dev, "Failed to perform QIF read sync!\n"); in da9150_fg_read_sync_start()
159 mutex_unlock(&fg->io_lock); in da9150_fg_read_sync_end()
181 mutex_lock(&fg->io_lock); in da9150_fg_write_attr_sync()
196 dev_err(fg->dev, "Timeout waiting for existing QIF sync!\n"); in da9150_fg_write_attr_sync()
[all …]
/linux/Documentation/devicetree/bindings/power/supply/
H A Dbq27xxx.yaml1 # SPDX-License-Identifier: GPL-2.0
4 ---
6 $schema: http://devicetree.org/meta-schemas/core.yaml#
8 title: TI BQ27XXX fuel gauge family
11 - Pali Rohár <pali@kernel.org>
12 - Andrew F. Davis <afd@ti.com>
13 - Sebastian Reichel <sre@kernel.org>
16 Support various Texas Instruments fuel gauge devices that share similar
20 - $ref: power-supply.yaml#
25 - ti,bq27200
[all …]
H A Ddlg,da9150-fuel-gauge.yaml1 # SPDX-License-Identifier: GPL-2.0
3 ---
4 $id: http://devicetree.org/schemas/power/supply/dlg,da9150-fuel-gauge.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
7 title: Dialog Semiconductor DA9150 Fuel-Gauge Power Supply
10 - Sebastian Reichel <sre@kernel.org>
13 - $ref: power-supply.yaml#
17 const: dlg,da9150-fuel-gauge
19 dlg,update-interval:
23 dlg,warn-soc-level:
[all …]
H A Dcharger-manager.yaml1 # SPDX-License-Identifier: GPL-2.0
3 ---
4 $id: http://devicetree.org/schemas/power/supply/charger-manager.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Sebastian Reichel <sre@kernel.org>
18 const: charger-manager
20 cm-chargers:
22 $ref: /schemas/types.yaml#/definitions/string-array
24 cm-num-chargers:
28 cm-fuel-gauge:
[all …]
H A Dmitsumi,mm8013.yaml1 # SPDX-License-Identifier: GPL-2.0-only OR BSD-2-Clause
3 ---
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
7 title: Mitsumi MM8013 fuel gauge
10 - Konrad Dybcio <konradybcio@kernel.org>
13 - $ref: power-supply.yaml#
23 - compatible
24 - reg
29 - |
31 #address-cells = <1>;
[all …]
H A Dmaxim,max17201.yaml1 # SPDX-License-Identifier: GPL-2.0-only OR BSD-2-Clause
3 ---
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
7 title: Maxim MAX17201 fuel gauge
10 - Dimitri Fedrau <dima.fedrau@gmail.com>
13 - $ref: power-supply.yaml#
18 - const: maxim,max17201
19 - items:
20 - enum:
21 - maxim,max17205
[all …]
H A Dstericsson,ab8500-fg.yaml1 # SPDX-License-Identifier: GPL-2.0
4 ---
5 $id: http://devicetree.org/schemas/power/supply/stericsson,ab8500-fg.yaml#
6 $schema: http://devicetree.org/meta-schemas/core.yaml#
8 title: AB8500 Fuel Gauge
11 - Sebastian Reichel <sre@kernel.org>
14 - $ref: power-supply.yaml#
18 const: stericsson,ab8500-fg
20 monitored-battery:
28 line-impedance-micro-ohms:
[all …]
H A Dmaxim,max17040.yaml1 # SPDX-License-Identifier: GPL-2.0
3 ---
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
7 title: Maxim 17040 fuel gauge series
10 - Sebastian Reichel <sre@kernel.org>
13 - $ref: power-supply.yaml#
18 - maxim,max17040
19 - maxim,max17041
20 - maxim,max17043
21 - maxim,max17044
[all …]
H A Dbattery.yaml1 # 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
15 on a fuel gauge chip. The battery node should be used where there is
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
[all …]
H A Dcw2015_battery.yaml1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
7 title: Battery driver for CW2015 shuntless fuel gauge by CellWise.
10 - Tobias Schramm <t.schramm@manjaro.org>
13 The driver can utilize information from a simple-battery linked via a
14 phandle in monitored-battery. If specified the driver uses the
15 charge-full-design-microamp-hours property of the battery.
18 - $ref: power-supply.yaml#
27 cellwise,battery-profile:
[all …]
H A Drichtek,rt5033-battery.yaml1 # SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/power/supply/richtek,rt5033-battery.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
7 title: Richtek RT5033 PMIC Fuel Gauge
10 - Stephan Gerhold <stephan@gerhold.net>
13 - $ref: power-supply.yaml#
17 const: richtek,rt5033-battery
26 - compatible
27 - reg
[all …]
H A Dadc-battery.yaml1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/power/supply/adc-battery.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Sebastian Reichel <sre@kernel.org>
24 - $ref: power-supply.yaml#
28 const: adc-battery
30 charged-gpios:
36 io-channels:
40 io-channel-names:
[all …]
/linux/Documentation/devicetree/bindings/mfd/
H A Dda9150.txt1 Dialog Semiconductor DA9150 Combined Charger/Fuel-Gauge MFD bindings
3 DA9150 consists of a group of sub-devices:
6 ------ -----------
7 da9150-gpadc : General Purpose ADC
8 da9150-charger : Battery Charger
9 da9150-fg : Battery Fuel-Gauge
14 - compatible : Should be "dlg,da9150"
15 - reg: Specifies the I2C slave address
16 - interrupts: IRQ line info for da9150 chip.
17 - interrupt-controller: da9150 has internal IRQs (own IRQ domain).
[all …]
H A Drichtek,rt5033.yaml1 # SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause)
3 ---
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Jakob Hauser <jahau@rocketmail.com>
13 RT5033 is a multifunction device which includes battery charger, fuel gauge,
16 battery fuel gauge uses a separate I2C bus.
30 The regulators of RT5033 have to be instantiated under a sub-node named
44 $ref: /schemas/power/supply/richtek,rt5033-charger.yaml#
47 - compatible
48 - reg
[all …]
H A Dsprd,sc27xx-pmic.txt8 - DCDCs to support CPU, memory.
9 - LDOs to support both internal and external requirement.
10 - Battery management system, such as charger, fuel gauge.
11 - Audio codec.
12 - User interface function, such as indicator, flash LED and so on.
13 - IC level interface, such as power on/off control, RTC and typec and so on.
16 - compatible: Should be one of the following:
22 - reg: The address of the device chip select, should be 0.
23 - spi-max-frequency: Typically set to 26000000.
24 - interrupts: The interrupt line the device is connected to.
[all …]
/linux/include/linux/mfd/
H A Dmax8997.h1 /* SPDX-License-Identifier: GPL-2.0+ */
3 * max8997.h - Driver for the Maxim 8997/8966
5 * Copyright (C) 2009-2010 Samsung Electrnoics
10 * MAX8997 has PMIC, MUIC, HAPTIC, RTC, FLASH, and Fuel Gauge devices.
11 * Except Fuel Gauge, every device shares the same I2C bus and included in
12 * this mfd driver. Although the fuel gauge is included in the chip, it is
121 * [0 - 3]: valid pattern number
124 * [0 - 15]: available cycles
126 * [0 - 255]: available period
154 * [0 - 31]: MAX8997_FLASH_MODE and MAX8997_FLASH_PIN_CONTROL_MODE
[all …]
/linux/Documentation/ABI/testing/
H A Dsysfs-platform-dptf4 Contact: linux-acpi@vger.kernel.org
6 (RO) The charger type - Traditional, Hybrid or NVDC.
11 Contact: linux-acpi@vger.kernel.org
19 Contact: linux-acpi@vger.kernel.org
27 Contact: linux-acpi@vger.kernel.org
33 - 0x00 = DC
34 - 0x01 = AC
35 - 0x02 = USB
36 - 0x03 = Wireless Charger
43 Contact: linux-acpi@vger.kernel.org
[all …]
/linux/drivers/platform/x86/x86-android-tablets/
H A Dlenovo.c1 // SPDX-License-Identifier: GPL-2.0-or-later
8 * Copyright (C) 2021-2023 Hans de Goede <hdegoede@redhat.com>
27 #include "shared-psy-info.h"
28 #include "x86-android-tablets.h"
33 * The Android kernels have a hack in the i915 driver to write a non-standard
34 * panel specific DSI register to set the duty-cycle of the LCD's PWM output.
46 * But on some models the panel's PWM output defaults to a duty-cycle of
65 PROPERTY_ENTRY_U32("hid-descr-addr", 0x0001),
66 PROPERTY_ENTRY_U32("post-reset-deassert-delay-ms", 150),
75 * The HiDeep IST940E touchscreen comes up in I2C-HID mode. The native protocol
[all …]
/linux/include/linux/power/
H A Dcharger-manager.h1 /* SPDX-License-Identifier: GPL-2.0-only */
8 * monitor charging even in the context of suspend-to-RAM with
62 /* The charger-manager use Extcon framework */
72 * Set min/max current of regulator to protect over-current issue
86 * Set if the charger-manager cannot control charger,
126 * @psy_name: the name of power-supply-class for charger manager
144 * @psy_charger_stat: the names of power-supply for chargers
147 * @psy_fuel_gauge: the name of power-supply for fuel gauge
160 * after full-batt. If discharging duration exceed 'discharging
203 * @fuel_gauge: power_supply for fuel gauge
[all …]
/linux/Documentation/devicetree/bindings/iio/adc/
H A Ddlg,da9150-gpadc.yaml1 # SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/iio/adc/dlg,da9150-gpadc.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Adam Thomson <Adam.Thomson.Opensource@diasemi.com>
14 DA9150 Charger & Fuel-Gauge IC.
18 const: dlg,da9150-gpadc
20 "#io-channel-cells":
24 - compatible
25 - "#io-channel-cells"
[all …]
/linux/Documentation/power/
H A Dcharger-manager.rst7 Charger Manager provides in-kernel battery charger management that
8 requires temperature monitoring during suspend-to-RAM state
12 Charger Manager is a platform_driver with power-supply-class entries.
13 An instance of Charger Manager (a platform-device created with Charger-Manager)
26 own power-supply-class and each power-supply-class can provide
28 aggregates charger-related information from multiple sources and
29 shows combined information as a single power-supply-class.
31 * Support for in suspend-to-RAM polling (with suspend_again callback)
32 While the battery is being charged and the system is in suspend-to-RAM,
50 * Support for premature full-battery event handling
[all …]

1234