From: Denis CIOCCA <denis.ciocca@st.com>
To: Nishanth Menon <nm@ti.com>
Cc: "linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>
Subject: Re: need help to configure IRQ on gpio 139 pandaboard using device tree
Date: Thu, 12 Dec 2013 14:39:26 +0100 [thread overview]
Message-ID: <52A9BC8E.9090007@st.com> (raw)
In-Reply-To: <52A8A1A1.9090104@ti.com>
Hi Nishant,
I've configured the device tree as you told me. Now, my device tree code
is that:
diff --git a/arch/arm/boot/dts/omap4-panda-es.dts
b/arch/arm/boot/dts/omap4-panda-es.dts
index 816d1c9..5644260 100644
--- a/arch/arm/boot/dts/omap4-panda-es.dts
+++ b/arch/arm/boot/dts/omap4-panda-es.dts
@@ -41,6 +41,12 @@
0xb6 (PIN_OUTPUT | MUX_MODE3) /* gpio_110 */
>;
};
+
+ lsm6db0_pins: lsm6db0_pins {
+ pinctrl-single,pins = <
+ 0xfc (PIN_INPUT | MUX_MODE3) /* mcspi1_cs2.gpio_139 */
+ >;
+ };
};
&led_wkgpio_pins {
@@ -49,6 +55,22 @@
>;
};
+&i2c4 {
+ pinctrl-names = "default";
+ pinctrl-0 = <&i2c4_pins>;
+
+ clock-frequency = <400000>;
+
+ lsm6db0@03 {
+ pinctrl-names = "default";
+ pinctrl-0 = <&lsm6db0_pins>;
+ compatible = "st,lsm6db0";
+ reg = <0x03>;
+ interrupts = <139 0x1>;
+ interrupt-parent = <&lsm6db0_pins>;
+ };
+};
+
&leds {
pinctrl-0 = <
&led_gpio_pins
I've also read the documentation file
Documentation/devicetree/bindings/interrupt-controller/interrupts.txt
but I'm confused about the gpio muxed with mcspi1.
Do you think my patch is correct?
Thanks,
Denis
next prev parent reply other threads:[~2013-12-12 13:39 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-11 14:28 need help to configure IRQ on gpio 139 pandaboard using device tree Denis CIOCCA
2013-12-11 15:39 ` menon.nishanth
2013-12-11 16:25 ` Denis CIOCCA
2013-12-11 17:32 ` Nishanth Menon
2013-12-12 13:39 ` Denis CIOCCA [this message]
2013-12-12 14:27 ` Denis CIOCCA
2013-12-12 14:49 ` Nishanth Menon
2013-12-12 15:05 ` Denis CIOCCA
2013-12-12 16:15 ` Nishanth Menon
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=52A9BC8E.9090007@st.com \
--to=denis.ciocca@st.com \
--cc=linux-omap@vger.kernel.org \
--cc=nm@ti.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.