From: Ricardo Rivera-Matos <r-rivera-matos@ti.com>
To: <sre@kernel.org>
Cc: <linux-pm@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<dmurphy@ti.com>
Subject: Re: [RESEND PATCH v5 0/3] BQ25150/155 Charger
Date: Tue, 24 Mar 2020 10:14:20 -0500 [thread overview]
Message-ID: <eb5f0818-21c7-1b84-b0c9-904bce9721be@ti.com> (raw)
In-Reply-To: <20200304174025.31655-1-r-rivera-matos@ti.com>
bump
On 3/4/20 11:40 AM, Ricardo Rivera-Matos wrote:
> Hello,
>
> This v5 series picks up on the development that Dan Murphy <dmurphy@ti.com> began with the power_supply framework and bq2515x_charger driver. This series incorporates the changes suggested by Sebastien Reichel <sre@kernel.org> in v4.
>
> Datasheets for these devices can be found at:
> http://www.ti.com/lit/ds/symlink/bq25150.pdf
> http://www.ti.com/lit/ds/symlink/bq25155.pdf
>
> Thanks, Ricardo
>
> Dan Murphy (1):
> power_supply: Add additional health properties to the header
>
> Ricardo Rivera-Matos (2):
> Add the bindings for the bq25150 and bq25155 500mA charging ICs from
> Texas Instruments.
> power: supply: bq25150 introduce the bq25150
>
> Documentation/ABI/testing/sysfs-class-power | 2 +-
> .../bindings/power/supply/bq2515x.yaml | 99 ++
> drivers/power/supply/Kconfig | 8 +
> drivers/power/supply/Makefile | 1 +
> drivers/power/supply/bq2515x_charger.c | 1170 +++++++++++++++++
> drivers/power/supply/power_supply_sysfs.c | 2 +-
> include/linux/power_supply.h | 3 +
> 7 files changed, 1283 insertions(+), 2 deletions(-)
> create mode 100644 Documentation/devicetree/bindings/power/supply/bq2515x.yaml
> create mode 100644 drivers/power/supply/bq2515x_charger.c
>
next parent reply other threads:[~2020-03-24 15:14 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20200304174025.31655-1-r-rivera-matos@ti.com>
2020-03-24 15:14 ` Ricardo Rivera-Matos [this message]
2020-05-01 17:24 ` [RESEND PATCH v5 0/3] BQ25150/155 Charger Sebastian Reichel
2020-05-01 17:55 ` Dan Murphy
2020-05-01 18:09 ` Ricardo Rivera-Matos
2020-05-03 1:44 ` Sebastian Reichel
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=eb5f0818-21c7-1b84-b0c9-904bce9721be@ti.com \
--to=r-rivera-matos@ti.com \
--cc=dmurphy@ti.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=sre@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).