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
--
To unsubscribe from this list: send the line "unsubscribe linux-omap" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
