Skip to contentSkip to conversation

AM43xx & OMAP5 DSS DT changes

PATCH New Tomi Valkeinen 2 participants 12 messages May 21, 2014 Device tree bindings

lore
Share & tools
lore

Tomi Valkeinen

author
#0 lore raw

cover AM43xx & OMAP5 DSS DT changes

Hi,

Here are the AM43xx and OMAP5 display DT changes again. I've sent the clock related changes separately, and I removed OMAP5's RFBI node, which depends on more clock changes. The RFBI driver doesn't work at the moment anyway, so removing the RFBI node should not be an issue.

Tony, if these look fine (the rfbi change is the only one compared to the previous versions), can you queue them for 3.16?

Tomi

Sathya Prakash M R (2):
ARM: dts: am4372.dtsi: add DSS information
ARM: dts: am437x-gp-evm: add LCD data

Tomi Valkeinen (4):
ARM: dts: am43x-epos-evm: add LCD data
ARM: dts: omap5.dtsi: add DSS nodes
ARM: dts: omap5-uevm.dts: add tca6424a
ARM: dts: omap5-uevm.dts: add display nodes

 arch/arm/boot/dts/am4372.dtsi        |  30 +++++++++++
 arch/arm/boot/dts/am437x-gp-evm.dts  |  97 +++++++++++++++++++++++++++++++++
 arch/arm/boot/dts/am43x-epos-evm.dts | 101 +++++++++++++++++++++++++++++++++++
 arch/arm/boot/dts/omap5-uevm.dts     |  89 ++++++++++++++++++++++++++++++
 arch/arm/boot/dts/omap5.dtsi         |  61 +++++++++++++++++++++
 5 files changed, 378 insertions(+)
Signature · 1 line
1.9.1
author
#1 lore raw

PATCH 1/6 ARM: dts: am4372.dtsi: add DSS information

From: Sathya Prakash M R <[email protected]>

Add DT data for the display subsystem for AM4372. The DSS on AM4372 is basically OMAP3's DSS, without DSI and VENC blocks.

Signed-off-by Sathya Prakash M R <[email protected]>
Signed-off-by Tomi Valkeinen <[email protected]>
---
 arch/arm/boot/dts/am4372.dtsi | 30 ++++++++++++++++++++++++++++++
 1 file changed, 30 insertions(+)
arch/arm/boot/dts/am4372.dtsi +30 -0
index d1f8707ff1df..8fd413d6d14b 100644
@@ -735,6 +735,36 @@
 			#size-cells = <1>;
 			status = "disabled";
 		};
+
+		dss: dss at 4832a000 {
+			compatible = "ti,omap3-dss";
+			reg = <0x4832a000 0x200>;
+			status = "disabled";
+			ti,hwmods = "dss_core";
+			clocks = <&disp_clk>;
+			clock-names = "fck";
+			#address-cells = <1>;
+			#size-cells = <1>;
+			ranges;
+
+			dispc at 4832a400 {
+				compatible = "ti,omap3-dispc";
+				reg = <0x4832a400 0x400>;
+				interrupts = <GIC_SPI 127 IRQ_TYPE_LEVEL_HIGH>;
+				ti,hwmods = "dss_dispc";
+				clocks = <&disp_clk>;
+				clock-names = "fck";
+			};
+
+			rfbi: rfbi at 4832a800 {
+				compatible = "ti,omap3-rfbi";
+				reg = <0x4832a800 0x100>;
+				ti,hwmods = "dss_rfbi";
+				clocks = <&disp_clk>;
+				clock-names = "fck";
+			};
+
+		};
 	};
 };
Signature · 1 line
1.9.1
author
#2 lore raw

PATCH 2/6 ARM: dts: am437x-gp-evm: add LCD data

In reply to Tomi Valkeinen

From: Sathya Prakash M R <[email protected]>

Add DT data for am437x-gp-evm's LCD panel.

Signed-off-by Sathya Prakash M R <[email protected]>
Signed-off-by Tomi Valkeinen <[email protected]>
---
 arch/arm/boot/dts/am437x-gp-evm.dts | 97 +++++++++++++++++++++++++++++++++++++
 1 file changed, 97 insertions(+)
