[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20201023201046.GB752111@lunn.ch>
Date: Fri, 23 Oct 2020 22:10:46 +0200
From: Andrew Lunn <andrew@...n.ch>
To: Florian Fainelli <f.fainelli@...il.com>
Cc: Grygorii Strashko <grygorii.strashko@...com>,
"David S. Miller" <davem@...emloft.net>, netdev@...r.kernel.org,
Jakub Kicinski <kuba@...nel.org>,
Heiner Kallweit <hkallweit1@...il.com>,
Sekhar Nori <nsekhar@...com>, linux-kernel@...r.kernel.org,
Vignesh Raghavendra <vigneshr@...com>,
Roger Quadros <rogerq@...com>,
Russell King <linux@...linux.org.uk>,
Sergei Shtylyov <sergei.shtylyov@...entembedded.com>
Subject: Re: [PATCH] RFC: net: phy: of phys probe/reset issue
> Yes there is: have your Ethernet PHY compatible string be of the form
> "ethernetAAAA.BBBB" and then there is no need for such hacking.
> of_get_phy_id() will parse that compatible and that will trigger
> of_mdiobus_register_phy() to take the phy_device_create() path.
Yep. That does seem like the cleanest way to do this. Let the PHY
driver deal with the resources it needs.
Andrew
Powered by blists - more mailing lists