[PATCH 17/19] ARM: sun5i: dt: Add display blocks to the DTSI
From: Maxime Ripard
Date: Fri Oct 30 2015 - 10:22:56 EST
The TCON and Display Engines are the two most important members of the
display pipeline.
With this alone, we can already use the display to an RGB interface.
Signed-off-by: Maxime Ripard <maxime.ripard@xxxxxxxxxxxxxxxxxx>
---
arch/arm/boot/dts/sun5i.dtsi | 40 ++++++++++++++++++++++++++++++++++++++++
1 file changed, 40 insertions(+)
diff --git a/arch/arm/boot/dts/sun5i.dtsi b/arch/arm/boot/dts/sun5i.dtsi
index 426db76c0fe6..a67f4bdf5bcc 100644
--- a/arch/arm/boot/dts/sun5i.dtsi
+++ b/arch/arm/boot/dts/sun5i.dtsi
@@ -481,6 +481,20 @@
#size-cells = <0>;
};
+ tcon: lcd-controller@01c0c000 {
+ compatible = "allwinner,sun4i-a10-tcon";
+ reg = <0x01c0c000 0x1000>;
+ interrupts = <44>;
+ clocks = <&ahb_gates 36>,
+ <&tcon_ch0_clk>,
+ <&tcon_ch1_clk>;
+ clock-names = "ahb",
+ "tcon-ch0",
+ "tcon-ch1";
+ clock-output-names = "tcon-pixel-clock";
+ status = "disabled";
+ };
+
mmc0: mmc@01c0f000 {
compatible = "allwinner,sun5i-a13-mmc";
reg = <0x01c0f000 0x1000>;
@@ -767,5 +781,31 @@
interrupts = <82>, <83>;
clocks = <&ahb_gates 28>;
};
+
+ de: display-engine@01e00000 {
+ compatible = "allwinner,sun5i-a13-display-engine";
+ reg = <0x01e00000 0x20000>,
+ <0x01e60000 0x10000>;
+ reg-names = "frontend0",
+ "backend0";
+ interrupts = <47>;
+ interrupt-names = "engine0";
+ clocks = <&ahb_gates 46>, <&de_fe_clk>,
+ <&dram_gates 25>, <&ahb_gates 44>,
+ <&de_be_clk>, <&dram_gates 26>;
+ clock-names = "frontend0-bus", "frontend0-mod",
+ "frontend0-ram", "backend0-bus",
+ "backend0-mod", "backend0-ram";
+ resets = <&de_fe_clk>,
+ <&de_be_clk>;
+ reset-names = "frontend0",
+ "backend0";
+
+ allwinner,tcon = <&tcon>;
+
+ assigned-clocks = <&de_be_clk>;
+ assigned-clock-rates = <300000000>;
+ status = "disabled";
+ };
};
};
--
2.6.2
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/