From: guodong.xu@linaro.org (Guodong Xu)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 0/6] MFD: add driver for HiSilicon Hi6421v530 PMIC
Date: Fri, 2 Jun 2017 16:51:11 +0800 [thread overview]
Message-ID: <20170602085117.27474-1-guodong.xu@linaro.org> (raw)
This patchset adds driver for HiSilicon Hi6421v530 PMIC.
Mainline kernel already has driver support to a similar chip, Hi6421.
Hi6421 and Hi6421v530 are both from the same vendor, HiSilicon, but
they are at different revisions. They both use the same Memory-mapped
I/O method to communicate with Main SoC. However, they differ quite a
lot in their regulator designs. Eg. they have completely different LDO
voltage points.
Patch 1 and 2 extends hi6421-pmic-core.c to support Hi6421v530 revision.
Patch 3 add hi6421v530-regulator.c driver for LDO regulators.
Patch 4 fixes an issue for hi6421 regulator, which is not related to v530
but it's found in this review.
Patch 5 is dts change, it depends and can be applied on hi3660/hikey960
patchset [1].
Patch 6 enables the relevant config items.
[1], http://www.spinics.net/lists/devicetree/msg178303.html
Major changes in v2:
- instead of writing a new driver, extend hi6421-pmic-core.c
to support its v530 revision
- update hi6421v530-regulator.c to use modern regulator driver
design logics.
Guodong Xu (4):
dt-bindings: mfd: hi6421: Add hi6421v530 compatible string
mfd: hi6421-pmic: add support for HiSilicon Hi6421v530
regulator: hi6421: Describe consumed platform device
arm64: defconfig: enable support hi6421v530 PMIC
Wang Xiaoyin (2):
regulator: hi6421v530: add driver for hi6421v530 voltage regulator
arm64: dts: hikey960: add device node for pmic and regulators
Documentation/devicetree/bindings/mfd/hi6421.txt | 4 +-
arch/arm64/boot/dts/hisilicon/hi3660-hikey960.dts | 46 +++++
arch/arm64/configs/defconfig | 2 +
drivers/mfd/hi6421-pmic-core.c | 56 ++++--
drivers/regulator/Kconfig | 10 ++
drivers/regulator/Makefile | 1 +
drivers/regulator/hi6421-regulator.c | 7 +
drivers/regulator/hi6421v530-regulator.c | 209 ++++++++++++++++++++++
include/linux/mfd/hi6421-pmic.h | 5 +
9 files changed, 326 insertions(+), 14 deletions(-)
create mode 100644 drivers/regulator/hi6421v530-regulator.c
--
2.10.2
next reply other threads:[~2017-06-02 8:51 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-02 8:51 Guodong Xu [this message]
2017-06-02 8:51 ` [PATCH v2 1/6] dt-bindings: mfd: hi6421: Add hi6421v530 compatible string Guodong Xu
2017-06-02 8:51 ` [PATCH v2 2/6] mfd: hi6421-pmic: add support for HiSilicon Hi6421v530 Guodong Xu
2017-06-02 8:51 ` [PATCH v2 3/6] regulator: hi6421v530: add driver for hi6421v530 voltage regulator Guodong Xu
2017-06-02 8:51 ` [PATCH v2 4/6] regulator: hi6421: Describe consumed platform device Guodong Xu
2017-06-07 19:32 ` Applied "regulator: hi6421: Describe consumed platform device" to the regulator tree Mark Brown
2017-06-02 8:51 ` [PATCH v2 5/6] arm64: dts: hikey960: add device node for pmic and regulators Guodong Xu
2017-06-02 8:51 ` [PATCH v2 6/6] arm64: defconfig: enable support hi6421v530 PMIC Guodong Xu
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=20170602085117.27474-1-guodong.xu@linaro.org \
--to=guodong.xu@linaro.org \
--cc=linux-arm-kernel@lists.infradead.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).