linux-input.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Hui Wang <jason77.wang@gmail.com>
To: dmitry.torokhov@gmail.com, jiejing.zhang@freescale.com,
	shawn.guo@linaro.org
Cc: linux-input@vger.kernel.org, devicetree-discuss@lists.ozlabs.org
Subject: [PATCH v4 RESEND 3/3] ARM: dts: imx6q-sabrelite: add eeti egalax
Date: Wed, 10 Oct 2012 17:12:03 +0800	[thread overview]
Message-ID: <1349860323-12786-4-git-send-email-jason77.wang@gmail.com> (raw)
In-Reply-To: <1349860323-12786-3-git-send-email-jason77.wang@gmail.com>

i.MX6Q sabrelite board uses i2c3 to connect an eeti egalax
touchscreen controller, add it as an i2c slave device in the dts.

Reviewed-by: Shawn Guo <shawn.guo@linaro.org>
Signed-off-by: Hui Wang <jason77.wang@gmail.com>
---
 arch/arm/boot/dts/imx6q-sabrelite.dts |   16 ++++++++++++++++
 arch/arm/boot/dts/imx6q.dtsi          |    9 +++++++++
 2 files changed, 25 insertions(+), 0 deletions(-)

diff --git a/arch/arm/boot/dts/imx6q-sabrelite.dts b/arch/arm/boot/dts/imx6q-sabrelite.dts
index d152328..99bef81 100644
--- a/arch/arm/boot/dts/imx6q-sabrelite.dts
+++ b/arch/arm/boot/dts/imx6q-sabrelite.dts
@@ -59,6 +59,7 @@
 							1262 0x80000000 /* MX6Q_PAD_SD3_DAT5__GPIO_7_0 */
 							1270 0x1f0b0	/* MX6Q_PAD_SD3_DAT4__GPIO_7_1 */
 							953  0x80000000	/* MX6Q_PAD_GPIO_0__CCM_CLKO */
+							972  0x10	/* MX6Q_PAD_GPIO_9__GPIO_1_9 */
 						>;
 					};
 				};
@@ -130,6 +131,21 @@
 					VDDIO-supply = <&reg_3p3v>;
 				};
 			};
+
+			i2c@021a8000 { /* I2C3 */
+				status = "okay";
+				clock-frequency = <100000>;
+				pinctrl-names = "default";
+				pinctrl-0 = <&pinctrl_i2c3_1>;
+
+				egalax_ts@04 {
+					compatible = "eeti,egalax_ts";
+					reg = <0x04>;
+					interrupt-parent = <&gpio1>;
+					interrupts = <9 8>;
+					wakeup-gpios = <&gpio1 9 0>;
+				};
+			};
 		};
 	};
 
diff --git a/arch/arm/boot/dts/imx6q.dtsi b/arch/arm/boot/dts/imx6q.dtsi
index f3990b0..8c5d8d9 100644
--- a/arch/arm/boot/dts/imx6q.dtsi
+++ b/arch/arm/boot/dts/imx6q.dtsi
@@ -639,6 +639,15 @@
 					};
 				};
 
+				i2c3 {
+					pinctrl_i2c3_1: i2c3grp-1 {
+						fsl,pins = <
+							1013 0x4001b8b1	/* MX6Q_PAD_GPIO_5__I2C3_SCL */
+							1037 0x4001b8b1	/* MX6Q_PAD_GPIO_16__I2C3_SDA */
+						>;
+					};
+				};
+
 				uart1 {
 					pinctrl_uart1_1: uart1grp-1 {
 						fsl,pins = <
-- 
1.7.6


  reply	other threads:[~2012-10-10  9:12 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-10  9:12 [PATCH v4 RESEND 0/3] Input: egalax_ts: parse devicetree to get gpio Hui Wang
2012-10-10  9:12 ` [PATCH v4 RESEND 1/3] Input: egalax_ts: get gpio from devicetree Hui Wang
2012-10-10  9:12   ` [PATCH v4 RESEND 2/3] Input: add devicetree binding note for Hui Wang
2012-10-10  9:12     ` Hui Wang [this message]
2012-10-10 16:30   ` [PATCH v4 RESEND 1/3] Input: egalax_ts: get gpio from devicetree Dmitry Torokhov
2012-10-11  8:55     ` Shawn Guo
2012-10-11  9:23       ` Hui Wang
2012-10-11 10:19       ` Russell King - ARM Linux
2012-10-11 10:25     ` Arnd Bergmann

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=1349860323-12786-4-git-send-email-jason77.wang@gmail.com \
    --to=jason77.wang@gmail.com \
    --cc=devicetree-discuss@lists.ozlabs.org \
    --cc=dmitry.torokhov@gmail.com \
    --cc=jiejing.zhang@freescale.com \
    --cc=linux-input@vger.kernel.org \
    --cc=shawn.guo@linaro.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).