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

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <169633065055.2221719.5628262920940888457.b4-ty@ti.com>
Date:   Tue, 3 Oct 2023 16:30:43 +0530
From:   Vignesh Raghavendra <vigneshr@...com>
To:     Nishanth Menon <nm@...com>, Tero Kristo <kristo@...nel.org>,
        Rob Herring <robh+dt@...nel.org>,
        Krzysztof Kozlowski <krzysztof.kozlowski+dt@...aro.org>,
        Conor Dooley <conor+dt@...nel.org>,
        Francesco Dolcini <francesco.dolcini@...adex.com>,
        Francesco Dolcini <francesco@...cini.it>
CC:     Vignesh Raghavendra <vigneshr@...com>,
        <linux-arm-kernel@...ts.infradead.org>,
        <devicetree@...r.kernel.org>, <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH v1] arm64: dts: ti: verdin-am62: disable MIPI DSI bridge

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