From: anilkumar@ti.com (AnilKumar Ch)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 2/2] arm/dts: Configure pinmuxs for user leds control on Bone
Date: Fri, 20 Jul 2012 13:01:48 +0530 [thread overview]
Message-ID: <1342769508-24810-3-git-send-email-anilkumar@ti.com> (raw)
In-Reply-To: <1342769508-24810-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 | 15 +++++++++++++++
1 files changed, 15 insertions(+), 0 deletions(-)
diff --git a/arch/arm/boot/dts/am335x-bone.dts b/arch/arm/boot/dts/am335x-bone.dts
index a4d4415..452ce3f 100644
--- a/arch/arm/boot/dts/am335x-bone.dts
+++ b/arch/arm/boot/dts/am335x-bone.dts
@@ -28,3 +28,18 @@
};
/include/ "tps65217.dtsi"
+
+&am3358_pinmux {
+
+ pinctrl-names = "default";
+ pinctrl-0 = <&userled_pins>;
+
+ userled_pins: pinmux_userled_pins {
+ pinctrl-single,pins = <
+ 0x54 0x7 /* gpmc_a5.gpio1_21, OMAP_PIN_OUTPUT | OMAP_MUX_MODE7 */
+ 0x58 0x17 /* gpmc_a6.gpio1_22, OMAP_PIN_OUTPUT_PULLUP | OMAP_MUX_MODE7 */
+ 0x5C 0x7 /* gpmc_a7.gpio1_23, OMAP_PIN_OUTPUT | OMAP_MUX_MODE7 */
+ 0x60 0x17 /* gpmc_a8.gpio1_24, OMAP_PIN_OUTPUT_PULLUP | OMAP_MUX_MODE7 */
+ >;
+ };
+};
--
1.7.0.4
next prev parent reply other threads:[~2012-07-20 7:31 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-20 7:31 [PATCH v2 0/2] Add pinctrl support to AM33XX family of devices AnilKumar Ch
2012-07-20 7:31 ` [PATCH v2 1/2] arm/dts: Add AM33XX basic pinctrl support AnilKumar Ch
2012-07-24 8:32 ` Tony Lindgren
2012-07-24 9:10 ` AnilKumar, Chimata
2012-07-20 7:31 ` AnilKumar Ch [this message]
2012-07-24 8:30 ` [PATCH v2 2/2] arm/dts: Configure pinmuxs for user leds control on Bone Tony Lindgren
2012-07-24 9:11 ` AnilKumar, Chimata
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=1342769508-24810-3-git-send-email-anilkumar@ti.com \
--to=anilkumar@ti.com \
--cc=linux-arm-kernel@lists.infradead.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).