From: Rhyland Klein <rklein@nvidia.com>
To: Mark Brown <broonie@opensource.wolfsonmicro.com>,
Samuel Ortiz <sameo@linux.intel.com>,
Grant Likely <grant.likely@secretlab.ca>,
Rob Herring <rob.herring@calxeda.com>, Liam Girdwood <lrg@ti.com>
Cc: linux-kernel@vger.kernel.org,
devicetree-discuss@lists.ozlabs.org,
Rhyland Klein <rklein@nvidia.com>
Subject: [PATCH 0/8 v2] Update TPS65910 to boot using devicetree
Date: Tue, 24 Apr 2012 16:36:02 -0700 [thread overview]
Message-ID: <1335310570-12455-1-git-send-email-rklein@nvidia.com> (raw)
This patch set updates the tps65910 driver to boot using devicetree.
This patch set now includes an addition to the of_regulator code which will
parse out all the regulator init data for a device given a list of the
regulator names it is expecting and a pointer to the array of where to store
the pointers to the regulator_init_data structures.
Rhyland Klein (8):
regulator: add generic of node parsing for regulators
regulator: add node validation checks
mfd: tps65910: Commonize regmap access through header
regulator: tps65910: Add device tree bindings
mfd: tps65910: Add device-tree support
regulator: tps65910 regulator: add device tree support
mfd: tps65910-irq: Add devicetree init support
ARM: Tegra: Add support for TPS65910 PMIC
Documentation/devicetree/bindings/mfd/tps65910.txt | 133 +++++++++++++
arch/arm/boot/dts/tegra-cardhu.dts | 91 +++++++++
drivers/gpio/gpio-tps65910.c | 14 +-
drivers/mfd/tps65910-irq.c | 55 ++++---
drivers/mfd/tps65910.c | 107 ++++++++---
drivers/regulator/of_regulator.c | 80 ++++++++
drivers/regulator/tps65910-regulator.c | 195 +++++++++++++++-----
include/linux/mfd/tps65910.h | 29 +++-
include/linux/regulator/of_regulator.h | 9 +
9 files changed, 606 insertions(+), 107 deletions(-)
create mode 100644 Documentation/devicetree/bindings/mfd/tps65910.txt
next reply other threads:[~2012-04-24 23:36 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-24 23:36 Rhyland Klein [this message]
2012-04-24 23:36 ` [PATCH 1/8 v2] regulator: add generic of node parsing for regulators Rhyland Klein
[not found] ` <1335310570-12455-1-git-send-email-rklein-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
2012-04-24 23:36 ` [PATCH 2/8 v2] regulator: add node validation checks Rhyland Klein
2012-04-24 23:36 ` [PATCH 3/8 v2] mfd: tps65910: Commonize regmap access through header Rhyland Klein
2012-05-17 23:52 ` Grant Likely
2012-04-24 23:36 ` [PATCH 4/8 v2] regulator: tps65910: Add device tree bindings Rhyland Klein
2012-05-17 23:53 ` Grant Likely
2012-04-24 23:36 ` [PATCH 5/8 v2] mfd: tps65910: Add device-tree support Rhyland Klein
2012-05-17 23:55 ` Grant Likely
2012-04-24 23:36 ` [PATCH 6/8 v2] regulator: tps65910 regulator: add device tree support Rhyland Klein
2012-04-24 23:36 ` [PATCH 7/8 v2] mfd: tps65910-irq: Add devicetree init support Rhyland Klein
2012-05-18 0:00 ` Grant Likely
2012-04-24 23:36 ` [PATCH 8/8 v2] ARM: Tegra: Add support for TPS65910 PMIC Rhyland Klein
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=1335310570-12455-1-git-send-email-rklein@nvidia.com \
--to=rklein@nvidia.com \
--cc=broonie@opensource.wolfsonmicro.com \
--cc=devicetree-discuss@lists.ozlabs.org \
--cc=grant.likely@secretlab.ca \
--cc=linux-kernel@vger.kernel.org \
--cc=lrg@ti.com \
--cc=rob.herring@calxeda.com \
--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;
as well as URLs for NNTP newsgroup(s).