[PATCH v1] arm64: dts: ti: verdin-am62: disable MIPI DSI bridge

[PATCH v1] arm64: dts: ti: verdin-am62: disable MIPI DSI bridge

[Francesco Dolcini]

From: Francesco Dolcini <francesco.dolcini@toradex.com>

Keep the DPI to MIPI-DSI bridge disabled in the SoM dtsi file.

The display chain is not wholly described in the device tree file, on
Verdin product family the displays are additional accessories that are
configured/enabled using DT overlays.

With this enabled we have issues when a display is enabled on
TIDSS port1 (LVDS) and port0 (DSI) is not used.

Fixes: 9e77200356ba ("arm64: dts: ti: verdin-am62: Add DSI display support")
Signed-off-by: Francesco Dolcini <francesco.dolcini@toradex.com>
---
 arch/arm64/boot/dts/ti/k3-am62-verdin.dtsi | 1 +
 1 file changed, 1 insertion(+)

diff --git a/arch/arm64/boot/dts/ti/k3-am62-verdin.dtsi b/arch/arm64/boot/dts/ti/k3-am62-verdin.dtsi
index 40992e7e4c30..5db52f237253 100644
--- a/arch/arm64/boot/dts/ti/k3-am62-verdin.dtsi
+++ b/arch/arm64/boot/dts/ti/k3-am62-verdin.dtsi
@@ -1061,6 +1061,7 @@ dsi_bridge: dsi@e {
 		vddc-supply = <&reg_1v2_dsi>;
 		vddmipi-supply = <&reg_1v2_dsi>;
 		vddio-supply = <&reg_1v8_dsi>;
+		status = "disabled";
 
 		dsi_bridge_ports: ports {
 			#address-cells = <1>;
-- 
2.25.1

Re: [PATCH v1] arm64: dts: ti: verdin-am62: disable MIPI DSI bridge

[Vignesh Raghavendra]

Hi Francesco Dolcini,

On Fri, 22 Sep 2023 14:30:03 +0200, Francesco Dolcini wrote:
> Keep the DPI to MIPI-DSI bridge disabled in the SoM dtsi file.
> 
> The display chain is not wholly described in the device tree file, on
> Verdin product family the displays are additional accessories that are
> configured/enabled using DT overlays.
> 
> With this enabled we have issues when a display is enabled on
> TIDSS port1 (LVDS) and port0 (DSI) is not used.
> 
> [...]

I have applied the following to branch ti-k3-dts-next on [1].
Thank you!

[1/1] arm64: dts: ti: verdin-am62: disable MIPI DSI bridge
      commit: 664e2852aa9142193c2e241327631f032b966742

All being well this means that it will be integrated into the linux-next
tree (usually sometime in the next 24 hours) and sent up the chain during
the next merge window (or sooner if it is a relevant bug fix), however if
problems are discovered then the patch may be dropped or reverted.

You may get further e-mails resulting from automated or manual testing
and review of the tree, please engage with people reporting problems and
send followup patches addressing any issues that are reported if needed.

If any updates are required or you are submitting further changes they
should be sent as incremental updates against current git, existing
patches will not be replaced.

Please add any relevant lists and maintainers to the CCs when replying
to this mail.

[1] https://git.kernel.org/pub/scm/linux/kernel/git/ti/linux.git
--
Vignesh