Home
last modified time | relevance | path

Searched refs:charger (Results 1 – 25 of 60) sorted by relevance

123

/Zephyr-latest/drivers/charger/
DKconfig6 bool "Battery charger drivers"
8 Enable battery charger driver configuration.
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
53 source "drivers/charger/Kconfig.sbs_charger"
54 source "drivers/charger/Kconfig.bq24190"
55 source "drivers/charger/Kconfig.bq25180"
[all …]
DKconfig.max203355 bool "MAX20335 battery charger driver"
12 Enable the MAX20335 battery charger driver.
DKconfig.bq2518011 Enable BQ25180 battery charger driver.
DCMakeLists.txt4 zephyr_syscall_header(${ZEPHYR_BASE}/include/zephyr/drivers/charger.h)
DKconfig.sbs_charger13 bool "Emulate an SBS 1.1 compliant smart battery 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()
119 if (!device_is_ready(charger)) { in main()
/Zephyr-latest/samples/drivers/charger/
DREADME.rst1 .. zephyr:code-sample:: 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.
DCMakeLists.txt6 project(charger) project
DKconfig1 # Private config options for charger sample app
/Zephyr-latest/tests/drivers/build_all/charger/
Di2c.dtsi26 charger: charger { label
27 compatible = "maxim,max20335-charger";
45 sbs-charger@3 {
46 compatible = "sbs,sbs-charger";
/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
Dbc12.rst19 charger capability on USB type C ports when the attached type-C partner does not
61 starts charger detection. At completion of the charger detection, the BC1.2
75 BC1.2 driver powers up the detection chip and configures the charger type
Dindex.rst20 charger.rst
/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/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/boards/shields/npm1300_ek/
Dnpm1300_ek.overlay46 npm1300_ek_charger: charger {
47 compatible = "nordic,npm1300-charger";
/Zephyr-latest/drivers/sensor/nordic/npm1300_charger/
DKconfig13 Enable NPM1300 charger driver.
/Zephyr-latest/tests/drivers/charger/sbs_charger/boards/
Demulated_board.overlay24 compatible = "sbs,sbs-charger";
Dqemu_cortex_a53.overlay28 compatible = "sbs,sbs-charger";
/Zephyr-latest/boards/actinius/common/
Dactinius_board_common.c56 if (DT_ENUM_IDX(CHARGER_ENABLE_NODE, charger) == 0) { in actinius_board_set_charger_enable()
/Zephyr-latest/drivers/usb_c/tcpc/
DKconfig.tcpc_tcpci21 Some TCPCs are going into deep sleep mode when no charger is connected and won't respond
/Zephyr-latest/samples/drivers/charger/src/
Dmain.c14 static const struct device *chgdev = DEVICE_DT_GET(DT_NODELABEL(charger));
/Zephyr-latest/boards/nordic/nrf9131ek/
Dnrf9131ek_nrf9131_common.dtsi112 pmic_charger: charger {
113 compatible = "nordic,npm1300-charger";
/Zephyr-latest/doc/hardware/emulator/
Dbus_emulators.rst59 expander driver talking over an I2C bus, with the GPIOs controlling a charger.
117 to simulate connecting and disconnecting a charger to the emulated BC1.2 device.
124 #. Test connects a charger using the BC1.2 emulator backend.
125 #. Test verifies B1.2 detection callback invoked with correct charger type.
126 #. Test disconnects a charger using the BC1.2 emulator backend.
/Zephyr-latest/boards/adafruit/feather_stm32f405/doc/
Dindex.rst9 with a lithium ion battery charger, native USB C connector, 2MB of
18 - LiPo connector and charger

123