linux-kernel - Re: net: asix: best way to handle orphan PHYs

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]

Date:   Wed, 9 Mar 2022 16:57:02 +0100
From:   Andrew Lunn <andrew@...n.ch>
To:     Oleksij Rempel <o.rempel@...gutronix.de>
Cc:     "David S. Miller" <davem@...emloft.net>,
        Jakub Kicinski <kuba@...nel.org>,
        Heiner Kallweit <hkallweit1@...il.com>,
        Russell King <linux@...linux.org.uk>, kernel@...gutronix.de,
        linux-kernel@...r.kernel.org, linux-usb@...r.kernel.org,
        netdev@...r.kernel.org, paskripkin@...il.com
Subject: Re: net: asix: best way to handle orphan PHYs

> EEPROM provides information, which PHY address should be used. If
> address is 0x10, it is internal PHY. Different parts of ASIX driver use
> this logic.

O.K, so the solution should be generic, unless there are devices with
bad EEPROM content.

> Ok, so if phy_suspend() is the preffered way, I need to get phydev
> without attaching it. Correct? Do we already have some helpers to do it?

mdiobus_get_phy() will get you the phydev is you know the bus and the
address.

	Andrew