Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20;
Date:   Wed, 9 Mar 2022 16:57:02 +0100
From:   Andrew Lunn <andrew@lunn.ch>
To:     Oleksij Rempel <o.rempel@pengutronix.de>
Cc:     "David S. Miller" <davem@davemloft.net>,
        Jakub Kicinski <kuba@kernel.org>,
        Heiner Kallweit <hkallweit1@gmail.com>,
        Russell King <linux@armlinux.org.uk>, kernel@pengutronix.de,
        linux-kernel@vger.kernel.org, linux-usb@vger.kernel.org,
        netdev@vger.kernel.org, paskripkin@gmail.com
Subject: Re: net: asix: best way to handle orphan PHYs
Message-ID: <YijOTgDA95c3uaTl@lunn.ch>
References: <20220309121835.GA15680@pengutronix.de>
 <YiisJogt/WO5gLId@lunn.ch>
 <20220309144523.GE15680@pengutronix.de>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20220309144523.GE15680@pengutronix.de>
Precedence: bulk

> 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