From: Stefan Wahren <stefan.wahren@i2se.com>
To: Liam Girdwood <lgirdwood@gmail.com>,
Mark Brown <broonie@kernel.org>, Rob Herring <robh+dt@kernel.org>,
Mark Rutland <mark.rutland@arm.com>
Cc: Fabio Estevam <fabio.estevam@nxp.com>,
Anson Huang <Anson.Huang@nxp.com>,
linux-imx@nxp.com, linux-kernel@vger.kernel.org,
devicetree@vger.kernel.org,
Stefan Wahren <stefan.wahren@i2se.com>
Subject: [PATCH RFC 0/2] regulator: pfuze100: add pfuze3001 support
Date: Fri, 15 Jun 2018 13:44:51 +0200 [thread overview]
Message-ID: <1529063093-19582-1-git-send-email-stefan.wahren@i2se.com> (raw)
This patch series adds support for the NXP PMIC PF3001. This
based mostly on the patches by Robin Gong and Mauro Salvini from
here [1].
[1] - https://community.nxp.com/docs/DOC-331899
Stefan Wahren (2):
dt-bindings: pfuze100: add pfuze3001 support
regulator: pfuze100: add pfuze3001 support
.../devicetree/bindings/regulator/pfuze100.txt | 77 ++++++++++++++++++++-
drivers/regulator/Kconfig | 4 +-
drivers/regulator/pfuze100-regulator.c | 78 ++++++++++++++++++++--
include/linux/regulator/pfuze100.h | 11 +++
4 files changed, 160 insertions(+), 10 deletions(-)
--
2.7.4
next reply other threads:[~2018-06-15 11:44 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-15 11:44 Stefan Wahren [this message]
2018-06-15 11:44 ` [PATCH RFC 1/2] dt-bindings: pfuze100: add pfuze3001 support Stefan Wahren
2018-06-18 12:01 ` Applied "regulator: pfuze100: add pfuze3001 support" to the regulator tree Mark Brown
2018-06-15 11:44 ` [PATCH RFC 2/2] regulator: pfuze100: add pfuze3001 support Stefan Wahren
2018-06-18 12:01 ` Applied "regulator: pfuze100: add pfuze3001 support" to the regulator tree Mark Brown
2018-06-16 18:40 ` [PATCH RFC 0/2] regulator: pfuze100: add pfuze3001 support Fabio Estevam
2018-06-16 19:25 ` Stefan Wahren
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=1529063093-19582-1-git-send-email-stefan.wahren@i2se.com \
--to=stefan.wahren@i2se.com \
--cc=Anson.Huang@nxp.com \
--cc=broonie@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=fabio.estevam@nxp.com \
--cc=lgirdwood@gmail.com \
--cc=linux-imx@nxp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=robh+dt@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).