From: James Hilliard <james.hilliard1@gmail.com>
To: Rob Herring <robh@kernel.org>,
Saravana Kannan <saravanak@kernel.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
"Rafael J. Wysocki" <rafael@kernel.org>,
Danilo Krummrich <dakr@kernel.org>, Andrew Lunn <andrew@lunn.ch>,
Heiner Kallweit <hkallweit1@gmail.com>,
Russell King <linux@armlinux.org.uk>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>,
Paolo Abeni <pabeni@redhat.com>
Cc: Christian Marangi <ansuelsmth@gmail.com>,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
driver-core@lists.linux.dev, netdev@vger.kernel.org,
James Hilliard <james.hilliard1@gmail.com>
Subject: [PATCH net-next 2/3] of: property: link PHY package suppliers to member PHYs
Date: Fri, 14 Aug 2026 18:46:16 -0600 [thread overview]
Message-ID: <20260814-submit-phy-package-fwdevlink-v1-v1-2-2319844f057a@gmail.com> (raw)
In-Reply-To: <20260814-submit-phy-package-fwdevlink-v1-v1-0-2319844f057a@gmail.com>
Ethernet PHY package nodes describe shared resources for their member
PHYs, but are not populated as struct devices. fw_devlink consequently
represents the package dependencies with proxy links to the closest
ancestor device.
The MDIO bus is a class device without a driver, so such a proxy can
remain available indefinitely and prevent a supplier from receiving its
sync_state() callback even after every PHY has probed.
Treat every enabled member PHY as a consumer of the common package
suppliers. The links can then be converted to links for the real PHY
devices and retired through their normal driver lifecycle.
Fixes: 385ef48f4686 ("net: phy: add support for scanning PHY in PHY packages nodes")
Signed-off-by: James Hilliard <james.hilliard1@gmail.com>
---
drivers/of/property.c | 14 ++++++++++++++
1 file changed, 14 insertions(+)
diff --git a/drivers/of/property.c b/drivers/of/property.c
index 72cf12907de0..f29ba818ecbc 100644
--- a/drivers/of/property.c
+++ b/drivers/of/property.c
@@ -1272,6 +1272,20 @@ static void of_link_to_phandle(struct device_node *con_np,
tmp_np = of_get_next_parent(tmp_np);
}
+ /*
+ * An Ethernet PHY package node describes resources shared by its member
+ * PHYs, but is not populated as a struct device. Link every enabled
+ * member PHY to those suppliers so fw_devlink can use the real consumer
+ * devices instead of leaving a proxy link on the MDIO bus indefinitely.
+ */
+ if (of_node_name_eq(con_np, "ethernet-phy-package")) {
+ for_each_available_child_of_node_scoped(con_np, child)
+ fwnode_link_add(of_fwnode_handle(child),
+ of_fwnode_handle(sup_np), flags);
+
+ return;
+ }
+
fwnode_link_add(of_fwnode_handle(con_np), of_fwnode_handle(sup_np), flags);
}
--
2.53.0
next prev parent reply other threads:[~2026-08-15 0:48 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-15 0:46 [PATCH net-next 0/3] of: mdio: fix fw_devlink for Ethernet PHY packages James Hilliard
2026-08-15 0:46 ` [PATCH net-next 1/3] driver core: factor sync-state-only link cleanup James Hilliard
2026-08-15 0:46 ` James Hilliard [this message]
2026-08-15 0:46 ` [PATCH net-next 3/3] net: mdio: release fw_devlink proxies after population James Hilliard
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20260814-submit-phy-package-fwdevlink-v1-v1-2-2319844f057a@gmail.com \
--to=james.hilliard1@gmail.com \
--cc=andrew@lunn.ch \
--cc=ansuelsmth@gmail.com \
--cc=dakr@kernel.org \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=driver-core@lists.linux.dev \
--cc=edumazet@google.com \
--cc=gregkh@linuxfoundation.org \
--cc=hkallweit1@gmail.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=rafael@kernel.org \
--cc=robh@kernel.org \
--cc=saravanak@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox