From: Laxman Dewangan <ldewangan@nvidia.com>
To: broonie@opensource.wolfsonmicro.com, lrg@ti.com,
rob.herring@calxeda.com, grant.likely@secretlab.ca,
swarren@wwwdotorg.org
Cc: sameo@linux.intel.com, devicetree-discuss@lists.ozlabs.org,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
Laxman Dewangan <ldewangan@nvidia.com>
Subject: [PATCH 0/2] regulator: tps65910: dt: identify regulator by prop regulator-compatible.
Date: Tue, 19 Jun 2012 11:21:25 +0530 [thread overview]
Message-ID: <1340085087-6608-1-git-send-email-ldewangan@nvidia.com> (raw)
Based on the discussion on patch
[PATCH 2/2] ARM: dt: tegra: cardhu: register core regulator tps65911
adding the property "regulator-compatible" for each regulator of device.
Modifying documentation as well to reflect this change.
Adding common API in regulators/of_regualator to match regulator
by their id.
Laxman Dewangan (2):
regulator: support for regulator match by regulator-compatible
regulator: tps65910: dt: identify regulator by regulator-compatible
Documentation/devicetree/bindings/mfd/tps65910.txt | 54 +++++++++++++----
drivers/regulator/of_regulator.c | 61 ++++++++++++++++++++
drivers/regulator/tps65910-regulator.c | 3 +-
include/linux/regulator/of_regulator.h | 13 ++++
4 files changed, 117 insertions(+), 14 deletions(-)
next reply other threads:[~2012-06-19 5:51 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-19 5:51 Laxman Dewangan [this message]
2012-06-19 5:51 ` [PATCH 1/2] regulator: support for regulator match by regulator-compatible Laxman Dewangan
2012-06-19 9:32 ` Mark Brown
2012-06-19 9:34 ` Laxman Dewangan
2012-06-19 10:43 ` Mark Brown
2012-06-19 10:37 ` Laxman Dewangan
2012-06-19 12:06 ` Laxman Dewangan
2012-06-19 12:18 ` Mark Brown
2012-06-19 5:51 ` [PATCH 2/2] regulator: tps65910: dt: identify regulator " Laxman Dewangan
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=1340085087-6608-1-git-send-email-ldewangan@nvidia.com \
--to=ldewangan@nvidia.com \
--cc=broonie@opensource.wolfsonmicro.com \
--cc=devicetree-discuss@lists.ozlabs.org \
--cc=grant.likely@secretlab.ca \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lrg@ti.com \
--cc=rob.herring@calxeda.com \
--cc=sameo@linux.intel.com \
--cc=swarren@wwwdotorg.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).