From: Rajendra Nayak <rnayak@ti.com>
To: broonie@opensource.wolfsonmicro.com, devicetree-discuss@lists.ozlabs.org
Cc: linux-omap@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
tony@atomide.com, lrg@ti.com, b-cousson@ti.com,
patches@linaro.org, linaro-dev@lists.linaro.org,
Rajendra Nayak <rnayak@ti.com>
Subject: [PATCH v3 0/2] Device tree support for TWL regulators
Date: Thu, 23 Feb 2012 17:05:52 +0530 [thread overview]
Message-ID: <1329996954-27083-1-git-send-email-rnayak@ti.com> (raw)
Re-sending as these patches did not make it to the lists due to
issues with my 'git send-email'
v3 has mainly 2 differences from v2
-1- TWL driver now uses just one table for both dt and
non-dt based lookup for driver data.
-2- All common regulator nodes for twl4030 and twl6030 are
now defined in the twl4030.dtsi and twl6030.dtsi instead of
repeating the nodes in all board files, which also means
the patch ('arm/dts: twl: Pass regulator data from dt')
has a dependency with the series from Benoit which adds the
twl4030.dtsi and twl6030.dtsi files[1].
I have tested the patches on omap4panda and omap3beagle boards.
[1] git://git.kernel.org/pub/scm/linux/kernel/git/bcousson/linux-omap-dt.git
for_3.4/dt_i2c_twl
Rajendra Nayak (2):
regulator: twl: adapt twl-regulator driver to dt
arm/dts: twl: Pass regulator data from dt
.../bindings/regulator/twl-regulator.txt | 63 ++++++
arch/arm/boot/dts/omap3-beagle.dts | 6 +
arch/arm/boot/dts/twl4030.dtsi | 18 ++
arch/arm/boot/dts/twl6030.dtsi | 60 +++++
drivers/regulator/twl-regulator.c | 227 +++++++++++++-------
5 files changed, 301 insertions(+), 73 deletions(-)
create mode 100644 Documentation/devicetree/bindings/regulator/twl-regulator.txt
next reply other threads:[~2012-02-23 11:35 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-23 11:35 Rajendra Nayak [this message]
2012-02-23 11:35 ` [PATCH v3 1/2] regulator: twl: adapt twl-regulator driver to dt Rajendra Nayak
2012-02-23 15:31 ` Mark Brown
2012-02-24 3:48 ` Rajendra Nayak
[not found] ` <1329996954-27083-1-git-send-email-rnayak-l0cyMroinI0@public.gmane.org>
2012-02-23 11:35 ` [PATCH v3 2/2] arm/dts: twl: Pass regulator data from dt Rajendra Nayak
-- strict thread matches above, loose matches on Subject: below --
2012-02-27 10:35 [PATCH v3 0/2] Device tree support for TWL regulators Rajendra Nayak
2012-02-27 12:15 ` Peter Ujfalusi
2012-02-27 12:31 ` Rajendra Nayak
2012-02-27 13:41 ` Mark Brown
2012-02-27 13:52 ` Cousson, Benoit
2012-02-27 14:03 ` Mark Brown
[not found] ` <20120227140356.GF3191-yzvPICuk2AATkU/dhu1WVueM+bqZidxxQQ4Iyu8u01E@public.gmane.org>
2012-02-27 14:21 ` Cousson, Benoit
[not found] ` <4F4B9166.7020909-l0cyMroinI0@public.gmane.org>
2012-02-27 14:53 ` Mark Brown
2012-02-28 5:41 ` Rajendra Nayak
2012-02-28 10:18 ` Mark Brown
2012-02-27 22:17 ` Grant Likely
[not found] ` <CACxGe6vU2dSpRrqd2y=ssgVsWuwpuvFtja9YcUAQA_ETWcwCYg-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2012-02-27 22:24 ` Cousson, Benoit
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=1329996954-27083-1-git-send-email-rnayak@ti.com \
--to=rnayak@ti.com \
--cc=b-cousson@ti.com \
--cc=broonie@opensource.wolfsonmicro.com \
--cc=devicetree-discuss@lists.ozlabs.org \
--cc=linaro-dev@lists.linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-omap@vger.kernel.org \
--cc=lrg@ti.com \
--cc=patches@linaro.org \
--cc=tony@atomide.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).