arch/arm/boot/dts/am437x-gp-evm.dts +97 -0
index df8798e8bd25..350e896a0d89 100644
@@ -53,6 +53,48 @@
 				0x02000069      /* LEFT */
 				0x0201006c>;      /* DOWN */
 		};
+
+	aliases {
+		display0 = &lcd0;
+	};
+
+	lcd0: display {
+		compatible = "osddisplays,osd057T0559-34ts", "panel-dpi";
+		label = "lcd";
+
+		pinctrl-names = "default";
+		pinctrl-0 = <&lcd_pins>;
+
+		/*
+		 * SelLCDorHDMI, LOW to select HDMI. This is not really the
+		 * panel's enable GPIO, but we don't have HDMI driver support nor
+		 * support to switch between two displays, so using this gpio as
+		 * panel's enable should be safe.
+		 */
+		enable-gpios = <&gpio5 8 GPIO_ACTIVE_HIGH>;
+
+		panel-timing {
+			clock-frequency = <33000000>;
+			hactive = <800>;
+			vactive = <480>;
+			hfront-porch = <210>;
+			hback-porch = <16>;
+			hsync-len = <30>;
+			vback-porch = <10>;
+			vfront-porch = <22>;
+			vsync-len = <13>;
+			hsync-active = <0>;
+			vsync-active = <0>;
+			de-active = <1>;
+			pixelclk-active = <1>;
+		};
+
+		port {
+			lcd_in: endpoint {
+				remote-endpoint = <&dpi_out>;
+			};
+		};
+	};
 };
 
 &am43xx_pinmux {

@@ -81,6 +123,47 @@
 			0x164 MUX_MODE0       /* eCAP0_in_PWM0_out.eCAP0_in_PWM0_out MODE0 */
 		>;
 	};
+
+	dss_pins: dss_pins {
+		pinctrl-single,pins = <
+			0x020 (PIN_OUTPUT_PULLUP | MUX_MODE1) /*gpmc ad 8 -> DSS DATA 23 */
+			0x024 (PIN_OUTPUT_PULLUP | MUX_MODE1)
+			0x028 (PIN_OUTPUT_PULLUP | MUX_MODE1)
+			0x02c (PIN_OUTPUT_PULLUP | MUX_MODE1)
+			0x030 (PIN_OUTPUT_PULLUP | MUX_MODE1)
+			0x034 (PIN_OUTPUT_PULLUP | MUX_MODE1)
+			0x038 (PIN_OUTPUT_PULLUP | MUX_MODE1)
+			0x03c (PIN_OUTPUT_PULLUP | MUX_MODE1) /*gpmc ad 15 -> DSS DATA 16 */
+			0x0a0 (PIN_OUTPUT_PULLUP | MUX_MODE0) /* DSS DATA 0 */
+			0x0a4 (PIN_OUTPUT_PULLUP | MUX_MODE0)
+			0x0a8 (PIN_OUTPUT_PULLUP | MUX_MODE0)
+			0x0ac (PIN_OUTPUT_PULLUP | MUX_MODE0)
+			0x0b0 (PIN_OUTPUT_PULLUP | MUX_MODE0)
+			0x0b4 (PIN_OUTPUT_PULLUP | MUX_MODE0)
+			0x0b8 (PIN_OUTPUT_PULLUP | MUX_MODE0)
+			0x0bc (PIN_OUTPUT_PULLUP | MUX_MODE0)
+			0x0c0 (PIN_OUTPUT_PULLUP | MUX_MODE0)
+			0x0c4 (PIN_OUTPUT_PULLUP | MUX_MODE0)
+			0x0c8 (PIN_OUTPUT_PULLUP | MUX_MODE0)
+			0x0cc (PIN_OUTPUT_PULLUP | MUX_MODE0)
+			0x0d0 (PIN_OUTPUT_PULLUP | MUX_MODE0)
+			0x0d4 (PIN_OUTPUT_PULLUP | MUX_MODE0)
+			0x0d8 (PIN_OUTPUT_PULLUP | MUX_MODE0)
+			0x0dc (PIN_OUTPUT_PULLUP | MUX_MODE0) /* DSS DATA 15 */
+			0x0e0 (PIN_OUTPUT_PULLUP | MUX_MODE0) /* DSS VSYNC */
+			0x0e4 (PIN_OUTPUT_PULLUP | MUX_MODE0) /* DSS HSYNC */
+			0x0e8 (PIN_OUTPUT_PULLUP | MUX_MODE0) /* DSS PCLK */
+			0x0ec (PIN_OUTPUT_PULLUP | MUX_MODE0) /* DSS AC BIAS EN */
+
+		>;
+	};
+
+	lcd_pins: lcd_pins {
+		pinctrl-single,pins = <
+			/* GPIO 5_8 to select LCD / HDMI */
+			0x238 (PIN_OUTPUT_PULLUP | MUX_MODE7)
+		>;
+	};
 };
 
 &i2c0 {

@@ -125,3 +208,17 @@
 	pinctrl-0 = <&mmc1_pins>;
 	cd-gpios = <&gpio0 6 GPIO_ACTIVE_HIGH>;
 };
