Home
last modified time | relevance | path

Searched full:charger (Results 1 – 25 of 89) sorted by relevance

1234

/Zephyr-latest/drivers/charger/
DKconfig5 menuconfig CHARGER config
6 bool "Battery charger drivers"
8 Enable battery charger driver configuration.
10 if CHARGER
12 module = CHARGER
13 module-str = charger
17 int "Battery charger init priority"
20 Battery charger initialization priority.
25 This symbol is y if the charger supports discharge
31 This symbol is y if the charger supports system
[all …]
DKconfig.sbs_charger5 bool "Smart Battery Charger"
10 Enable I2C-based/SMBus-based driver for a Smart Battery Charger.
13 bool "Emulate an SBS 1.1 compliant smart battery charger"
DKconfig.bq251806 bool "BQ25180 Battery Charger"
11 Enable BQ25180 battery charger driver.
DKconfig.max203355 bool "MAX20335 battery charger driver"
12 Enable the MAX20335 battery charger driver.
DKconfig.bq241905 bool "BQ24190 Battery Charger"
10 Enable I2C-based driver for the TI BQ24190 Battery Charger.
/Zephyr-latest/samples/drivers/charger/
DREADME.rst1 .. zephyr:code-sample:: charger
2 :name: Charger
5 Charge a battery using the charger driver API.
14 - The application will first poll for external power provided to the charger device.
15 - If power is provided to the charger, then the sample application will attempt to enable the charge
18 charger device and report any relevant information to the log.
19 - Once the charger device reports that the charge cycle has completed, the application returns.
22 the battery pack. Additionally, the sample intentionally does not respond to the reported charger
24 responsibility of responding to these events falls on the user or the charger device implementation.
Dsample.yaml2 name: Generic charger
4 sample.drivers.charger:
5 tags: charger
6 depends_on: charger
DKconfig1 # Private config options for charger sample app
6 mainmenu "Charger application"
/Zephyr-latest/include/zephyr/drivers/
Dcharger.h9 * @brief Charger APIs
16 * @brief Charger Interface
17 * @defgroup charger_interface Charger Interface
36 /** Indicates if external supply is present for the charger. */
42 /** Represents the charging status of the charger. */
45 /** Represents the charging algo type of the charger. */
48 /** Represents the health of the charger. */
93 * Configuration to issue a notification to the system based on the charger status change
99 * Configuration to issue a notification to the system based on the charger online change
104 /** Reserved to demark end of common charger properties */
[all …]
/Zephyr-latest/boards/actinius/icarus/dts/bindings/
Dactinius-charger-enable.yaml6 charger or to leave it on auto. The option can be changed by changing
7 the `charger` property in the associated dt node to `auto`
10 compatible: "actinius-charger-enable"
18 description: Pin used to enable/disable the charger
20 charger:
26 description: Charger enable choice (auto or disabled)
/Zephyr-latest/doc/hardware/peripherals/
Dcharger.rst6 The charger subsystem exposes an API to uniformly access battery charger devices.
8 A charger device, or charger peripheral, is a device used to take external power provided to the
10 The charger device can exist as a module, an integrated circuit, or as a functional block in a power
14 executed the battery pack is charged according to the charge profile configured on the charger
16 manufacturer. On charger devices with a control port, the charge profile can be configured by the
31 Fundamentally, a property is a configurable setting, state, or quantity that a charger device can
/Zephyr-latest/tests/drivers/charger/sbs_charger/
Dtestcase.yaml7 - charger
10 drivers.charger.sbs.emulated:
11 filter: dt_compat_enabled("sbs,sbs-charger")
26 drivers.charger.sbs.emulated_64_bit_i2c_addr:
27 filter: dt_compat_enabled("sbs,sbs-charger")
/Zephyr-latest/tests/drivers/build_all/charger/
Dtestcase.yaml5 drivers.charger.build:
8 - charger
13 drivers.charger.emul.build:
16 - charger
Di2c.dtsi26 charger: charger { label
27 compatible = "maxim,max20335-charger";
45 sbs-charger@3 {
46 compatible = "sbs,sbs-charger";
/Zephyr-latest/samples/shields/npm1300_ek/src/
Dmain.c26 static const struct device *charger = DEVICE_DT_GET(DT_NODELABEL(npm1300_ek_charger)); variable
85 sensor_sample_fetch(charger); in read_sensors()
86 sensor_channel_get(charger, SENSOR_CHAN_GAUGE_VOLTAGE, &volt); in read_sensors()
87 sensor_channel_get(charger, SENSOR_CHAN_GAUGE_AVG_CURRENT, &current); in read_sensors()
88 sensor_channel_get(charger, SENSOR_CHAN_GAUGE_TEMP, &temp); in read_sensors()
89 sensor_channel_get(charger, (enum sensor_channel)SENSOR_CHAN_NPM1300_CHARGER_STATUS, in read_sensors()
91 sensor_channel_get(charger, (enum sensor_channel)SENSOR_CHAN_NPM1300_CHARGER_ERROR, &error); in read_sensors()
92 sensor_attr_get(charger, (enum sensor_channel)SENSOR_CHAN_NPM1300_CHARGER_VBUS_STATUS, in read_sensors()
104 printk("Charger Status: %d, Error: %d, VBUS: %s\n", status.val1, error.val1, in read_sensors()
119 if (!device_is_ready(charger)) { in main()
[all …]
/Zephyr-latest/boards/actinius/common/
Dactinius_board_common.c52 LOG_ERR("The Charger Enable Pin port is not ready"); in actinius_board_set_charger_enable()
56 if (DT_ENUM_IDX(CHARGER_ENABLE_NODE, charger) == 0) { in actinius_board_set_charger_enable()
58 LOG_INF("Charger is set to auto"); in actinius_board_set_charger_enable()
61 LOG_INF("Charger is disabled"); in actinius_board_set_charger_enable()
84 LOG_ERR("Failed to set the Charger Enable Pin (error: %d)", result); in actinius_board_init()
/Zephyr-latest/drivers/sensor/nordic/npm1300_charger/
DKconfig6 bool "NPM1300 Charger"
13 Enable NPM1300 charger driver.
/Zephyr-latest/boards/actinius/icarus/
Dactinius_icarus_common_2_0_0.dtsi42 charger_enable: charger-enable {
43 compatible = "actinius-charger-enable";
45 charger = "auto";
/Zephyr-latest/dts/bindings/charger/
Dsbs,sbs-charger.yaml7 description: SBS 1.1 compliant charger (http://www.sbs-forum.org/specs)
9 compatible: "sbs,sbs-charger"
Dmaxim,max20335-charger.yaml4 description: Maxim MAX20335 battery charger
8 compatible: "maxim,max20335-charger"
53 voltage drops to this level, the charger current
Dti,bq25180.yaml5 BQ25180 I2C Controlled, 1-Cell, 1-A Linear Battery Charger with Power Path
8 The device has a single child node for the charger. For example:
/Zephyr-latest/samples/drivers/charger/src/
Dmain.c11 #include <zephyr/drivers/charger.h>
14 static const struct device *chgdev = DEVICE_DT_GET(DT_NODELABEL(charger));
22 printk("Error: no charger device found.\n"); in main()
33 printk("Found device \"%s\", getting charger data\n", chgdev->name); in main()
59 /* Poll until external power is presented to the charger */ in main()
/Zephyr-latest/include/zephyr/drivers/sensor/
Dnpm1300_charger.h11 /* NPM1300 charger specific channels */
18 /* NPM1300 charger specific attributes */
/Zephyr-latest/samples/subsys/usb_c/sink/
DREADME.rst14 After the USB-C Sink device is plugged into a Power Delivery charger, it
15 negotiates with the charger to provide 5V@100mA and displays all
16 Power Delivery Objects (PDOs) provided by the charger.
39 Connect a charger and see console output:
/Zephyr-latest/include/zephyr/drivers/usb/
Dusb_bc12.h35 /** BC1.2 USB charger voltage. */
38 * BC1.2 USB charger minimum current. Set to match the Isusp of 2.5 mA parameter.
49 /** BC1.2 USB charger maximum current. */
116 * @brief BC1.2 callback for charger configuration
118 * @param dev BC1.2 device which is notifying of the new charger state.
121 * If NULL, then the partner charger is disconnected or the BC1.2 device is

1234