On Tue, Mar 21, 2017 at 03:09:15PM -0700, Liam Breck wrote: > From: Liam Breck <kernel@xxxxxxxxxxxxxxxxx> > > precharge-current-microamp and endcharge-current-microamp are used > by battery chargers at the beginning and end of a charging cycle. > > Depends-on: https://patchwork.kernel.org/patch/9633605/ > Cc: Rob Herring <robh@xxxxxxxxxx> > Cc: devicetree@xxxxxxxxxxxxxxx > Signed-off-by: Liam Breck <kernel@xxxxxxxxxxxxxxxxx> > --- > Documentation/devicetree/bindings/power/supply/battery.txt | 4 ++++ > 1 file changed, 4 insertions(+) > > diff --git a/Documentation/devicetree/bindings/power/supply/battery.txt b/Documentation/devicetree/bindings/power/supply/battery.txt > index 53a68c0..494374a 100644 > --- a/Documentation/devicetree/bindings/power/supply/battery.txt > +++ b/Documentation/devicetree/bindings/power/supply/battery.txt > @@ -12,6 +12,8 @@ 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 > + - precharge-current-microamp: current for pre-charge phase > + - endcharge-current-microamp: current for charge termination phase current is implied by microamp, so perhaps just pre-charge-microamp and end-charge-microamp. I know little about batteries, but don't you also need to know when each phase starts/ends? I mainly ask because we just added the previous properties and now we're adding 2 more. While fine to add features to a driver one by one, we really shouldn't for bindings. The h/w is not evolving (in a month). Rob -- To unsubscribe from this list: send the line "unsubscribe devicetree" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