+
+&dss {
+	status = "ok";
+
+	pinctrl-names = "default";
+	pinctrl-0 = <&dss_pins>;
+
+	port {
+		dpi_out: endpoint at 0 {
+			remote-endpoint = <&lcd_in>;
+			data-lines = <24>;
+		};
+	};
+};
Signature · 1 line
1.9.1
author
#3 lore raw

PATCH 3/6 ARM: dts: am43x-epos-evm: add LCD data

In reply to Tomi Valkeinen

Add DT data for am43x-epos-evm's LCD panel.

Signed-off-by Tomi Valkeinen <[email protected]>
---
 arch/arm/boot/dts/am43x-epos-evm.dts | 101 +++++++++++++++++++++++++++++++++++
 1 file changed, 101 insertions(+)
arch/arm/boot/dts/am43x-epos-evm.dts +101 -0
index 167dbc8494de..9aa5af71f96f 100644
@@ -19,6 +19,10 @@
 	model = "TI AM43x EPOS EVM";
 	compatible = "ti,am43x-epos-evm","ti,am4372","ti,am43";
 
+	aliases {
+		display0 = &lcd0;
+	};
+
 	vmmcsd_fixed: fixedregulator-sd {
 		compatible = "regulator-fixed";
 		regulator-name = "vmmcsd_fixed";

@@ -27,6 +31,44 @@
 		enable-active-high;
 	};
 
