From: Vaibhav Hiremath <hvaibhav@ti.com>
To: linux-omap@vger.kernel.org
Cc: linux-arm-kernel@lists.infradead.org,
devicetree-discuss@lists.ozlabs.org, mporter@ti.com,
b-cousson@ti.com, jacmet@sunsite.dk,
Vaibhav Hiremath <hvaibhav@ti.com>
Subject: [PATCH-V2 4/6] ARM: dts: AM33XX: Add pinctrl binding to gpio-leds node
Date: Thu, 28 Mar 2013 12:12:41 +0530 [thread overview]
Message-ID: <1364452963-22083-5-git-send-email-hvaibhav@ti.com> (raw)
In-Reply-To: <1364452963-22083-1-git-send-email-hvaibhav@ti.com>
Now gpio-leds driver is using devm_pinctrl_get_select_default()
api to set default pinmux configuration required for the
functionality of the driver, so this patch moves respective
pinctrl binding inside leds node.
Signed-off-by: Vaibhav Hiremath <hvaibhav@ti.com>
Cc: Benoit Cousson <b-cousson@ti.com>
---
arch/arm/boot/dts/am335x-bone.dts | 5 ++++-
arch/arm/boot/dts/am335x-evmsk.dts | 5 ++++-
2 files changed, 8 insertions(+), 2 deletions(-)
diff --git a/arch/arm/boot/dts/am335x-bone.dts b/arch/arm/boot/dts/am335x-bone.dts
index 860630b..1d623e4 100644
--- a/arch/arm/boot/dts/am335x-bone.dts
+++ b/arch/arm/boot/dts/am335x-bone.dts
@@ -26,7 +26,7 @@
am33xx_pinmux: pinmux@44e10800 {
pinctrl-names = "default";
- pinctrl-0 = <&user_leds_s0>;
+ pinctrl-0 = <>;
user_leds_s0: user_leds_s0 {
pinctrl-single,pins = <
@@ -65,6 +65,9 @@
};
leds {
+ pinctrl-names = "default";
+ pinctrl-0 = <&user_leds_s0>;
+
compatible = "gpio-leds";
led@2 {
diff --git a/arch/arm/boot/dts/am335x-evmsk.dts b/arch/arm/boot/dts/am335x-evmsk.dts
index 15a3052..21d5a08 100644
--- a/arch/arm/boot/dts/am335x-evmsk.dts
+++ b/arch/arm/boot/dts/am335x-evmsk.dts
@@ -32,7 +32,7 @@
am33xx_pinmux: pinmux@44e10800 {
pinctrl-names = "default";
- pinctrl-0 = <&user_leds_s0 &gpio_keys_s0>;
+ pinctrl-0 = <&gpio_keys_s0>;
user_leds_s0: user_leds_s0 {
pinctrl-single,pins = <
@@ -121,6 +121,9 @@
};
leds {
+ pinctrl-names = "default";
+ pinctrl-0 = <&user_leds_s0>;
+
compatible = "gpio-leds";
led@1 {
--
1.7.0.4
next prev parent reply other threads:[~2013-03-28 6:42 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-28 6:42 [PATCH-V2 0/6] ARM: dts: AM33XX: Cleanup and pinctrl binding support Vaibhav Hiremath
[not found] ` <1364452963-22083-1-git-send-email-hvaibhav-l0cyMroinI0@public.gmane.org>
2013-03-28 6:42 ` [PATCH-V2 1/6] ARM: dts: AM33XX: Fix the i2c numbering to match hardware/TRM Vaibhav Hiremath
2013-03-28 6:42 ` [PATCH-V2 6/6] ARM: dts: AM33XX: Add default pinctrl binding for UART0 device Vaibhav Hiremath
2013-03-28 12:26 ` [PATCH-V2 0/6] ARM: dts: AM33XX: Cleanup and pinctrl binding support Benoit Cousson
2013-03-29 14:52 ` Hiremath, Vaibhav
2013-03-28 6:42 ` [PATCH-V2 2/6] ARM: dts: AM33XX: Add default pinctrl binding for I2C device Vaibhav Hiremath
2013-03-28 6:42 ` [PATCH-V2 3/6] ARM: dts: AM33XX: Fix gpio numbering to match hardware/TRM Vaibhav Hiremath
2013-03-28 6:42 ` Vaibhav Hiremath [this message]
2013-03-28 6:42 ` [PATCH-V2 5/6] ARM: dts: AM33XX: Fix uart " Vaibhav Hiremath
2013-03-28 7:07 ` Peter Korsgaard
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=1364452963-22083-5-git-send-email-hvaibhav@ti.com \
--to=hvaibhav@ti.com \
--cc=b-cousson@ti.com \
--cc=devicetree-discuss@lists.ozlabs.org \
--cc=jacmet@sunsite.dk \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-omap@vger.kernel.org \
--cc=mporter@ti.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).