Rob Herring wrote:
It's not a generic phy. It's a funky "internal phy" that differs among >SOCs. I call it the internal phy, but I could use another name. Internally, >some people call it the "sgmii phy", but I don't think that's accurate.
Funky internal PHYs are precisely the types of PHYs this binding is for. It is generic in that the type is not defined. It can be USB, HDMI, DSI, LVDS, etc.
I don't understand what you're getting at. There are two IP blocks that have a private interconnect. One is the MAC, and the other is an internal PHY, but the driver programs them as one device.
If you want me to make some kind of change, you're going to have to be more specific.
>That's what I thought to, but without it, of_phy_find_device() won't work. >I need a pointer to the phy node, and I use of_parse_phandle() to get it: > > struct device_node *phy_np; > > ret = of_mdiobus_register(mii_bus, np); > if (ret) { > dev_err(&pdev->dev, "could not register mdio bus\n"); > return ret; > } > > phy_np = of_parse_phandle(np, "phy-handle", 0);
You can just as easily find the child node called ethernet-phy.
As Andrew pointed out, using phy-handle allows me to place the phy node anywhere.
I've already made changes to this design, and every change has raised objections. I don't see anything wrong with phy-handle. A lot of drivers use it.
-- Qualcomm Datacenter Technologies, Inc. as an affiliate of Qualcomm Technologies, Inc. Qualcomm Technologies, Inc. is a member of the Code Aurora Forum, a Linux Foundation Collaborative Project. -- To unsubscribe from this list: send the line "unsubscribe devicetree" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