+	lcd0: display {
+		compatible = "osddisplays,osd057T0559-34ts", "panel-dpi";
+		label = "lcd";
+
+		pinctrl-names = "default";
+		pinctrl-0 = <&lcd_pins>;
+
+		/*
+		 * SelLCDorHDMI, LOW to select HDMI. This is not really the
+		 * panel's enable GPIO, but we don't have HDMI driver support nor
+		 * support to switch between two displays, so using this gpio as
+		 * panel's enable should be safe.
+		 */
+		enable-gpios = <&gpio2 1 GPIO_ACTIVE_HIGH>;
+
+		panel-timing {
+			clock-frequency = <33000000>;
+			hactive = <800>;
+			vactive = <480>;
+			hfront-porch = <210>;
+			hback-porch = <16>;
+			hsync-len = <30>;
+			vback-porch = <10>;
+			vfront-porch = <22>;
+			vsync-len = <13>;
+			hsync-active = <0>;
+			vsync-active = <0>;
+			de-active = <1>;
+			pixelclk-active = <1>;
+		};
+
+		port {
+			lcd_in: endpoint {
+				remote-endpoint = <&dpi_out>;
+			};
+		};
+	};
+
 	am43xx_pinmux: pinmux at 44e10800 {
 		cpsw_default: cpsw_default {
 			pinctrl-single,pins = <

@@ -138,6 +180,46 @@
 				0x160 (PIN_INPUT | MUX_MODE7) /* spi0_cs1.gpio0_6 */
 			>;
 		};
+
+		dss_pins: dss_pins {
+			pinctrl-single,pins = <
+				0x020 (PIN_OUTPUT_PULLUP | MUX_MODE1) /*gpmc ad 8 -> DSS DATA 23 */
+				0x024 (PIN_OUTPUT_PULLUP | MUX_MODE1)
+				0x028 (PIN_OUTPUT_PULLUP | MUX_MODE1)
+				0x02C (PIN_OUTPUT_PULLUP | MUX_MODE1)
+				0x030 (PIN_OUTPUT_PULLUP | MUX_MODE1)
+				0x034 (PIN_OUTPUT_PULLUP | MUX_MODE1)
+				0x038 (PIN_OUTPUT_PULLUP | MUX_MODE1)
+				0x03C (PIN_OUTPUT_PULLUP | MUX_MODE1) /*gpmc ad 15 -> DSS DATA 16 */
+				0x0A0 (PIN_OUTPUT_PULLUP | MUX_MODE0) /* DSS DATA 0 */
+				0x0A4 (PIN_OUTPUT_PULLUP | MUX_MODE0)
+				0x0A8 (PIN_OUTPUT_PULLUP | MUX_MODE0)
+				0x0AC (PIN_OUTPUT_PULLUP | MUX_MODE0)
+				0x0B0 (PIN_OUTPUT_PULLUP | MUX_MODE0)
+				0x0B4 (PIN_OUTPUT_PULLUP | MUX_MODE0)
+				0x0B8 (PIN_OUTPUT_PULLUP | MUX_MODE0)
+				0x0BC (PIN_OUTPUT_PULLUP | MUX_MODE0)
+				0x0C0 (PIN_OUTPUT_PULLUP | MUX_MODE0)
+				0x0C4 (PIN_OUTPUT_PULLUP | MUX_MODE0)
+				0x0C8 (PIN_OUTPUT_PULLUP | MUX_MODE0)
+				0x0CC (PIN_OUTPUT_PULLUP | MUX_MODE0)
+				0x0D0 (PIN_OUTPUT_PULLUP | MUX_MODE0)
+				0x0D4 (PIN_OUTPUT_PULLUP | MUX_MODE0)
+				0x0D8 (PIN_OUTPUT_PULLUP | MUX_MODE0)
+				0x0DC (PIN_OUTPUT_PULLUP | MUX_MODE0) /* DSS DATA 15 */
+				0x0E0 (PIN_OUTPUT_PULLUP | MUX_MODE0) /* DSS VSYNC */
+				0x0E4 (PIN_OUTPUT_PULLUP | MUX_MODE0) /* DSS HSYNC */
+				0x0E8 (PIN_OUTPUT_PULLUP | MUX_MODE0) /* DSS PCLK */
+				0x0EC (PIN_OUTPUT_PULLUP | MUX_MODE0) /* DSS AC BIAS EN */
+			>;
+		};
+
+		lcd_pins: lcd_pins {
+			pinctrl-single,pins = <
+				/* GPMC CLK -> GPIO 2_1 to select LCD / HDMI */
+				0x08C (PIN_OUTPUT_PULLUP | MUX_MODE7)
+			>;
+		};
 	};
 
 	matrix_keypad: matrix_keypad at 0 {

@@ -260,6 +342,10 @@
 	status = "okay";
 };
 
+&gpio5 {
+	status = "okay";
+};
+
 &elm {
 	status = "okay";
 };

@@ -367,3 +453,18 @@
 	pinctrl-0 = <&spi1_pins>;
 	status = "okay";
 };
+
+
+&dss {
+	status = "ok";
+
+	pinctrl-names = "default";
+	pinctrl-0 = <&dss_pins>;
+
+	port {
+		dpi_out: endpoint at 0 {
+			remote-endpoint = <&lcd_in>;
+			data-lines = <24>;
+		};
+	};
+};
Signature · 1 line
1.9.1
author
#4 lore raw

PATCH 4/6 ARM: dts: omap5.dtsi: add DSS nodes

In reply to Tomi Valkeinen

Add OMAP5 DSS nodes to omap5.dtsi.

Signed-off-by Tomi Valkeinen <[email protected]>
---
 arch/arm/boot/dts/omap5.dtsi | 61 ++++++++++++++++++++++++++++++++++++++++++++
 1 file changed, 61 insertions(+)
arch/arm/boot/dts/omap5.dtsi +61 -0
index f8c9855ce587..b80f4c5d0a5b 100644
@@ -869,6 +869,67 @@
 
 			#thermal-sensor-cells = <1>;
 		};
