From: Ian Ray <ian.ray@ge.com>
To: u-boot@lists.denx.de
Subject: [U-Boot, 0/3] power: pmic: add Dialog DA9063 PMIC and regulators
Date: Tue, 14 Jan 2020 15:56:15 +0000 [thread overview]
Message-ID: <cover.1579014062.git.ian.ray@ge.com> (raw)
Add a PMIC driver for DA9063 PMIC and associated registers.
Allow pmic dump command to skip register holes.
Note: This change is a prerequisite for enabling full DM support
for ge_bx50v3_config.
Note: Split out of https://patchwork.ozlabs.org/cover/1182351/.
Feedback in https://patchwork.ozlabs.org/patch/1182404/ and
https://patchwork.ozlabs.org/patch/1182416/ has been addressed.
Martin Fuzzey (3):
power: pmic: add driver for Dialog DA9063 PMIC
power: regulator: add driver for Dialog DA9063 PMIC
pmic: allow dump command for non contiguous register maps
cmd/pmic.c | 12 +-
drivers/power/pmic/Kconfig | 14 ++
drivers/power/pmic/Makefile | 1 +
drivers/power/pmic/da9063.c | 130 +++++++++++++
drivers/power/regulator/Kconfig | 20 ++
drivers/power/regulator/Makefile | 1 +
drivers/power/regulator/da9063.c | 388 +++++++++++++++++++++++++++++++++++++++
include/power/da9063_pmic.h | 320 ++++++++++++++++++++++++++++++++
8 files changed, 884 insertions(+), 2 deletions(-)
create mode 100644 drivers/power/pmic/da9063.c
create mode 100644 drivers/power/regulator/da9063.c
create mode 100644 include/power/da9063_pmic.h
--
2.10.1
next reply other threads:[~2020-01-14 15:56 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-14 15:56 Ian Ray [this message]
2020-01-14 15:56 ` [U-Boot, 1/3] power: pmic: add driver for Dialog DA9063 PMIC Ian Ray
2020-01-28 0:56 ` Tom Rini
2020-01-14 15:56 ` [U-Boot, 2/3] power: regulator: " Ian Ray
2020-01-28 0:56 ` Tom Rini
2020-01-14 15:56 ` [U-Boot, 3/3] pmic: allow dump command for non contiguous register maps Ian Ray
2020-01-28 0:56 ` Tom Rini
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=cover.1579014062.git.ian.ray@ge.com \
--to=ian.ray@ge.com \
--cc=u-boot@lists.denx.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.