| Message ID | 20170511134221.5569-3-quentin.schulz@free-electrons.com (mailing list archive) |
|---|---|
| State | Not Applicable, archived |
| Headers | show |
On Thu, May 11, 2017 at 03:42:18PM +0200, Quentin Schulz wrote: > This adds the constant-charge-current-max-microamp property to the list > of optional properties of the battery. > > The constant charge current is critical for batteries as they can't > handle all charge currents. > > Signed-off-by: Quentin Schulz <quentin.schulz@free-electrons.com> > --- > Documentation/devicetree/bindings/power/supply/battery.txt | 2 ++ > 1 file changed, 2 insertions(+) Acked-by: Rob Herring <robh@kernel.org>
diff --git a/Documentation/devicetree/bindings/power/supply/battery.txt b/Documentation/devicetree/bindings/power/supply/battery.txt index 63a7028d1434..12c1abc93a90 100644 --- a/Documentation/devicetree/bindings/power/supply/battery.txt +++ b/Documentation/devicetree/bindings/power/supply/battery.txt @@ -12,6 +12,7 @@ Optional Properties: - voltage-min-design-microvolt: drained battery voltage - energy-full-design-microwatt-hours: battery design energy - charge-full-design-microamp-hours: battery design capacity + - constant-charge-current-max-microamp: battery maximum constant charge current Batteries must be referenced by chargers and/or fuel-gauges using a phandle. The phandle's property should be named @@ -24,6 +25,7 @@ Example: voltage-min-design-microvolt = <3200000>; energy-full-design-microwatt-hours = <5290000>; charge-full-design-microamp-hours = <1430000>; + constant-charge-current-max-microamp = <300000>; }; charger: charger@11 {
This adds the constant-charge-current-max-microamp property to the list of optional properties of the battery. The constant charge current is critical for batteries as they can't handle all charge currents. Signed-off-by: Quentin Schulz <quentin.schulz@free-electrons.com> --- Documentation/devicetree/bindings/power/supply/battery.txt | 2 ++ 1 file changed, 2 insertions(+)