+
+		dss: dss at 58000000 {
+			compatible = "ti,omap5-dss";
+			reg = <0x58000000 0x80>;
+			status = "disabled";
+			ti,hwmods = "dss_core";
+			clocks = <&dss_dss_clk>;
+			clock-names = "fck";
+			#address-cells = <1>;
+			#size-cells = <1>;
+			ranges;
+
+			dispc at 58001000 {
+				compatible = "ti,omap5-dispc";
+				reg = <0x58001000 0x1000>;
+				interrupts = <GIC_SPI 25 IRQ_TYPE_LEVEL_HIGH>;
+				ti,hwmods = "dss_dispc";
+				clocks = <&dss_dss_clk>;
+				clock-names = "fck";
+			};
+
+			dsi1: encoder at 58004000 {
+				compatible = "ti,omap5-dsi";
+				reg = <0x58004000 0x200>,
+				      <0x58004200 0x40>,
+				      <0x58004300 0x40>;
+				reg-names = "proto", "phy", "pll";
+				interrupts = <GIC_SPI 53 IRQ_TYPE_LEVEL_HIGH>;
+				status = "disabled";
+				ti,hwmods = "dss_dsi1";
+				clocks = <&dss_dss_clk>, <&dss_sys_clk>;
+				clock-names = "fck", "sys_clk";
+			};
+
+			dsi2: encoder at 58005000 {
+				compatible = "ti,omap5-dsi";
+				reg = <0x58009000 0x200>,
+				      <0x58009200 0x40>,
+				      <0x58009300 0x40>;
+				reg-names = "proto", "phy", "pll";
+				interrupts = <GIC_SPI 55 IRQ_TYPE_LEVEL_HIGH>;
+				status = "disabled";
+				ti,hwmods = "dss_dsi2";
+				clocks = <&dss_dss_clk>, <&dss_sys_clk>;
+				clock-names = "fck", "sys_clk";
+			};
+
+			hdmi: encoder at 58060000 {
+				compatible = "ti,omap5-hdmi";
+				reg = <0x58040000 0x400>,
+				      <0x58040200 0x80>,
+				      <0x58040300 0x80>,
+				      <0x58060000 0x19000>;
+				reg-names = "wp", "pll", "phy", "core";
+				interrupts = <GIC_SPI 101 IRQ_TYPE_LEVEL_HIGH>;
+				status = "disabled";
+				ti,hwmods = "dss_hdmi";
+				clocks = <&dss_48mhz_clk>, <&dss_sys_clk>;
+				clock-names = "fck", "sys_clk";
+			};
+		};
 	};
 };
Signature · 1 line
1.9.1
author
#5 lore raw

PATCH 5/6 ARM: dts: omap5-uevm.dts: add tca6424a

In reply to Tomi Valkeinen

omap5-uevm has a tca6424a I/O expander. Add it to the .dts file.

Signed-off-by Tomi Valkeinen <[email protected]>
---
 arch/arm/boot/dts/omap5-uevm.dts | 7 +++++++
 1 file changed, 7 insertions(+)
arch/arm/boot/dts/omap5-uevm.dts +7 -0
index 3b99ec25b748..76877516f6df 100644
@@ -434,6 +434,13 @@
 	pinctrl-0 = <&i2c5_pins>;
 
 	clock-frequency = <400000>;
+
+	gpio9: gpio at 22 {
+		compatible = "ti,tca6424";
+		reg = <0x22>;
+		gpio-controller;
+		#gpio-cells = <2>;
+	};
 };
 
 &mcbsp3 {
Signature · 1 line
1.9.1
author
#6 lore raw

PATCH 6/6 ARM: dts: omap5-uevm.dts: add display nodes

In reply to Tomi Valkeinen

omap5-uevm has a single HDMI output. Add the necessary display information, including pinmuxing.

Signed-off-by Tomi Valkeinen <[email protected]>
---
 arch/arm/boot/dts/omap5-uevm.dts | 82 ++++++++++++++++++++++++++++++++++++++++
 1 file changed, 82 insertions(+)
arch/arm/boot/dts/omap5-uevm.dts +82 -0
index 76877516f6df..9ffbe71b88c3 100644
@@ -183,6 +183,19 @@
 		>;
 	};
 
