netdev - Re: [PATCH] net: usb: lan78xx: add weak dependency with micrel phy module

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: <c169a84d-d0e5-4fdf-a112-01ac819447e4@lunn.ch>
Date: Mon, 29 Jul 2024 14:42:12 +0200
From: Andrew Lunn <andrew@...n.ch>
To: Jose Ignacio Tornos Martinez <jtornosm@...hat.com>
Cc: UNGLinuxDriver@...rochip.com, davem@...emloft.net, edumazet@...gle.com,
	gregkh@...uxfoundation.org, kuba@...nel.org,
	linux-kernel@...r.kernel.org, linux-usb@...r.kernel.org,
	lucas.demarchi@...el.com, mcgrof@...nel.org, netdev@...r.kernel.org,
	pabeni@...hat.com, woojung.huh@...rochip.com
Subject: Re: [PATCH] net: usb: lan78xx: add weak dependency with micrel phy
 module

On Mon, Jul 29, 2024 at 10:37:38AM +0200, Jose Ignacio Tornos Martinez wrote:
> Hello Andrew,
> 
> I like the idea from Jakub, reading the associated phy from the hardware
> in some way, although reading your last comments I don't know if it could
> be possible for all the cases.
> Let me ask you about this to understand better, if present,
> always reading /sys/bus/mdio_bus/devices/*/phy_id,
> could it be enough to get the possible related phy? 
> And after this get the related phy module?

There should be sufficient information in /sys. eg.

$ cat /sys/class/net/enp1s0/phydev/phy_id
0x001cc914

So enp1s0 probed a PHY using the ID 0x001cc914. Turn that into binary
and you get 0000 0000 0001 1100 1100 1001 0001 0100. Look that up in alias.

alias mdio:0000000000011100110010?????????? realtek

So you need to realtek PHY driver for my enp1s0.

	Andrew