linux-kernel - Re: [PATCH] phy/marvell/phy-mvebu-cp110-utmi: fix dr

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: <176898553494.1268719.2606750668583538596.b4-ty@kernel.org>
Date: Wed, 21 Jan 2026 14:22:14 +0530
From: Vinod Koul <vkoul@...nel.org>
To: linux-kernel@...r.kernel.org, kishon@...nel.org, 
 Aleksandar Gerasimovski <aleksandar.gerasimovski@...den.com>
Subject: Re: [PATCH] phy/marvell/phy-mvebu-cp110-utmi: fix dr_mode property
 read from dts


On Tue, 06 Jan 2026 15:06:43 +0000, Aleksandar Gerasimovski wrote:
> The problem with the current implementation is that it does not consider
> that the USB controller can have multiple PHY handles with different
> arguments count, as for example we have in our cn9131 based platform:
> "phys = <&cp0_comphy1 0>, <&cp0_utmi0>;".
> 
> In such case calling "of_usb_get_dr_mode_by_phy" with -1 (no phy-cells)
> leads to not proper phy detection, taking the "marvell,cp110-utmi-phy"
> dts definition we can call the "of_usb_get_dr_mode_by_phy" with 0
> (#phy-cells = <0>) and safely look for that phy.
> 
> [...]

Applied, thanks!

[1/1] phy/marvell/phy-mvebu-cp110-utmi: fix dr_mode property read from dts
      commit: e2ce913452ab56b3330539cc443b97b7ea8c3a1a

Best regards,
-- 
~Vinod