From: Tom Rini Date: Thu, 18 Jun 2020 15:26:12 -0400 Subject: [PATCH 2/4] net: fec: Allow the PHY node to be retrieved In-Reply-To: <20200618190524.21272-2-festevam@gmail.com> References: <20200618190524.21272-1-festevam@gmail.com> <20200618190524.21272-2-festevam@gmail.com> Message-ID: <20200618192612.GZ27801@bill-the-cat> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: u-boot@lists.denx.de On Thu, Jun 18, 2020 at 04:05:22PM -0300, Fabio Estevam wrote: > As we move towards driver model, it is required to let the FEC driver > know how to properly deal with an Ethernet PHY subnode in the device tree. > > For example: > > &fec { > pinctrl-names = "default"; > pinctrl-0 = <&pinctrl_microsom_enet_ar8035>; > phy-handle = <&phy>; > phy-mode = "rgmii-id"; > phy-reset-duration = <2>; > phy-reset-gpios = <&gpio4 15 GPIO_ACTIVE_LOW>; > status = "okay"; > > mdio { > #address-cells = <1>; > #size-cells = <0>; > > phy: ethernet-phy at 0 { > reg = <0>; > qca,clk-out-frequency = <125000000>; > }; > }; > }; > > Currently the PHY node pointer is incorrectly associated with the > Ethernel controller instead of the PHY node itself. > > This causes the PHY properties, such as "qca,clk-out-frequency" in > the example above to not get parsed. > > Fix this problem by populating the phy_of_node node. > > Suggested-by: Vladimir Oltean > Signed-off-by: Fabio Estevam Tested-by: Tom Rini -- Tom -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 659 bytes Desc: not available URL: