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 RESEND 04/10] ARM: dts: AM33XX: Add volume-keys device tree data to am335x-evm
Date: Tue, 6 Nov 2012 19:18:32 +0530	[thread overview]
Message-ID: <1352209718-5586-5-git-send-email-anilkumar@ti.com> (raw)
In-Reply-To: <1352209718-5586-1-git-send-email-anilkumar@ti.com>

Add gpio based volume keys device tree data to am335x-evm by adding
all the required parameters like keycode, gpios and etc.

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

diff --git a/arch/arm/boot/dts/am335x-evm.dts b/arch/arm/boot/dts/am335x-evm.dts
index e087b87..9f65f17 100644
--- a/arch/arm/boot/dts/am335x-evm.dts
+++ b/arch/arm/boot/dts/am335x-evm.dts
@@ -137,6 +137,27 @@
 				0x0101001c	/* ENTER */
 				0x0201006c>;	/* DOWN */
 	};
+
+	gpio_keys: volume_keys@0 {
+		compatible = "gpio-keys";
+		#address-cells = <1>;
+		#size-cells = <0>;
+		autorepeat;
+
+		switch@9 {
+			label = "volume-up";
+			linux,code = <115>;
+			gpios = <&gpio1 2 1>;
+			gpio-key,wakeup;
+		};
+
+		switch@10 {
+			label = "volume-down";
+			linux,code = <114>;
+			gpios = <&gpio1 3 1>;
+			gpio-key,wakeup;
+		};
+	};
 };
 
 /include/ "tps65910.dtsi"
-- 
1.7.9.5


  parent reply	other threads:[~2012-11-06 13:48 UTC|newest]

Thread overview: 14+ 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 ` [PATCH RESEND 01/10] ARM: dts: AM33XX: Add pinmux configuration for matrix keypad to EVM 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-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 [this message]
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 ` [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 ` [PATCH RESEND 08/10] ARM: dts: AM33XX: Add user-leds device tree data to am335x-evmsk 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 ` [PATCH RESEND 10/10] ARM: dts: AM33XX: Add push-buttons device tree data to am335x-evmsk AnilKumar Ch
2012-11-06 14:56 ` [PATCH RESEND 00/10] ARM: dts: AM33XX: Add device tree data Benoit Cousson
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-5-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).