From: Dmitry Osipenko <digetx@gmail.com>
To: Sebastian Reichel <sre@kernel.org>,
Rob Herring <robh+dt@kernel.org>, Andy Gross <agross@kernel.org>,
Bjorn Andersson <bjorn.andersson@linaro.org>,
David Heidelberg <david@ixit.cz>
Cc: linux-pm@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-arm-msm@vger.kernel.org,
Jonghwa Lee <jonghwa3.lee@samsung.com>,
John Stultz <john.stultz@linaro.org>,
Vinay Simha BN <simhavcs@gmail.com>
Subject: [PATCH v2 0/9] Summit SMB3xx driver & device-tree
Date: Sun, 7 Jun 2020 17:41:04 +0300 [thread overview]
Message-ID: <20200607144113.10202-1-digetx@gmail.com> (raw)
We gathered existing patches, fixed and improved what we could and
final result is an working charging driver with device-tree support
for Nexus 7.
At this moment charging works with:
- Nexus 7 2012 (grouper and tilapia)
- Nexus 7 2013 (flo and deb)
- ... and there are more devices equipped with these chargers.
Changelog:
v2: - Addressed v1 review comments from Rob Herring and Sebastian Reichel
by moving out common battery properties from the charger node into the
battery-cell node.
- power_supply_register() of the SMB driver converted to resource-managed
API variant.
- Improved DT property names of the SMB binding by making them to follow
the generic power-supply naming scheme (-microvolts at the end, etc).
David Heidelberg (6):
dt-bindings: power: supply: Add device-tree binding for Summit SMB3xx
power: supply: smb347-charger: Use resource-managed API
power: supply: smb347-charger: Implement device-tree support
power: supply: smb347-charger: Support SMB345 and SMB358
power: supply: smb347-charger: Remove virtual smb347-battery
ARM: dts: qcom: apq8064-nexus7: Add SMB345 charger node
Dmitry Osipenko (3):
dt-bindings: battery: Add temperature properties
power: supply: Support battery temperature device-tree properties
power: supply: smb347-charger: Replace mutex with IRQ disable/enable
.../bindings/power/supply/battery.txt | 10 +
.../power/supply/summit,smb347-charger.yaml | 165 +++++
.../boot/dts/qcom-apq8064-asus-nexus7-flo.dts | 23 +
drivers/power/supply/Kconfig | 6 +-
drivers/power/supply/power_supply_core.c | 18 +
drivers/power/supply/smb347-charger.c | 565 +++++++++---------
.../dt-bindings/power/summit,smb347-charger.h | 19 +
include/linux/power_supply.h | 6 +
8 files changed, 542 insertions(+), 270 deletions(-)
create mode 100644 Documentation/devicetree/bindings/power/supply/summit,smb347-charger.yaml
create mode 100644 include/dt-bindings/power/summit,smb347-charger.h
--
2.26.0
next reply other threads:[~2020-06-07 14:45 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-07 14:41 Dmitry Osipenko [this message]
2020-06-07 14:41 ` [PATCH v2 1/9] dt-bindings: power: supply: Add device-tree binding for Summit SMB3xx Dmitry Osipenko
2020-07-13 23:39 ` Rob Herring
2020-07-16 17:24 ` Dmitry Osipenko
2020-06-07 14:41 ` [PATCH v2 2/9] dt-bindings: battery: Add temperature properties Dmitry Osipenko
2020-07-13 23:46 ` Rob Herring
2020-07-16 17:24 ` Dmitry Osipenko
2020-06-07 14:41 ` [PATCH v2 3/9] power: supply: Support battery temperature device-tree properties Dmitry Osipenko
2020-06-07 14:41 ` [PATCH v2 4/9] power: supply: smb347-charger: Use resource-managed API Dmitry Osipenko
2020-06-07 14:41 ` [PATCH v2 5/9] power: supply: smb347-charger: Implement device-tree support Dmitry Osipenko
2020-06-07 14:41 ` [PATCH v2 6/9] power: supply: smb347-charger: Support SMB345 and SMB358 Dmitry Osipenko
2020-06-07 14:41 ` [PATCH v2 7/9] power: supply: smb347-charger: Remove virtual smb347-battery Dmitry Osipenko
2020-06-07 14:41 ` [PATCH v2 8/9] power: supply: smb347-charger: Replace mutex with IRQ disable/enable Dmitry Osipenko
2020-06-07 14:41 ` [PATCH v2 9/9] ARM: dts: qcom: apq8064-nexus7: Add SMB345 charger node Dmitry Osipenko
2020-07-08 7:42 ` [PATCH v2 0/9] Summit SMB3xx driver & device-tree Dmitry Osipenko
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=20200607144113.10202-1-digetx@gmail.com \
--to=digetx@gmail.com \
--cc=agross@kernel.org \
--cc=bjorn.andersson@linaro.org \
--cc=david@ixit.cz \
--cc=devicetree@vger.kernel.org \
--cc=john.stultz@linaro.org \
--cc=jonghwa3.lee@samsung.com \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=robh+dt@kernel.org \
--cc=simhavcs@gmail.com \
--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).