From: Timon Baetz <timon.baetz@protonmail.com>
To: Liam Girdwood <lgirdwood@gmail.com>,
Mark Brown <broonie@kernel.org>,
Krzysztof Kozlowski <krzk@kernel.org>,
Rob Herring <robh+dt@kernel.org>,
Sebastian Reichel <sre@kernel.org>
Cc: linux-kernel@vger.kernel.org, devicetree@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-samsung-soc@vger.kernel.org, linux-pm@vger.kernel.org,
Timon Baetz <timon.baetz@protonmail.com>
Subject: [PATCH 0/3] charger-supply for max8997_charger
Date: Sat, 30 Jan 2021 17:28:49 +0000 [thread overview]
Message-ID: <20210130172747.2022977-1-timon.baetz@protonmail.com> (raw)
Based on the discussion from [0] add an optional DT property to retrieve
the regulator used for charging control in the max8997_charger driver.
[0] https://lore.kernel.org/lkml/20210118124505.GG4455@sirena.org.uk/
Timon Baetz (3):
regulator: dt-bindings: Document charger-supply for max8997
ARM: dts: exynos: Add charger supply for I9100
power: supply: max8997_charger: Switch to new binding
.../bindings/regulator/max8997-regulator.txt | 1 +
arch/arm/boot/dts/exynos4210-i9100.dts | 2 ++
drivers/power/supply/max8997_charger.c | 12 ++++++++----
3 files changed, 11 insertions(+), 4 deletions(-)
--
2.25.1
next reply other threads:[~2021-01-30 17:29 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-30 17:28 Timon Baetz [this message]
2021-01-30 17:29 ` [PATCH 1/3] regulator: dt-bindings: Document charger-supply for max8997 Timon Baetz
2021-01-30 17:29 ` [PATCH 2/3] ARM: dts: exynos: Add charger supply for I9100 Timon Baetz
2021-02-11 5:59 ` Timon Baetz
2021-02-11 7:39 ` Krzysztof Kozlowski
2021-03-02 8:52 ` Krzysztof Kozlowski
2021-01-30 17:30 ` [PATCH 3/3] power: supply: max8997_charger: Switch to new binding Timon Baetz
2021-01-31 17:28 ` Krzysztof Kozlowski
2021-02-01 9:26 ` Timon Baetz
2021-02-01 18:03 ` Krzysztof Kozlowski
2021-03-09 7:47 ` Timon Baetz
2021-03-26 16:20 ` Timon Baetz
2021-02-03 21:07 ` (subset) [PATCH 0/3] charger-supply for max8997_charger Mark Brown
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=20210130172747.2022977-1-timon.baetz@protonmail.com \
--to=timon.baetz@protonmail.com \
--cc=broonie@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzk@kernel.org \
--cc=lgirdwood@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=robh+dt@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).