linux-kernel - Re: [PATCH] phy: phy-rockchip-samsung-hdptx: Add support for RK3576

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] [thread-next>] [day] [month] [year] [list]

Message-ID: <751f18a4-900b-4644-9ae7-d28fa44888da@collabora.com>
Date: Thu, 6 Mar 2025 22:21:01 +0200
From: Cristian Ciocaltea <cristian.ciocaltea@...labora.com>
To: Nicolas Frattaroli <nicolas.frattaroli@...labora.com>,
 Heiko Stuebner <heiko@...ech.de>, Andy Yan <andyshrk@....com>,
 Vinod Koul <vkoul@...nel.org>, Kishon Vijay Abraham I <kishon@...nel.org>
Cc: Sebastian Reichel <sebastian.reichel@...labora.com>,
 kernel@...labora.com, linux-phy@...ts.infradead.org,
 linux-arm-kernel@...ts.infradead.org, linux-rockchip@...ts.infradead.org,
 linux-kernel@...r.kernel.org
Subject: Re: [PATCH] phy: phy-rockchip-samsung-hdptx: Add support for RK3576

Hi,

On 3/6/25 9:29 PM, Nicolas Frattaroli wrote:
> Despite the compatible already being listed in the bindings, the PHY
> driver never gained explicit support for it. This is especially a
> problem because the explicitly listed PHY addresses need to be specified
> for each SoC.
> 
> To solve this, add the compatible, and a PHY config, with the address
> gleaned from rk3576.dtsi.
> 
> Signed-off-by: Nicolas Frattaroli <nicolas.frattaroli@...labora.com>
> ---
> I thought this must've been already submitted somewhere, but it wasn't
> in linux-next and searching for the modified file on lore also didn't
> yield any results. I guess this slipped through the cracks, and
> torpedoes HDMI support for RK3576 entirely until merged, so it'd be
> great if this could be merged in time for 6.15.
> 
> Let me know if I'm just very confused and this is already handled in
> some other series that's about to be applied.

I'm not aware of this being submitted as part of another series, that's
probably because commit f08d1c085638 ("phy: phy-rockchip-samsung-hdptx:
Don't use dt aliases to determine phy-id"), which actually changed the
approach of mapping the PHY IDs, has been applied fairly recently.

Reviewed-by: Cristian Ciocaltea <cristian.ciocaltea@...labora.com>

Cheers,
Cristian