linux-kernel - Re: [PATCH 1/4] arm64: dts: ti: k3-am62x-phyboard-lyra: Set RGB input to 16-bit for HDMI 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: <173523339473.39503.8596566004787069215.b4-ty@ti.com>
Date: Thu, 26 Dec 2024 11:30:00 -0600
From: Nishanth Menon <nm@...com>
To: <vigneshr@...com>, <kristo@...nel.org>, <robh@...nel.org>,
        <krzk+dt@...nel.org>, <conor+dt@...nel.org>,
        Wadim Egorov
	<w.egorov@...tec.de>
CC: Nishanth Menon <nm@...com>, <upstream@...ts.phytec.de>,
        <linux-arm-kernel@...ts.infradead.org>, <devicetree@...r.kernel.org>,
        <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH 1/4] arm64: dts: ti: k3-am62x-phyboard-lyra: Set RGB input to 16-bit for HDMI bridge

Hi Wadim Egorov,

On Fri, 01 Nov 2024 14:14:24 +0100, Wadim Egorov wrote:
> The phyBOARD-Lyra connects only 16 pins to the SII902x HDMI bridge's RGB
> input. The default 24-bit setting causes incorrect color output. Update
> to 16-bit to match the hardware configuration.
> 
> 

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

[1/4] arm64: dts: ti: k3-am62x-phyboard-lyra: Set RGB input to 16-bit for HDMI bridge
      commit: a4b422390be3c4147db6d97b016adecb3573635d
[2/4] arm64: dts: ti: k3-am62x-phyboard-lyra: Add HDMI bridge regulators
      commit: 2a0418ac48d3083e2b209242237abef84497d19f
[3/4] arm64: dts: ti: k3-am62-phycore-som: Define vcc-supply for I2C EEPROM
      commit: 4ffe12ccae4ab20e5dc41dc428f909467ed7cc4d
[4/4] arm64: dts: ti: am62-phyboard-lyra: Provide a vcc-supply for the I2C EEPROM
      commit: 80ad23c4032c6b2afe225c866b9496472965b9ed

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
-- 
Regards,
Nishanth Menon
Key (0xDDB5849D1736249D) / Fingerprint: F8A2 8693 54EB 8232 17A3  1A34 DDB5 849D 1736 249D