devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
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 10/10] ARM: dts: AM33XX: Add push-buttons device tree data to am335x-evmsk
Date: Mon, 5 Nov 2012 16:15:50 +0530	[thread overview]
Message-ID: <1352112350-13398-11-git-send-email-anilkumar@ti.com> (raw)
In-Reply-To: <1352112350-13398-1-git-send-email-anilkumar@ti.com>

Add gpio based push buttons device tree data to am335x-evmsk device
by adding all the necessary parameters like key-code, gpios and etc.

Signed-off-by: AnilKumar Ch <anilkumar@ti.com>
---
 arch/arm/boot/dts/am335x-evmsk.dts |   31 +++++++++++++++++++++++++++++++
 1 file changed, 31 insertions(+)

diff --git a/arch/arm/boot/dts/am335x-evmsk.dts b/arch/arm/boot/dts/am335x-evmsk.dts
index 0f825dd..f5a6162 100644
--- a/arch/arm/boot/dts/am335x-evmsk.dts
+++ b/arch/arm/boot/dts/am335x-evmsk.dts
@@ -139,6 +139,37 @@
 			default-state = "off";
 		};
 	};
+
+	gpio_buttons: gpio_buttons@0 {
+		compatible = "gpio-keys";
+		#address-cells = <1>;
+		#size-cells = <0>;
+
+		switch@1 {
+			label = "button0";
+			linux,code = <0x100>;
+			gpios = <&gpio3 3 0>;
+		};
+
+		switch@2 {
+			label = "button1";
+			linux,code = <0x101>;
+			gpios = <&gpio3 2 0>;
+		};
+
+		switch@3 {
+			label = "button2";
+			linux,code = <0x102>;
+			gpios = <&gpio1 30 0>;
+			gpio-key,wakeup;
+		};
+
+		switch@4 {
+			label = "button3";
+			linux,code = <0x103>;
+			gpios = <&gpio3 5 0>;
+		};
+	};
 };
 
 /include/ "tps65910.dtsi"
-- 
1.7.9.5


  parent reply	other threads:[~2012-11-05 10:45 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-11-05 10:45 [PATCH 00/10] ARM: dts: AM33XX: Add device tree data AnilKumar Ch
2012-11-05 10:45 ` [PATCH 01/10] ARM: dts: AM33XX: Add pinmux configuration for matrix keypad to EVM AnilKumar Ch
2012-11-05 10:45 ` [PATCH 02/10] ARM: dts: AM33XX: Add matrix keypad device tree data to am335x-evm AnilKumar Ch
2012-11-05 10:45 ` [PATCH 03/10] ARM: dts: AM33XX: Add pinmux configuration for volume-keys to EVM AnilKumar Ch
2012-11-05 10:45 ` [PATCH 04/10] ARM: dts: AM33XX: Add volume-keys device tree data to am335x-evm AnilKumar Ch
2012-11-05 10:45 ` [PATCH 05/10] ARM: dts: AM33XX: Add pinmux configuration for user-leds to BONE AnilKumar Ch
2012-11-05 10:45 ` [PATCH 06/10] ARM: dts: AM33XX: Add user-leds device tree data to am335x-bone AnilKumar Ch
2012-11-05 10:45 ` [PATCH 07/10] ARM: dts: AM33XX: Add pinmux configuration for gpio-leds to EVMSK AnilKumar Ch
2012-11-05 10:45 ` [PATCH 08/10] ARM: dts: AM33XX: Add user-leds device tree data to am335x-evmsk AnilKumar Ch
2012-11-05 10:45 ` [PATCH 09/10] ARM: dts: AM33XX: Add pinmux configuration for gpio-keys to EVMSK AnilKumar Ch
2012-11-05 10:45 ` AnilKumar Ch [this message]
2012-11-05 13:46 ` [PATCH 00/10] ARM: dts: AM33XX: Add device tree data AnilKumar, Chimata
2012-11-05 16:37   ` Benoit Cousson
2012-11-06  4:33     ` 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=1352112350-13398-11-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 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).