Add I2C and it's child device nodes for beagle board.
The I2C1 controller child devices are not populated and it
should be handled along with OMAP clock changes.
Signed-off-by: G, Manjunath Kondaiah <manj...@ti.com>
---
arch/arm/boot/dts/omap3-beagle-nunchuck.dts | 5 ---
arch/arm/boot/dts/omap3-beagle.dts | 42 +++++++++++++++++++++++++++
2 files changed, 42 insertions(+), 5 deletions(-)
diff --git a/arch/arm/boot/dts/omap3-beagle-nunchuck.dts
b/arch/arm/boot/dts/omap3-beagle-nunchuck.dts
index 2607be5..479be11 100644
--- a/arch/arm/boot/dts/omap3-beagle-nunchuck.dts
+++ b/arch/arm/boot/dts/omap3-beagle-nunchuck.dts
@@ -2,11 +2,6 @@
/ {
i2c@48072000 {
- compatible = "ti,omap3-i2c";
- reg = <0x48072000 0x80>;
- #address-cells = <1>;
- #size-cells = <0>;
-
eeprom@50 {
compatible = "at,at24c01";
reg = < 0x50 >;
diff --git a/arch/arm/boot/dts/omap3-beagle.dts
b/arch/arm/boot/dts/omap3-beagle.dts
index 4439466..491ee2b 100644
--- a/arch/arm/boot/dts/omap3-beagle.dts
+++ b/arch/arm/boot/dts/omap3-beagle.dts
@@ -4,4 +4,46 @@
/ {
model = "TI OMAP3 BeagleBoard";
compatible = "ti,omap3-beagle";
+ interrupt-parent = <&gic>;
+
+ gic: interrupt-controller@48241000 {
+ compatible = "ti,omap-gic", "arm,gic";
+ interrupt-controller;
+ #interrupt-cells = <1>;
+ reg = <0x48200000 0x1000>;
+ };
+
+ i2c@48070000 {
+ #address-cells = <1>;
+ #size-cells = <0>;
+ compatible = "ti,omap_i2c";
+ reg = <0x48070000 0x100>;
+ interrupts = < 88 >;
+ interrupt-parent = <&gic>;
+ clock-frequency = <2600>;
+ status = "disabled";
+ };
+
+ i2c@48072000 {
+ #address-cells = <1>;
+ #size-cells = <0>;
+ compatible = "ti,omap_i2c";
+ reg = <0x48072000 0x100>;
+ interrupts = < 89 >;
+ interrupt-parent = <&gic>;
+ clock-frequency = <400>;
+ status = "ok";
+ };
+
+ i2c@48060000 {
+ #address-cells = <1>;
+ #size-cells = <0>;
+ compatible = "ti,omap_i2c";
+ reg = <0x48060000 0x100>;
+ interrupts = < 93 >;
+ interrupt-parent = <&gic>;
+ clock-frequency = <100>;
+ status = "ok";
+ };
+
};
--
1.7.4.1
--
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
