[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20160311213516.GE19277@lunn.ch>
Date: Fri, 11 Mar 2016 22:35:16 +0100
From: Andrew Lunn <andrew@...n.ch>
To: David Daney <ddaney.cavm@...il.com>
Cc: Florian Fainelli <f.fainelli@...il.com>,
Mark Rutland <mark.rutland@....com>,
Robert Richter <rric@...nel.org>,
Pawel Moll <pawel.moll@....com>,
Ian Campbell <ijc+devicetree@...lion.org.uk>,
netdev@...r.kernel.org, David Daney <david.daney@...ium.com>,
David Daney <ddaney@...iumnetworks.com>,
linux-kernel@...r.kernel.org, Rob Herring <robh+dt@...nel.org>,
Kumar Gala <galak@...eaurora.org>,
Sunil Goutham <sgoutham@...ium.com>,
Radha Mohan Chintakuntla <rchintakuntla@...ium.com>,
"David S. Miller" <davem@...emloft.net>,
linux-arm-kernel@...ts.infradead.org
Subject: Re: [PATCH 1/3] net: thunderx: Cleanup PHY probing code.
> For this phy, we have:
>
> compatible = "cortina,cs4223-slice";
That actually means something else is happening, i think.
of_mdiobus_register() looks at the children, and decides if each child
is a phy or an mdio device, by calling of_mdiobus_child_is_phy().
Since this compatible string is not in whitelist_phys[], it will
return false. of_mdiobus_register() will then do a
of_mdiobus_register_device(). This compatible means it is an MDIO
device, not a PHY. So when you later call of_phy_find_device() it is
always going to return NULL, because there is no PHY there, only an
MDIO device.
How usable is the hardware without a PHY driver? Is a better solution
that your write a very minimal PHY driver?
Andrew
Powered by blists - more mailing lists