From: Sebastian Reichel <sebastian.reichel@collabora.com>
To: Linus Walleij <linus.walleij@linaro.org>
Cc: Marcus Cooper <codekipper@gmail.com>,
linux-pm@vger.kernel.org, Rob Herring <robh+dt@kernel.org>
Subject: Re: [PATCH 1/2] dt-bindings: power: Extend battery bindings with type
Date: Fri, 16 Jul 2021 16:09:59 +0200 [thread overview]
Message-ID: <20210716140959.4ajgyiwtwq3iq2wc@earth.universe> (raw)
In-Reply-To: <20210627234515.3057935-1-linus.walleij@linaro.org>
[-- Attachment #1: Type: text/plain, Size: 2172 bytes --]
Hi,
On Mon, Jun 28, 2021 at 01:45:14AM +0200, Linus Walleij wrote:
> This adds a battery-type property and bindings for the different
> "technologies" that are used in Linux. More types can be added.
Makes sense to have this.
> This is needed to convert the custom ST-Ericsson AB8500 battery
> properties over to the generic battery bindings.
Great :)
> Signed-off-by: Linus Walleij <linus.walleij@linaro.org>
> ---
> I need a bunch of new bindings for switch the STE AB8500 custom
> bindings out, but I need to start somewhere, this is as good as
> any place to start.
> ---
> .../devicetree/bindings/power/supply/battery.yaml | 14 ++++++++++++++
This should be CC'd to Rob Herring.
> 1 file changed, 14 insertions(+)
>
> diff --git a/Documentation/devicetree/bindings/power/supply/battery.yaml b/Documentation/devicetree/bindings/power/supply/battery.yaml
> index c3b4b7543591..3561ae2c1d58 100644
> --- a/Documentation/devicetree/bindings/power/supply/battery.yaml
> +++ b/Documentation/devicetree/bindings/power/supply/battery.yaml
> @@ -31,6 +31,20 @@ properties:
> compatible:
> const: simple-battery
>
> + battery-type:
The smart battery standard names the property storing this information
"DeviceChemistry", which (as a non-native speaker) seems like a
better fitting name. Thoughts?
> + description: This describes the chemical technology of the battery.
> + oneOf:
> + - const: nickel-cadmium
> + - const: nickel-metal-hydride
> + - const: lithium-ion
> + description: This is a blanket type for all lithium-ion batteries,
> + including those below. If possible, a precise compatible string
> + from below should be used, but sometimes it is unknown which specific
> + lithium ion battery is employed and this wide compatible can be used.
> + - const: lithium-ion-polymer
> + - const: lithium-ion-iron-phosphate
> + - const: lithium-ion-manganese-oxide
The values look good to me.
-- Sebastian
> over-voltage-threshold-microvolt:
> description: battery over-voltage limit
>
> --
> 2.31.1
>
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
prev parent reply other threads:[~2021-07-16 14:10 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-27 23:45 [PATCH 1/2] dt-bindings: power: Extend battery bindings with type Linus Walleij
2021-06-27 23:45 ` [PATCH 2/2] power: supply: core: Parse battery type/technology Linus Walleij
2021-06-28 2:13 ` kernel test robot
2021-06-28 2:18 ` kernel test robot
2021-06-28 2:20 ` kernel test robot
2021-06-28 3:43 ` kernel test robot
2021-07-16 14:09 ` Sebastian Reichel [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20210716140959.4ajgyiwtwq3iq2wc@earth.universe \
--to=sebastian.reichel@collabora.com \
--cc=codekipper@gmail.com \
--cc=linus.walleij@linaro.org \
--cc=linux-pm@vger.kernel.org \
--cc=robh+dt@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).