+	dss_hdmi_pins: pinmux_dss_hdmi_pins {
+		pinctrl-single,pins = <
+			0x0fc (PIN_INPUT_PULLUP | MUX_MODE0)	/* hdmi_cec.hdmi_cec */
+			0x100 (PIN_INPUT | MUX_MODE0)	/* hdmi_ddc_scl.hdmi_ddc_scl */
+			0x102 (PIN_INPUT | MUX_MODE0)	/* hdmi_ddc_sda.hdmi_ddc_sda */
+		>;
+	};
+
+	tpd12s015_pins: pinmux_tpd12s015_pins {
+		pinctrl-single,pins = <
+			0x0fe (PIN_INPUT_PULLDOWN | MUX_MODE6)	/* hdmi_hpd.gpio7_193 */
+		>;
+	};
 };
 
 &omap5_pmx_wkup {

@@ -498,3 +511,72 @@
 &cpu0 {
 	cpu0-supply = <&smps123_reg>;
 };
+
+/ {
+	aliases {
+		display0 = &hdmi0;
+	};
+
+	tpd12s015: encoder at 0 {
+		compatible = "ti,tpd12s015";
+
+		pinctrl-names = "default";
+		pinctrl-0 = <&tpd12s015_pins>;
+
+		gpios = <&gpio9 0 GPIO_ACTIVE_HIGH>,	/* TCA6424A P01, CT CP HPD */
+			<&gpio9 1 GPIO_ACTIVE_HIGH>,	/* TCA6424A P00, LS OE */
+			<&gpio7 1 GPIO_ACTIVE_HIGH>;	/* GPIO 193, HPD */
+
+		ports {
+			#address-cells = <1>;
+			#size-cells = <0>;
+
+			port at 0 {
+				reg = <0>;
+
+				tpd12s015_in: endpoint at 0 {
+					remote-endpoint = <&hdmi_out>;
+				};
+			};
+
+			port at 1 {
+				reg = <1>;
+
+				tpd12s015_out: endpoint at 0 {
+					remote-endpoint = <&hdmi_connector_in>;
+				};
+			};
+		};
+	};
+
+	hdmi0: connector at 0 {
+		compatible = "hdmi-connector";
+		label = "hdmi";
+
+		type = "b";
+
+		port {
+			hdmi_connector_in: endpoint {
+				remote-endpoint = <&tpd12s015_out>;
+			};
+		};
+	};
+};
+
+&dss {
+	status = "ok";
+};
+
+&hdmi {
+	status = "ok";
+	vdda-supply = <&ldo4_reg>;
+
+	pinctrl-names = "default";
+	pinctrl-0 = <&dss_hdmi_pins>;
+
+	port {
+		hdmi_out: endpoint {
+			remote-endpoint = <&tpd12s015_in>;
+		};
+	};
+};
Signature · 1 line
1.9.1
#7 lore raw

cover AM43xx & OMAP5 DSS DT changes

In reply to Tomi Valkeinen
Quoted 9 lines · Tomi Valkeinen

Hi,

Here are the AM43xx and OMAP5 display DT changes again. I've sent the clock related changes separately, and I removed OMAP5's RFBI node, which depends on more clock changes. The RFBI driver doesn't work at the moment anyway, so removing the RFBI node should not be an issue.

Tony, if these look fine (the rfbi change is the only one compared to the previous versions), can you queue them for 3.16?

Probably best that you do a late branch again after arm-soc dts changes have been merged. Sounds like you have at least that macro dependency to omap-for-v3.16/dt-v2 so you should probably base your branch on that. So for this:

Acked-by Tony Lindgren <[email protected]>
author
#8 lore raw

cover AM43xx & OMAP5 DSS DT changes

Quoted 8 lines · Tony Lindgren
Quoted 7 lines · Tomi Valkeinen

Hi,

Here are the AM43xx and OMAP5 display DT changes again. I've sent the clock related changes separately, and I removed OMAP5's RFBI node, which depends on more clock changes. The RFBI driver doesn't work at the moment anyway, so removing the RFBI node should not be an issue.

Quoted 6 lines
Quoted 2 lines

Tony, if these look fine (the rfbi change is the only one compared to the previous versions), can you queue them for 3.16?

Probably best that you do a late branch again after arm-soc dts changes have been merged. Sounds like you have at least that macro dependency to omap-for-v3.16/dt-v2 so you should probably base your branch on

There are no dependencies that I know of. Which macro dependency is that?

Tomi

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: OpenPGP digital signature
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20140521/6b68bd54/attachment-0001.sig>

#9 lore raw

cover AM43xx & OMAP5 DSS DT changes

Quoted 9 lines · Tomi Valkeinen
Quoted 8 lines · Tony Lindgren
Quoted 7 lines · Tomi Valkeinen

Hi,

Here are the AM43xx and OMAP5 display DT changes again. I've sent the clock related changes separately, and I removed OMAP5's RFBI node, which depends on more clock changes. The RFBI driver doesn't work at the moment anyway, so removing the RFBI node should not be an issue.

Quoted 8 lines
Quoted 6 lines
Quoted 2 lines

Tony, if these look fine (the rfbi change is the only one compared to the previous versions), can you queue them for 3.16?

Probably best that you do a late branch again after arm-soc dts changes have been merged. Sounds like you have at least that macro dependency to omap-for-v3.16/dt-v2 so you should probably base your branch on

There are no dependencies that I know of. Which macro dependency is that?

Oh for the "[PATCH v2] ARM: dts: duovero-parlor: Add HDMI output" that now uses the OMAP4_IOPAD macro.

Regards,

Tony

author
#10 lore raw

cover AM43xx & OMAP5 DSS DT changes

Quoted 13 lines · Tony Lindgren
Quoted 12 lines · Tomi Valkeinen
Quoted 11 lines · Tony Lindgren
Quoted 9 lines · Tomi Valkeinen

Hi,

Here are the AM43xx and OMAP5 display DT changes again. I've sent the clock related changes separately, and I removed OMAP5's RFBI node, which depends on more clock changes. The RFBI driver doesn't work at the moment anyway, so removing the RFBI node should not be an issue.

Tony, if these look fine (the rfbi change is the only one compared to the previous versions), can you queue them for 3.16?

Quoted 8 lines
Quoted 5 lines
Quoted 3 lines

Probably best that you do a late branch again after arm-soc dts changes have been merged. Sounds like you have at least that macro dependency to omap-for-v3.16/dt-v2 so you should probably base your branch on

There are no dependencies that I know of. Which macro dependency is that?

Oh for the "[PATCH v2] ARM: dts: duovero-parlor: Add HDMI output" that now uses the OMAP4_IOPAD macro.

Ok.

But generally, isn't it better if the .dts changes go through your tree? None of the display related .dts changes have any dependencies to omapdss as such.

I can collect the patches, as I've done, to let them mature a bit in my tree, but I'd rather get them merged via your dt branch.

Tomi

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: OpenPGP digital signature
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20140521/59aee510/attachment.sig>

#11 lore raw

cover AM43xx & OMAP5 DSS DT changes

Quoted 20 lines · Tomi Valkeinen
Quoted 19 lines · Tony Lindgren
Quoted 17 lines · Tomi Valkeinen
Quoted 8 lines · Tony Lindgren
Quoted 7 lines · Tomi Valkeinen

Hi,

Here are the AM43xx and OMAP5 display DT changes again. I've sent the clock related changes separately, and I removed OMAP5's RFBI node, which depends on more clock changes. The RFBI driver doesn't work at the moment anyway, so removing the RFBI node should not be an issue.

Quoted 6 lines
Quoted 2 lines

Tony, if these look fine (the rfbi change is the only one compared to the previous versions), can you queue them for 3.16?

Probably best that you do a late branch again after arm-soc dts changes have been merged. Sounds like you have at least that macro dependency to omap-for-v3.16/dt-v2 so you should probably base your branch on

There are no dependencies that I know of. Which macro dependency is that?

Quoted 8 lines
Quoted 2 lines

Oh for the "[PATCH v2] ARM: dts: duovero-parlor: Add HDMI output" that now uses the OMAP4_IOPAD macro.

Ok.

But generally, isn't it better if the .dts changes go through your tree? None of the display related .dts changes have any dependencies to omapdss as such.

Yes in general, but it's getting very late for v3.16, and..

Quoted 2 lines

I can collect the patches, as I've done, to let them mature a bit in my tree, but I'd rather get them merged via your dt branch.

..I may not queue any more patches for v3.16. The branches I've sent have not yet been merged into arm-soc, so at minimum I'm going to wait for that. If we have -rc6 tagged today and no -rc7, I'm switching into fixes only mode. So in this case it's probably best that you merge them so we can get the display dependency out of the way for v3.16.

Regards,

Tony