From: AnilKumar Ch <anilkumar@ti.com>
To: linux-omap@vger.kernel.org
Cc: tony@atomide.com, b-cousson@ti.com,
linux-arm-kernel@lists.infradead.org,
devicetree-discuss@lists.ozlabs.org, grant.likely@secretlab.ca,
AnilKumar Ch <anilkumar@ti.com>
Subject: [PATCH 2/2] arm/dts: Configure pinmuxs for user leds control on Bone
Date: Thu, 5 Jul 2012 14:43:36 +0530 [thread overview]
Message-ID: <1341479616-18630-3-git-send-email-anilkumar@ti.com> (raw)
In-Reply-To: <1341479616-18630-1-git-send-email-anilkumar@ti.com>
Adds GPIO pinctrl nodes to am3358_pinmux master node to control
user leds (USR0, USR1, USR2 and USR3) present on BeagleBone.
Signed-off-by: AnilKumar Ch <anilkumar@ti.com>
---
arch/arm/boot/dts/am335x-bone.dts | 24 ++++++++++++++++++++++++
1 file changed, 24 insertions(+)
diff --git a/arch/arm/boot/dts/am335x-bone.dts b/arch/arm/boot/dts/am335x-bone.dts
index a9af4db..c3810b7 100644
--- a/arch/arm/boot/dts/am335x-bone.dts
+++ b/arch/arm/boot/dts/am335x-bone.dts
@@ -18,3 +18,27 @@
reg = <0x80000000 0x10000000>; /* 256 MB */
};
};
+
+&am3358_pinmux {
+
+ pinctrl-names = "default";
+ pinctrl-0 = <&userled_pins>;
+
+ userled_pins: pinmux_userled_pins {
+ gpmc_a5.gpio1_21 {
+ pinctrl-simple,cells = <0x54 0x7>; /* OMAP_PIN_OUTPUT | OMAP_MUX_MODE7 */
+ };
+
+ gpmc_a6.gpio1_22 {
+ pinctrl-simple,cells = <0x58 0x17>; /* OMAP_PIN_OUTPUT_PULLUP | OMAP_MUX_MODE7 */
+ };
+
+ gpmc_a7.gpio1_23 {
+ pinctrl-simple,cells = <0x5C 0x7>; /* OMAP_PIN_OUTPUT | OMAP_MUX_MODE7 */
+ };
+
+ gpmc_a8.gpio1_24 {
+ pinctrl-simple,cells = <0x60 0x17>; /* OMAP_PIN_OUTPUT_PULLUP | OMAP_MUX_MODE7 */
+ };
+ };
+};
--
1.7.9.5
WARNING: multiple messages have this Message-ID (diff)
From: anilkumar@ti.com (AnilKumar Ch)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 2/2] arm/dts: Configure pinmuxs for user leds control on Bone
Date: Thu, 5 Jul 2012 14:43:36 +0530 [thread overview]
Message-ID: <1341479616-18630-3-git-send-email-anilkumar@ti.com> (raw)
In-Reply-To: <1341479616-18630-1-git-send-email-anilkumar@ti.com>
Adds GPIO pinctrl nodes to am3358_pinmux master node to control
user leds (USR0, USR1, USR2 and USR3) present on BeagleBone.
Signed-off-by: AnilKumar Ch <anilkumar@ti.com>
---
arch/arm/boot/dts/am335x-bone.dts | 24 ++++++++++++++++++++++++
1 file changed, 24 insertions(+)
diff --git a/arch/arm/boot/dts/am335x-bone.dts b/arch/arm/boot/dts/am335x-bone.dts
index a9af4db..c3810b7 100644
--- a/arch/arm/boot/dts/am335x-bone.dts
+++ b/arch/arm/boot/dts/am335x-bone.dts
@@ -18,3 +18,27 @@
reg = <0x80000000 0x10000000>; /* 256 MB */
};
};
+
+&am3358_pinmux {
+
+ pinctrl-names = "default";
+ pinctrl-0 = <&userled_pins>;
+
+ userled_pins: pinmux_userled_pins {
+ gpmc_a5.gpio1_21 {
+ pinctrl-simple,cells = <0x54 0x7>; /* OMAP_PIN_OUTPUT | OMAP_MUX_MODE7 */
+ };
+
+ gpmc_a6.gpio1_22 {
+ pinctrl-simple,cells = <0x58 0x17>; /* OMAP_PIN_OUTPUT_PULLUP | OMAP_MUX_MODE7 */
+ };
+
+ gpmc_a7.gpio1_23 {
+ pinctrl-simple,cells = <0x5C 0x7>; /* OMAP_PIN_OUTPUT | OMAP_MUX_MODE7 */
+ };
+
+ gpmc_a8.gpio1_24 {
+ pinctrl-simple,cells = <0x60 0x17>; /* OMAP_PIN_OUTPUT_PULLUP | OMAP_MUX_MODE7 */
+ };
+ };
+};
--
1.7.9.5
next prev parent reply other threads:[~2012-07-05 9:13 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-05 9:13 [PATCH 0/2] Add pinctrl support to AM33XX family of devices AnilKumar Ch
2012-07-05 9:13 ` AnilKumar Ch
2012-07-05 9:13 ` [PATCH 1/2] arm/dts: Add AM33XX basic pinctrl support AnilKumar Ch
2012-07-05 9:13 ` AnilKumar Ch
2012-07-06 8:23 ` Tony Lindgren
2012-07-06 8:23 ` Tony Lindgren
2012-07-09 13:37 ` AnilKumar, Chimata
2012-07-09 13:37 ` AnilKumar, Chimata
2012-07-05 9:13 ` AnilKumar Ch [this message]
2012-07-05 9:13 ` [PATCH 2/2] arm/dts: Configure pinmuxs for user leds control on Bone AnilKumar Ch
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=1341479616-18630-3-git-send-email-anilkumar@ti.com \
--to=anilkumar@ti.com \
--cc=b-cousson@ti.com \
--cc=devicetree-discuss@lists.ozlabs.org \
--cc=grant.likely@secretlab.ca \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-omap@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.