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 01/10] ARM: dts: AM33XX: Add pinmux configuration for matrix keypad to EVM
Date: Mon, 5 Nov 2012 16:15:41 +0530 [thread overview]
Message-ID: <1352112350-13398-2-git-send-email-anilkumar@ti.com> (raw)
In-Reply-To: <1352112350-13398-1-git-send-email-anilkumar@ti.com>
Add pinmux configurations for gpio matrix keypad. In this patch, only
single named mode/state is added and these pins are configured during
pinctrl driver initialization.
Default mode is nothing but the values required for the module during
active state. With this configurations module is functional as
expected.
Signed-off-by: AnilKumar Ch <anilkumar@ti.com>
---
arch/arm/boot/dts/am335x-evm.dts | 15 +++++++++++++++
1 file changed, 15 insertions(+)
diff --git a/arch/arm/boot/dts/am335x-evm.dts b/arch/arm/boot/dts/am335x-evm.dts
index 513284f..9199456 100644
--- a/arch/arm/boot/dts/am335x-evm.dts
+++ b/arch/arm/boot/dts/am335x-evm.dts
@@ -24,6 +24,21 @@
reg = <0x80000000 0x10000000>; /* 256 MB */
};
+ am33xx_pinmux: pinmux@44e10800 {
+ pinctrl-names = "default";
+ pinctrl-0 = <&matrix_keypad_s0>;
+
+ matrix_keypad_s0: matrix_keypad_s0 {
+ pinctrl-single,pins = <
+ 0x54 0x7 /* gpmc_a5.gpio1_21, OUTPUT | MODE7 */
+ 0x58 0x7 /* gpmc_a6.gpio1_22, OUTPUT | MODE7 */
+ 0x64 0x27 /* gpmc_a9.gpio1_25, INPUT | MODE7 */
+ 0x68 0x27 /* gpmc_a10.gpio1_26, INPUT | MODE7 */
+ 0x6c 0x27 /* gpmc_a11.gpio1_27, INPUT | MODE7 */
+ >;
+ };
+ };
+
ocp {
uart1: serial@44e09000 {
status = "okay";
--
1.7.9.5
next prev 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 ` AnilKumar Ch [this message]
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 ` [PATCH 10/10] ARM: dts: AM33XX: Add push-buttons device tree data to am335x-evmsk AnilKumar Ch
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-2-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).