From: AnilKumar Ch <anilkumar@ti.com>
To: tony@atomide.com
Cc: b-cousson@ti.com, linux-arm-kernel@lists.infradead.org,
linux-omap@vger.kernel.org, grant.likely@secretlab.ca,
devicetree-discuss@lists.ozlabs.org,
AnilKumar Ch <anilkumar@ti.com>
Subject: [PATCH RESEND 06/10] ARM: dts: AM33XX: Add user-leds device tree data to am335x-bone
Date: Tue, 6 Nov 2012 19:18:34 +0530 [thread overview]
Message-ID: <1352209718-5586-7-git-send-email-anilkumar@ti.com> (raw)
In-Reply-To: <1352209718-5586-1-git-send-email-anilkumar@ti.com>
Add gpio-leds device tree data to am335x-bone device to enable gpio
based user-leds (USR0, USR1, USR2 and USR3) present on BeagleBone.
[koen@dominion.thruhere.net: led0, led1 suggested by koen]
Signed-off-by: AnilKumar Ch <anilkumar@ti.com>
---
arch/arm/boot/dts/am335x-bone.dts | 30 ++++++++++++++++++++++++++++++
1 file changed, 30 insertions(+)
diff --git a/arch/arm/boot/dts/am335x-bone.dts b/arch/arm/boot/dts/am335x-bone.dts
index 1aac58b..2c33888 100644
--- a/arch/arm/boot/dts/am335x-bone.dts
+++ b/arch/arm/boot/dts/am335x-bone.dts
@@ -53,6 +53,36 @@
};
};
+
+ leds {
+ compatible = "gpio-leds";
+
+ led@2 {
+ label = "beaglebone:green:heartbeat";
+ gpios = <&gpio2 21 0>;
+ linux,default-trigger = "heartbeat";
+ default-state = "off";
+ };
+
+ led@3 {
+ label = "beaglebone:green:mmc0";
+ gpios = <&gpio2 22 0>;
+ linux,default-trigger = "mmc0";
+ default-state = "off";
+ };
+
+ led@4 {
+ label = "beaglebone:green:usr2";
+ gpios = <&gpio2 23 0>;
+ default-state = "off";
+ };
+
+ led@5 {
+ label = "beaglebone:green:usr3";
+ gpios = <&gpio2 24 0>;
+ default-state = "off";
+ };
+ };
};
/include/ "tps65217.dtsi"
--
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 RESEND 06/10] ARM: dts: AM33XX: Add user-leds device tree data to am335x-bone
Date: Tue, 6 Nov 2012 19:18:34 +0530 [thread overview]
Message-ID: <1352209718-5586-7-git-send-email-anilkumar@ti.com> (raw)
In-Reply-To: <1352209718-5586-1-git-send-email-anilkumar@ti.com>
Add gpio-leds device tree data to am335x-bone device to enable gpio
based user-leds (USR0, USR1, USR2 and USR3) present on BeagleBone.
[koen at dominion.thruhere.net: led0, led1 suggested by koen]
Signed-off-by: AnilKumar Ch <anilkumar@ti.com>
---
arch/arm/boot/dts/am335x-bone.dts | 30 ++++++++++++++++++++++++++++++
1 file changed, 30 insertions(+)
diff --git a/arch/arm/boot/dts/am335x-bone.dts b/arch/arm/boot/dts/am335x-bone.dts
index 1aac58b..2c33888 100644
--- a/arch/arm/boot/dts/am335x-bone.dts
+++ b/arch/arm/boot/dts/am335x-bone.dts
@@ -53,6 +53,36 @@
};
};
+
+ leds {
+ compatible = "gpio-leds";
+
+ led at 2 {
+ label = "beaglebone:green:heartbeat";
+ gpios = <&gpio2 21 0>;
+ linux,default-trigger = "heartbeat";
+ default-state = "off";
+ };
+
+ led at 3 {
+ label = "beaglebone:green:mmc0";
+ gpios = <&gpio2 22 0>;
+ linux,default-trigger = "mmc0";
+ default-state = "off";
+ };
+
+ led at 4 {
+ label = "beaglebone:green:usr2";
+ gpios = <&gpio2 23 0>;
+ default-state = "off";
+ };
+
+ led at 5 {
+ label = "beaglebone:green:usr3";
+ gpios = <&gpio2 24 0>;
+ default-state = "off";
+ };
+ };
};
/include/ "tps65217.dtsi"
--
1.7.9.5
next prev parent reply other threads:[~2012-11-06 13:50 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-06 13:48 [PATCH RESEND 00/10] ARM: dts: AM33XX: Add device tree data AnilKumar Ch
2012-11-06 13:48 ` AnilKumar Ch
2012-11-06 13:48 ` [PATCH RESEND 01/10] ARM: dts: AM33XX: Add pinmux configuration for matrix keypad to EVM AnilKumar Ch
2012-11-06 13:48 ` AnilKumar Ch
2012-11-06 13:48 ` [PATCH RESEND 02/10] ARM: dts: AM33XX: Add matrix keypad device tree data to am335x-evm AnilKumar Ch
2012-11-06 13:48 ` AnilKumar Ch
2012-11-21 8:58 ` Peter Korsgaard
2012-11-21 8:58 ` Peter Korsgaard
2012-11-06 13:48 ` [PATCH RESEND 03/10] ARM: dts: AM33XX: Add pinmux configuration for volume-keys to EVM AnilKumar Ch
2012-11-06 13:48 ` AnilKumar Ch
2012-11-06 13:48 ` [PATCH RESEND 04/10] ARM: dts: AM33XX: Add volume-keys device tree data to am335x-evm AnilKumar Ch
2012-11-06 13:48 ` AnilKumar Ch
2012-11-06 13:48 ` [PATCH RESEND 05/10] ARM: dts: AM33XX: Add pinmux configuration for user-leds to BONE AnilKumar Ch
2012-11-06 13:48 ` AnilKumar Ch
2012-11-06 13:48 ` AnilKumar Ch [this message]
2012-11-06 13:48 ` [PATCH RESEND 06/10] ARM: dts: AM33XX: Add user-leds device tree data to am335x-bone AnilKumar Ch
2012-11-06 13:48 ` [PATCH RESEND 07/10] ARM: dts: AM33XX: Add pinmux configuration for gpio-leds to EVMSK AnilKumar Ch
2012-11-06 13:48 ` AnilKumar Ch
2012-11-06 13:48 ` [PATCH RESEND 08/10] ARM: dts: AM33XX: Add user-leds device tree data to am335x-evmsk AnilKumar Ch
2012-11-06 13:48 ` AnilKumar Ch
2012-11-06 13:48 ` [PATCH RESEND 09/10] ARM: dts: AM33XX: Add pinmux configuration for gpio-keys to EVMSK AnilKumar Ch
2012-11-06 13:48 ` AnilKumar Ch
2012-11-06 13:48 ` [PATCH RESEND 10/10] ARM: dts: AM33XX: Add push-buttons device tree data to am335x-evmsk AnilKumar Ch
2012-11-06 13:48 ` AnilKumar Ch
2012-11-06 14:56 ` [PATCH RESEND 00/10] ARM: dts: AM33XX: Add device tree data Benoit Cousson
2012-11-06 14:56 ` Benoit Cousson
2012-11-07 8:10 ` AnilKumar, Chimata
2012-11-07 8:10 ` 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=1352209718-5586-7-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.