From: Charles Keepax <ckeepax@opensource.wolfsonmicro.com>
To: broonie@kernel.org
Cc: robh+dt@kernel.org, pawel.moll@arm.com, mark.rutland@arm.com,
ijc+devicetree@hellion.org.uk, galak@codeaurora.org,
rob@landley.net, sameo@linux.intel.com, lee.jones@linaro.org,
lgirdwood@gmail.com, ckeepax@opensource.wolfsonmicro.com,
linux-kernel@vger.kernel.org
Subject: [PATCH 0/5] Arizona regulator updates v3
Date: Wed, 19 Mar 2014 10:18:53 +0000 [thread overview]
Message-ID: <1395224338-3709-1-git-send-email-ckeepax@opensource.wolfsonmicro.com> (raw)
Hi,
This series of patches are small fixes/improvements to the
Arizona regulators. The main thing added is proper device
tree bindings for getting the regulator init_data.
Changes Since v2:
- We now set external_dcvdd in arizona-core and then clear
in the LDO1 regulator driver, such that if the regulator
driver is not compiled in then we will default to an
external DCVDD.
Thanks,
Charles
Charles Keepax (5):
arizona: Correct small errors in the DT binding documentation
mfd: arizona: Fix and factor out read of device tree GPIOs
regulator: arizona-ldo1: Move setup processing from arizona-core
regulator: arizona-ldo1: Add processing of init_data from device tree
regulator: arizona-micsupp: Add processing of init_data from device
tree
Documentation/devicetree/bindings/mfd/arizona.txt | 32 +++++++---
drivers/mfd/arizona-core.c | 43 ++++++++-----
drivers/regulator/arizona-ldo1.c | 70 +++++++++++++++++++++
drivers/regulator/arizona-micsupp.c | 50 +++++++++++++++
include/linux/mfd/arizona/core.h | 3 +
5 files changed, 171 insertions(+), 27 deletions(-)
--
1.7.2.5
next reply other threads:[~2014-03-19 10:27 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-19 10:18 Charles Keepax [this message]
2014-03-19 10:18 ` [PATCH 1/5] arizona: Correct small errors in the DT binding documentation Charles Keepax
2014-03-21 10:54 ` Lee Jones
2014-03-19 10:18 ` [PATCH 2/5] mfd: arizona: Fix and factor out read of device tree GPIOs Charles Keepax
2014-03-21 10:52 ` Lee Jones
2014-03-21 15:44 ` Charles Keepax
2014-03-24 8:44 ` Lee Jones
2014-03-19 10:18 ` [PATCH 3/5] regulator: arizona-ldo1: Move setup processing from arizona-core Charles Keepax
2014-03-21 10:40 ` Lee Jones
2014-03-19 10:18 ` [PATCH 4/5] regulator: arizona-ldo1: Add processing of init_data from device tree Charles Keepax
2014-03-21 10:34 ` Lee Jones
2014-03-21 15:45 ` Charles Keepax
2014-03-19 10:18 ` [PATCH 5/5] regulator: arizona-micsupp: " Charles Keepax
2014-03-21 10:28 ` Lee Jones
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=1395224338-3709-1-git-send-email-ckeepax@opensource.wolfsonmicro.com \
--to=ckeepax@opensource.wolfsonmicro.com \
--cc=broonie@kernel.org \
--cc=galak@codeaurora.org \
--cc=ijc+devicetree@hellion.org.uk \
--cc=lee.jones@linaro.org \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=pawel.moll@arm.com \
--cc=rob@landley.net \
--cc=robh+dt@kernel.org \
--cc=sameo@linux.intel.com \
/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