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,
linux-arm-kernel@lists.infradead.org,
devicetree-discuss@lists.ozlabs.org
Subject: [PATCH v4 3/3] ARM: dts: imx6q-sabrelite: add eeti egalax
Date: Thu, 16 Aug 2012 18:47:31 +0800 [thread overview]
Message-ID: <1345114051-3052-4-git-send-email-jason77.wang@gmail.com> (raw)
In-Reply-To: <1345114051-3052-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.
Signed-off-by: Hui Wang <jason77.wang@gmail.com>
---
arch/arm/boot/dts/imx6q-sabrelite.dts | 16 ++++++++++++++++
arch/arm/boot/dts/imx6q.dtsi | 7 +++++++
2 files changed, 23 insertions(+), 0 deletions(-)
diff --git a/arch/arm/boot/dts/imx6q-sabrelite.dts b/arch/arm/boot/dts/imx6q-sabrelite.dts
index 72f30f3..337ec74 100644
--- a/arch/arm/boot/dts/imx6q-sabrelite.dts
+++ b/arch/arm/boot/dts/imx6q-sabrelite.dts
@@ -54,6 +54,7 @@
144 0x80000000 /* MX6Q_PAD_EIM_D22__GPIO_3_22 */
121 0x80000000 /* MX6Q_PAD_EIM_D19__GPIO_3_19 */
953 0x80000000 /* MX6Q_PAD_GPIO_0__CCM_CLKO */
+ 972 0x10 /* MX6Q_PAD_GPIO_9__GPIO_1_9 */
>;
};
};
@@ -115,6 +116,21 @@
VDDIO-supply = <®_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 fd57079..6f833b3 100644
--- a/arch/arm/boot/dts/imx6q.dtsi
+++ b/arch/arm/boot/dts/imx6q.dtsi
@@ -552,6 +552,13 @@
};
};
+ i2c3 {
+ pinctrl_i2c3_1: i2c3grp-1 {
+ fsl,pins = <1013 0x4001b8b1 /* MX6Q_PAD_GPIO_5__I2C3_SCL */
+ 1037 0x4001b8b1>; /* MX6Q_PAD_GPIO_16__I2C3_SDA */
+ };
+ };
+
serial2 {
pinctrl_serial2_1: serial2grp-1 {
fsl,pins = <183 0x1b0b1 /* MX6Q_PAD_EIM_D26__UART2_TXD */
--
1.7.6
next prev parent reply other threads:[~2012-08-16 10:48 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-16 10:47 [PATCH v4 0/3] Input: egalax_ts: parse devicetree to get gpio Hui Wang
2012-08-16 10:47 ` [PATCH v4 1/3] Input: egalax_ts: get gpio from devicetree node Hui Wang
2012-08-16 10:47 ` [PATCH v4 2/3] Input: add devicetree binding note for egalax_ts Hui Wang
2012-08-16 10:47 ` Hui Wang [this message]
2012-08-17 0:33 ` [PATCH v4 3/3] ARM: dts: imx6q-sabrelite: add eeti egalax Shawn Guo
2012-08-17 1:20 ` Hui Wang
2012-08-17 0:32 ` [PATCH v4 2/3] Input: add devicetree binding note for egalax_ts Shawn Guo
2012-08-17 0:31 ` [PATCH v4 1/3] Input: egalax_ts: get gpio from devicetree node Shawn Guo
2012-10-09 11:58 ` Arnd Bergmann
2012-10-10 3:26 ` Hui Wang
2012-10-10 6:18 ` 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=1345114051-3052-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-arm-kernel@lists.infradead.org \
--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).