nordic,npm10xx-charger
Description
Nordic's nPM10 Series PMIC battery charger
Examples
npm1012: pmic@6a {
reg = <0x6a>;
compatible = "nordic,npm10xx";
/* ... */
charger {
compatible = "nordic,npm10xx-charger";
charging-enable;
charge-current-microamp = <25000>;
term-voltage-microvolt = <4200000>;
term-current-percent = "3.125%";
/* ... */
};
/* ... */
};
Properties
Node specific properties
Properties not inherited from the base binding file.
Name |
Type |
Details |
|---|---|---|
|
|
Enable charging.
|
|
|
Charge current in uA.
Available range is 0.5-128 mA in 0.5 mA steps and 129-256 mA in 1 mA steps.
|
|
|
Charge termination voltage in uV. Available range is 3.5-4.65 V in 10 mV steps.
|
|
|
Charge termination current in percent of current-microamp.
Legal values: |
|
|
Charge current in uA for the NTC warm region. Same range as current-microamp.
|
|
|
Charge termination voltage in uV for the NTC warm region. Same range as term-microvolt.
|
|
|
Charge current in uA for the NTC cool region. Same range as current-microamp.
|
|
|
Charge termination voltage in uV for the NTC cool region. Same range as term-microvolt.
|
|
|
Trickle charge current in percent of current-microamp.
Legal values: |
|
|
Trickle charge voltage in uV.
Legal values: |
|
|
Charge throttle current in percent of current-microamp.
Legal values: |
|
|
Charge throttle voltage level in uV.
Vthrottle = term-voltage-{,-cool,-warm}microvolt- - throttle-level-microvolt.
Legal values: |
|
|
Trickle charge timeout in minutes.
Legal values: |
|
|
Charge cycle timeout in hours.
Legal values: |
|
|
Beta value of selected thermistor.
|
|
|
Thermistor cold threshold in degrees Celsius.
|
|
|
Thermistor cool threshold in degrees Celsius.
|
|
|
Thermistor warm threshold in degrees Celsius.
|
|
|
Thermistor hot threshold in degrees Celsius.
|
|
|
Die temperature current reduce threshold in degrees Celsius.
When die temperature exceeds this threshold, charging current will be reduced.
|
|
|
Die temperature resume threshold in degrees Celsius. When die temperature falls below this
threshold, charging current will gradually increase. Recommended to be at least 10 degrees
lower than dietemp-reduce-degrees.
|
|
|
Disable battery temperature monitoring during charging.
|
|
|
Disable automatic recharge.
|
|
|
Disable charging of warm battery.
|
|
|
Disable charging of cool battery.
|
|
|
Use custom values for termination voltage and charge current in warm and cool temperature
regions. The default JEITA values will be used otherwise.
|
|
|
Enable throttle charging.
|
|
|
Disable charging of battery below VBATLOW threshold (2.1 or 1.1 V).
|
|
|
VBATLOW threshold. Choose between 2.1 and 1.1 V.
Legal values: |
|
|
VBUS input current limit to set during initialization.
Legal values: |
|
|
The device monitors VBUS and limits SYSREG current to maintain the VBUS voltage above the
selected level. Choose a level to set during initialization.
Legal values: |
Deprecated node specific properties
Deprecated properties not inherited from the base binding file.
(None)
Base properties
Properties inherited from the base binding file, which defines common properties that may be set on many nodes. Not all of these may apply to the “nordic,npm10xx-charger” compatible.
Name |
Type |
Details |
|---|---|---|
|
|
Indicates the operational status of the hardware or other
resource that the node represents. In particular:
- "okay" means the resource is operational and, for example,
can be used by device drivers
- "disabled" means the resource is not operational and the system
should treat it as if it is not present
For details, see "2.3.4 status" in Devicetree Specification v0.4.
Legal values: See Important properties for more information. |
|
|
This property is a list of strings that essentially define what
type of hardware or other resource this devicetree node
represents. Each device driver checks for specific compatible
property values to find the devicetree nodes that represent
resources that the driver should manage.
The recommended format is "vendor,device", The "vendor" part is
an abbreviated name of the vendor. The "device" is usually from
the datasheet.
The compatible property can have multiple values, ordered from
most- to least-specific. Having additional values is useful when the
device is a specific instance of a more general family, to allow the
system to match the most specific driver available.
For details, see "2.3.1 compatible" in Devicetree Specification v0.4.
This property is required. See Important properties for more information. |
|
|
Information used to address the device. The value is specific to
the device (i.e. is different depending on the compatible
property).
The "reg" property is typically a sequence of (address, length) pairs.
Each pair is called a "register block". Values are
conventionally written in hex.
For details, see "2.3.6 reg" in Devicetree Specification v0.4.
See Important properties for more information. |
|
|
Optional names given to each register block in the "reg" property.
For example:
/ {
soc {
#address-cells = <1>;
#size-cells = <1>;
uart@1000 {
reg = <0x1000 0x2000>, <0x3000 0x4000>;
reg-names = "foo", "bar";
};
};
};
The uart@1000 node has two register blocks:
- one with base address 0x1000, size 0x2000, and name "foo"
- another with base address 0x3000, size 0x4000, and name "bar"
|
|
|
Information about interrupts generated by the device, encoded as an array
of one or more interrupt specifiers. The format of the data in this property
varies by where the device appears in the interrupt tree. Devices with the same
"interrupt-parent" will use the same format in their interrupts properties.
For details, see "2.4 Interrupts and Interrupt Mapping" in
Devicetree Specification v0.4.
See Important properties for more information. |
|
|
Extended interrupt specifier for device, used as an alternative to
the "interrupts" property.
For details, see "2.4 Interrupts and Interrupt Mapping" in
Devicetree Specification v0.4.
|
|
|
Optional names given to each interrupt generated by a device.
The interrupts themselves are defined in either "interrupts" or
"interrupts-extended" properties.
For details, see "2.4 Interrupts and Interrupt Mapping" in
Devicetree Specification v0.4.
|
|
|
If present, this refers to the node which handles interrupts generated
by this device.
For details, see "2.4 Interrupts and Interrupt Mapping" in
Devicetree Specification v0.4.
|
|
|
Human readable string describing the device. Use of this property is
deprecated except as needed on a case-by-case basis.
For details, see "4.1.2 Miscellaneous Properties" in Devicetree
Specification v0.4.
See Important properties for more information. |
|
|
Information about the device's clock providers. In general, this property
should follow conventions established in the dt-schema binding:
https://github.com/devicetree-org/dt-schema/blob/main/dtschema/schemas/clock/clock.yaml
|
|
|
Optional names given to each clock provider in the "clocks" property.
|
|
|
This property encodes the number of <u32> cells used by address fields
in "reg" properties in this node's children.
For details, see "2.3.5 #address-cells and #size-cells" in Devicetree
Specification v0.4.
|
|
|
This property encodes the number of <u32> cells used by size fields in
"reg" properties in this node's children.
For details, see "2.3.5 #address-cells and #size-cells" in Devicetree
Specification v0.4.
|
|
|
DMA channel specifiers relevant to the device.
|
|
|
Optional names given to the DMA channel specifiers in the "dmas" property.
|
|
|
IO channel specifiers relevant to the device.
|
|
|
Optional names given to the IO channel specifiers in the "io-channels" property.
|
|
|
Mailbox / IPM channel specifiers relevant to the device.
|
|
|
Optional names given to the mbox specifiers in the "mboxes" property.
|
|
|
Power domain specifiers relevant to the device.
|
|
|
Optional names given to the power domain specifiers in the "power-domains" property.
|
|
|
Number of cells in power-domains property
|
|
|
HW spinlock id relevant to the device.
|
|
|
Optional names given to the hwlock specifiers in the "hwlocks" property.
|
|
|
Do not initialize device automatically on boot. Device should be manually
initialized using device_init().
|
|
|
Property to identify that a device can be used as wake up source.
When this property is provided a specific flag is set into the
device that tells the system that the device is capable of
wake up the system.
Wake up capable devices are disabled (interruptions will not wake up
the system) by default but they can be enabled at runtime if necessary.
|
|
|
Automatically configure the device for runtime power management after the
init function runs.
|
|
|
List of power states that will disable this device power.
|