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 1/3] driver core: factor sync-state-only link cleanup
Date: Fri, 14 Aug 2026 18:46:15 -0600 [thread overview]
Message-ID: <20260814-submit-phy-package-fwdevlink-v1-v1-1-2319844f057a@gmail.com> (raw)
In-Reply-To: <20260814-submit-phy-package-fwdevlink-v1-v1-0-2319844f057a@gmail.com>
device_links_driver_bound() drops managed sync-state-only links after a
consumer successfully probes, then re-evaluates each affected supplier
for a sync_state() callback.
Frameworks which populate child devices below a driverless device need
to complete the same lifecycle step, but cannot rely on a successful
driver probe to trigger it.
Factor the existing cleanup into a lock-held helper and reuse it from
device_links_driver_bound(). Add a public locking wrapper so frameworks
which populate children below driverless devices can retire temporary
fw_devlink proxy links without affecting real dependency or runtime-PM
links.
Signed-off-by: James Hilliard <james.hilliard1@gmail.com>
---
drivers/base/core.c | 74 ++++++++++++++++++++++++++++++++++++++------------
include/linux/device.h | 1 +
2 files changed, 58 insertions(+), 17 deletions(-)
diff --git a/drivers/base/core.c b/drivers/base/core.c
index 4d026682944f..627fcfa274f0 100644
--- a/drivers/base/core.c
+++ b/drivers/base/core.c
@@ -1305,6 +1305,57 @@ static void device_link_drop_managed(struct device_link *link)
kref_put(&link->kref, __device_link_del);
}
+/* Caller must hold the device links write lock. */
+static void __device_links_drop_sync_state_only(struct device *dev,
+ struct list_head *sync_list)
+{
+ struct device_link *link, *ln;
+
+ list_for_each_entry_safe(link, ln, &dev->links.suppliers, c_node) {
+ struct device *supplier;
+
+ if (!device_link_test(link, DL_FLAG_MANAGED) ||
+ !device_link_test(link, DL_FLAG_SYNC_STATE_ONLY))
+ continue;
+
+ /*
+ * DL_FLAG_SYNC_STATE_ONLY excludes all other managed link flags,
+ * so it is safe to drop the managed link completely.
+ */
+ supplier = link->supplier;
+ device_link_drop_managed(link);
+
+ if (defer_sync_state_count)
+ __device_links_supplier_defer_sync(supplier);
+ else
+ __device_links_queue_sync_state(supplier, sync_list);
+ }
+}
+
+/**
+ * device_links_drop_sync_state_only - Drop managed sync-state-only links
+ * @dev: Consumer device whose proxy links should be dropped
+ *
+ * Frameworks which populate child devices below a driverless device can call
+ * this after adding all of the children. The children will have acquired their
+ * own links by then, so the temporary links which only prevent suppliers from
+ * receiving sync_state() callbacks are no longer needed.
+ *
+ * Re-evaluate each affected supplier for a sync_state() callback after its
+ * link is dropped.
+ */
+void device_links_drop_sync_state_only(struct device *dev)
+{
+ LIST_HEAD(sync_list);
+
+ device_links_write_lock();
+ __device_links_drop_sync_state_only(dev, &sync_list);
+ device_links_write_unlock();
+
+ device_links_flush_sync_list(&sync_list, NULL);
+}
+EXPORT_SYMBOL_GPL(device_links_drop_sync_state_only);
+
static ssize_t waiting_for_supplier_show(struct device *dev,
const struct device_attribute *attr,
char *buf)
@@ -1418,6 +1469,8 @@ void device_links_driver_bound(struct device *dev)
else
__device_links_queue_sync_state(dev, &sync_list);
+ __device_links_drop_sync_state_only(dev, &sync_list);
+
list_for_each_entry_safe(link, ln, &dev->links.suppliers, c_node) {
struct device *supplier;
@@ -1425,17 +1478,10 @@ void device_links_driver_bound(struct device *dev)
continue;
supplier = link->supplier;
- if (device_link_test(link, DL_FLAG_SYNC_STATE_ONLY)) {
- /*
- * When DL_FLAG_SYNC_STATE_ONLY is set, it means no
- * other DL_MANAGED_LINK_FLAGS have been set. So, it's
- * save to drop the managed link completely.
- */
- device_link_drop_managed(link);
- } else if (dev_is_best_effort(dev) &&
- device_link_test(link, DL_FLAG_INFERRED) &&
- link->status != DL_STATE_CONSUMER_PROBE &&
- !dev_can_match(link->supplier)) {
+ if (dev_is_best_effort(dev) &&
+ device_link_test(link, DL_FLAG_INFERRED) &&
+ link->status != DL_STATE_CONSUMER_PROBE &&
+ !dev_can_match(link->supplier)) {
/*
* When dev_is_best_effort() is true, we ignore device
* links to suppliers that don't have a driver. If the
@@ -1449,12 +1495,6 @@ void device_links_driver_bound(struct device *dev)
WRITE_ONCE(link->status, DL_STATE_ACTIVE);
}
- /*
- * This needs to be done even for the deleted
- * DL_FLAG_SYNC_STATE_ONLY device link in case it was the last
- * device link that was preventing the supplier from getting a
- * sync_state() call.
- */
if (defer_sync_state_count)
__device_links_supplier_defer_sync(supplier);
else
diff --git a/include/linux/device.h b/include/linux/device.h
index aee79fd6b32b..8afb9f2b0d82 100644
--- a/include/linux/device.h
+++ b/include/linux/device.h
@@ -1381,6 +1381,7 @@ struct device_link *device_link_add(struct device *consumer,
struct device *supplier, u32 flags);
void device_link_del(struct device_link *link);
void device_link_remove(void *consumer, struct device *supplier);
+void device_links_drop_sync_state_only(struct device *dev);
void device_links_supplier_sync_state_pause(void);
void device_links_supplier_sync_state_resume(void);
void device_link_wait_removal(void);
--
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 ` James Hilliard [this message]
2026-08-15 0:46 ` [PATCH net-next 2/3] of: property: link PHY package suppliers to member PHYs James Hilliard
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-1-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