From: Sebastian Reichel <sre@kernel.org>
To: Ricardo Rivera-Matos <r-rivera-matos@ti.com>
Cc: pali@kernel.org, robh@kernel.org, afd@ti.com, dmurphy@ti.com,
linux-pm@vger.kernel.org, linux-kernel@vger.kernel.org,
devicetree@vger.kernel.org, sspatil@android.com
Subject: Re: [PATCH v17 0/4] Add JEITA properties and introduce the bq2515x charger
Date: Mon, 27 Jul 2020 01:26:24 +0200 [thread overview]
Message-ID: <20200726232624.wmrcvjznbrxibc5n@earth.universe> (raw)
In-Reply-To: <20200720204400.7351-1-r-rivera-matos@ti.com>
[-- Attachment #1: Type: text/plain, Size: 1636 bytes --]
Hi,
On Mon, Jul 20, 2020 at 03:43:56PM -0500, Ricardo Rivera-Matos wrote:
> Hello,
>
> This patchset adds additional health properties to the power_supply header.
> These additional properties are taken from the JEITA specification. This
> patchset also introduces the bq2515x family of charging ICs.
>
> Dan Murphy (2):
> power_supply: Add additional health properties to the header
> dt-bindings: power: Convert battery.txt to battery.yaml
>
> Ricardo Rivera-Matos (2):
> dt-bindings: power: Add the bindings for the bq2515x family of
> chargers.
> power: supply: bq25150 introduce the bq25150
I merged patches 1,3,4 (the bq2515x ones). The patch converting
battery.txt to battery.yaml is not ok in its current form.
-- Sebastian
> Documentation/ABI/testing/sysfs-class-power | 3 +-
> .../bindings/power/supply/battery.txt | 86 +-
> .../bindings/power/supply/battery.yaml | 157 +++
> .../bindings/power/supply/bq2515x.yaml | 93 ++
> drivers/power/supply/Kconfig | 13 +
> drivers/power/supply/Makefile | 1 +
> drivers/power/supply/bq2515x_charger.c | 1169 +++++++++++++++++
> drivers/power/supply/power_supply_sysfs.c | 3 +
> include/linux/power_supply.h | 3 +
> 9 files changed, 1442 insertions(+), 86 deletions(-)
> create mode 100644 Documentation/devicetree/bindings/power/supply/battery.yaml
> create mode 100644 Documentation/devicetree/bindings/power/supply/bq2515x.yaml
> create mode 100644 drivers/power/supply/bq2515x_charger.c
>
> --
> 2.27.0
>
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
prev parent reply other threads:[~2020-07-26 23:26 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-20 20:43 [PATCH v17 0/4] Add JEITA properties and introduce the bq2515x charger Ricardo Rivera-Matos
2020-07-20 20:43 ` [PATCH v17 1/4] power_supply: Add additional health properties to the header Ricardo Rivera-Matos
2020-07-20 20:43 ` [PATCH v17 2/4] dt-bindings: power: Convert battery.txt to battery.yaml Ricardo Rivera-Matos
2020-07-23 16:56 ` Rob Herring
2020-07-26 23:24 ` Sebastian Reichel
2020-07-27 18:17 ` [EXTERNAL] " Ricardo Rivera-Matos
2020-07-20 20:43 ` [PATCH v17 3/4] dt-bindings: power: Add the bindings for the bq2515x family of chargers Ricardo Rivera-Matos
2020-07-20 20:44 ` [PATCH v17 4/4] power: supply: bq25150 introduce the bq25150 Ricardo Rivera-Matos
2020-07-26 23:26 ` 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=20200726232624.wmrcvjznbrxibc5n@earth.universe \
--to=sre@kernel.org \
--cc=afd@ti.com \
--cc=devicetree@vger.kernel.org \
--cc=dmurphy@ti.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=pali@kernel.org \
--cc=r-rivera-matos@ti.com \
--cc=robh@kernel.org \
--cc=sspatil@android.com \
/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).