Solve postboot supplier cleanup and optimize probe ordering
Subsystems (6)
v10 cover Solve postboot supplier cleanup and optimize probe ordering
Add device-links to track functional dependencies between devices after they are created (but before they are probed) by looking at their common DT bindings like clocks, interconnects, etc.
Having functional dependencies automatically added before the devices are probed, provides the following benefits:
- Optimizes device probe order and avoids the useless work of attempting probes of devices that will not probe successfully (because their suppliers aren't present or haven't probed yet).
For example, in a commonly available mobile SoC, registering just one consumer device's driver at an initcall level earlier than the supplier device's driver causes 11 failed probe attempts before the consumer device probes successfully. This was with a kernel with all the drivers statically compiled in. This problem gets a lot worse if all the drivers are loaded as modules without direct symbol dependencies.
- Supplier devices like clock providers, interconnect providers, etc need to keep the resources they provide active and at a particular state(s) during boot up even if their current set of consumers don't request the resource to be active. This is because the rest of the consumers might not have probed yet and turning off the resource before all the consumers have probed could lead to a hang or undesired user experience.
Some frameworks (Eg: regulator) handle this today by turning off "unused" resources at late_initcall_sync and hoping all the devices have probed by then. This is not a valid assumption for systems with loadable modules. Other frameworks (Eg: clock) just don't handle this due to the lack of a clear signal for when they can turn off resources. This leads to downstream hacks to handle cases like this that can easily be solved in the upstream kernel.
By linking devices before they are probed, we give suppliers a clear count of the number of dependent consumers. Once all of the consumers are active, the suppliers can turn off the unused resources without making assumptions about the number of consumers.
By default we just add device-links to track "driver presence" (probe succeeded) of the supplier device. If any other functionality provided by device-links are needed, it is left to the consumer/supplier devices to change the link when they probe.
v1 -> v2:
- Drop patch to speed up of_find_device_by_node()
- Drop depends-on property and use existing bindings
v2 -> v3:
- Refactor the code to have driver core initiate the linking of devs
- Have driver core link consumers to supplier before it's probed
- Add support for drivers to edit the device links before probing
v3 -> v4:
- Tested edit_links() on system with cyclic dependency. Works.
- Added some checks to make sure device link isn't attempted from parent device node to child device node.
- Added way to pause/resume sync_state callbacks across of_platform_populate().
- Recursively parse DT node to create device links from parent to suppliers of parent and all child nodes.
v4 -> v5:
- Fixed copy-pasta bugs with linked list handling
- Walk up the phandle reference till I find an actual device (needed for regulators to work)
- Added support for linking devices from regulator DT bindings
- Tested the whole series again to make sure cyclic dependencies are broken with edit_links() and regulator links are created properly.
v5 -> v6:
- Split, squashed and reordered some of the patches.
- Refactored the device linking code to follow the same code pattern for any property.
v6 -> v7:
- No functional changes.
- Renamed i to index
- Added comment to clarify not having to check property name for every index
- Added "matched" variable to clarify code. No functional change.
- Added comments to include/linux/device.h for add_links()
v7 -> v8:
- Rebased on top of linux-next to handle device link changes in [1]
v8 -> v9:
- Fixed kbuild test bot reported errors (docs and const)
v9->v10:
- Changes made based on reviews on LKML [2] and discussions at ELC [3]
- Dropped the edit_links() patch
- Dropped the patch that skips linking for default bus nodes
- 1/7: Changed from bus.add_links() to fwnode.ops.add_links()
- 1/7: Update device link doc
- 1/7: Lots of comments/fn doc updates
- 1/7: Renamed device_link_check_waiting_consumers() to device_link_add_missing_supplier_links()
- 2/7: Moved DT parsing/linking code from of/platform.c to of/property.c
- 2/7: Lots of comments/fn doc updates
- 2/7: Returned errors for all error cases in of_link_to_phandle()
- 2/7: Some minor code refactor to remove "bool done"
- 2/7: Added debug messages when links not created due permanent errors
- 3/7: Minor comments update
- Added 2 new patches 6/7 and 7/7 to handle cyclic dependencies using depends-on
[1] - https://lore.kernel.org/lkml/2305283.AStDPdUUnE@kreacher/
[2] - https://lore.kernel.org/lkml/[email protected]/
[3] - https://lore.kernel.org/lkml/CAGETcx_pSnC_2D7ufLRyfE3b8uRc814XEf8zu+SpNtT7_Z8NLg@mail.gmail.com/
-Saravana
Saravana Kannan (7):
driver core: Add support for linking devices during device addition
of: property: Add functional dependency link from DT bindings driver core: Add sync_state driver/bus callback of/platform: Pause/resume sync state during init and
of_platform_populate()
of: property: Create device links for all child-supplier depencencies
dt-bindings: Add depends-on property to break cyclic inferred
dependencies
of: property: Add "depends-on" parsing support to
of_fwnode_add_links()
.../admin-guide/kernel-parameters.rst | 1 + .../admin-guide/kernel-parameters.txt | 6 + .../devicetree/bindings/depends-on.txt | 46 ++++ Documentation/driver-api/device_link.rst | 3 +- drivers/base/core.c | 154 +++++++++++ drivers/of/platform.c | 12 + drivers/of/property.c | 258 ++++++++++++++++++ include/linux/device.h | 26 ++ include/linux/fwnode.h | 17 ++ 9 files changed, 522 insertions(+), 1 deletion(-) create mode 100644 Documentation/devicetree/bindings/depends-on.txt
Signature · 1 line
2.23.0.187.g17f5b7556c-goog
PATCH v10 1/7 driver core: Add support for linking devices during device addition
The firmware corresponding to a device (dev.fwnode) might be able to provide functional dependency information between a device and its supplier and consumer devices. Tracking this functional dependency allows optimizing device probe order and informing a supplier when all its consumers have probed (and thereby actively managing their resources).
The existing device links feature allows tracking and using supplier-consumer relationships. So, this patch adds the add_links() fwnode callback to allow firmware to create device links for each device as the device is added.
However, when consumer devices are added, they might not have a supplier device to link to despite needing mandatory resources/functionality from one or more suppliers. A waiting_for_suppliers list is created to track such consumers and retry linking them when new devices get added.
--- Documentation/driver-api/device_link.rst | 3 +- drivers/base/core.c | 89 ++++++++++++++++++++++++ include/linux/device.h | 2 + include/linux/fwnode.h | 17 +++++ 4 files changed, 110 insertions(+), 1 deletion(-)
Documentation/driver-api/device_link.rst +2 -1
@@ -281,7 +281,8 @@ State machine :c:func:`driver_bound()`.) * Before a consumer device is probed, presence of supplier drivers is - verified by checking that links to suppliers are in ``DL_STATE_AVAILABLE`` + verified by checking the consumer device is not in the wait_for_suppliers + list and by checking that links to suppliers are in ``DL_STATE_AVAILABLE`` state. The state of the links is updated to ``DL_STATE_CONSUMER_PROBE``. (Call to :c:func:`device_links_check_suppliers()` from :c:func:`really_probe()`.)
drivers/base/core.c +89 -0
125 lines not on this page · raw message
include/linux/device.h +2 -0
@@ -1131,11 +1131,13 @@ enum dl_dev_state {* struct dev_links_info - Device data related to device links. * @suppliers: List of links to supplier devices. * @consumers: List of links to consumer devices. +* @needs_suppliers: Hook to global list of devices waiting for suppliers. * @status: Driver status information. */ struct dev_links_info {struct list_head suppliers;struct list_head consumers; +struct list_head needs_suppliers;enum dl_dev_state status; };
include/linux/fwnode.h +17 -0
@@ -65,6 +65,21 @@ struct fwnode_reference_args {* endpoint node. * @graph_get_port_parent: Return the parent node of a port node. * @graph_parse_endpoint: Parse endpoint for port and endpoint id. +* @add_links: Called after the device corresponding to the fwnode is added +* using device_add(). The function is expected to create device +* links to all the suppliers of the device that are available at +* the time this function is called. The function must NOT stop +* at the first failed device link if other unlinked supplier +* devices are present in the system. If some suppliers are not +* yet available, this function will be called again when other +* devices are added to allow creating device links to any newly +* available suppliers. +* +* Return 0 if device links have been successfully created to all +* the suppliers of this device or if the supplier information is +* not known. Return an error if and only if the supplier +* information is known but some of the suppliers are not yet +* available to create device links to. */ struct fwnode_operations {struct fwnode_handle *(*get)(struct fwnode_handle *fwnode);
@@ -102,6 +117,8 @@ struct fwnode_operations { (*graph_get_port_parent)(struct fwnode_handle *fwnode);int (*graph_parse_endpoint)(const struct fwnode_handle *fwnode,struct fwnode_endpoint *endpoint); +int (*add_links)(const struct fwnode_handle *fwnode, +struct device *dev); };#define fwnode_has_op (fwnode, op) \
Signature · 1 line
2.23.0.187.g17f5b7556c-goog
PATCH v10 2/7 of: property: Add functional dependency link from DT bindings
In reply to Saravana KannanAdd device links after the devices are created (but before they are probed) by looking at common DT bindings like clocks and interconnects.
Automatically adding device links for functional dependencies at the framework level provides the following benefits:
- Optimizes device probe order and avoids the useless work of attempting probes of devices that will not probe successfully (because their suppliers aren't present or haven't probed yet).
For example, in a commonly available mobile SoC, registering just one consumer device's driver at an initcall level earlier than the supplier device's driver causes 11 failed probe attempts before the consumer device probes successfully. This was with a kernel with all the drivers statically compiled in. This problem gets a lot worse if all the drivers are loaded as modules without direct symbol dependencies.
- Supplier devices like clock providers, interconnect providers, etc need to keep the resources they provide active and at a particular state(s) during boot up even if their current set of consumers don't request the resource to be active. This is because the rest of the consumers might not have probed yet and turning off the resource before all the consumers have probed could lead to a hang or undesired user experience.
Some frameworks (Eg: regulator) handle this today by turning off "unused" resources at late_initcall_sync and hoping all the devices have probed by then. This is not a valid assumption for systems with loadable modules. Other frameworks (Eg: clock) just don't handle this due to the lack of a clear signal for when they can turn off resources. This leads to downstream hacks to handle cases like this that can easily be solved in the upstream kernel.
By linking devices before they are probed, we give suppliers a clear count of the number of dependent consumers. Once all of the consumers are active, the suppliers can turn off the unused resources without making assumptions about the number of consumers.
By default we just add device-links to track "driver presence" (probe succeeded) of the supplier device. If any other functionality provided by device-links are needed, it is left to the consumer/supplier devices to change the link when they probe.
kbuild test robot reported clang error about missing const
--- .../admin-guide/kernel-parameters.rst | 1 + .../admin-guide/kernel-parameters.txt | 6 + drivers/of/property.c | 241 ++++++++++++++++++ 3 files changed, 248 insertions(+)
Documentation/admin-guide/kernel-parameters.rst +1 -0
@@ -127,6 +127,7 @@ parameter is applicable:: NET Appropriate network support is enabled. NUMA NUMA support is enabled. NFS Appropriate NFS support is enabled. + OF Devicetree is enabled. OSS OSS sound support is enabled. PV_OPS A paravirtualized kernel is enabled. PARIDE The ParIDE (parallel port IDE) subsystem is enabled.
Documentation/admin-guide/kernel-parameters.txt +6 -0
@@ -3187,6 +3187,12 @@ This can be set from sysctl after boot. See Documentation/admin-guide/sysctl/vm.rst for details. + of_devlink [OF, KNL] Create device links between consumer and + supplier devices by scanning the devictree to infer the + consumer/supplier relationships. A consumer device + will not be probed until all the supplier devices have + probed successfully. + ohci1394_dma=early [HW] enable debugging via the ohci1394 driver. See Documentation/debugging-via-ohci1394.txt for more info.
drivers/of/property.c +241 -0
258 lines not on this page · raw message
Signature · 1 line
2.23.0.187.g17f5b7556c-goog
Re: [PATCH v10 2/7] of: property: Add functional dependency link from DT bindings
Quoted 76 lines · Saravana Kannan
Add device links after the devices are created (but before they are probed) by looking at common DT bindings like clocks and interconnects.
Automatically adding device links for functional dependencies at the framework level provides the following benefits:
- Optimizes device probe order and avoids the useless work of attempting probes of devices that will not probe successfully (because their suppliers aren't present or haven't probed yet).
For example, in a commonly available mobile SoC, registering just one consumer device's driver at an initcall level earlier than the supplier device's driver causes 11 failed probe attempts before the consumer device probes successfully. This was with a kernel with all the drivers statically compiled in. This problem gets a lot worse if all the drivers are loaded as modules without direct symbol dependencies.
- Supplier devices like clock providers, interconnect providers, etc need to keep the resources they provide active and at a particular state(s) during boot up even if their current set of consumers don't request the resource to be active. This is because the rest of the consumers might not have probed yet and turning off the resource before all the consumers have probed could lead to a hang or undesired user experience.
Some frameworks (Eg: regulator) handle this today by turning off "unused" resources at
late_initcall_syncand hoping all the devices have probed by then. This is not a valid assumption for systems with loadable modules. Other frameworks (Eg: clock) just don't handle this due to the lack of a clear signal for when they can turn off resources. This leads to downstream hacks to handle cases like this that can easily be solved in the upstream kernel.By linking devices before they are probed, we give suppliers a clear count of the number of dependent consumers. Once all of the consumers are active, the suppliers can turn off the unused resources without making assumptions about the number of consumers.
By default we just add device-links to track "driver presence" (probe succeeded) of the supplier device. If any other functionality provided by device-links are needed, it is left to the consumer/supplier devices to change the link when they probe.
kbuild test robot reported clang error about missing const
Reported-by kbuild test robot <[email protected]>Signed-off-by Saravana Kannan <[email protected]>--- .../admin-guide/kernel-parameters.rst | 1 + .../admin-guide/kernel-parameters.txt | 6 + drivers/of/property.c | 241 ++++++++++++++++++ 3 files changed, 248 insertions(+)drivers/of/property.c +20
-0+static int of_link_to_phandle (struct device *dev,struct device_node *sup_np) +{ +struct platform_device *sup_dev; +u32 dl_flags =DL_FLAG_AUTOPROBE_CONSUMER ; +int ret =0 ; +struct device_node *tmp_np = sup_np; + +of_node_get (sup_np); +/* +* Find the device node that contains the supplier phandle. It may be +* @sup_np or it may be an ancestor of @sup_np. +*/ +while (sup_np && !of_find_property (sup_np,"compatible" ,NULL )) + sup_np =of_get_next_parent (sup_np); +if (!sup_np) { +dev_dbg (dev,"Not linking to %pOFP - No device\n" , tmp_np); +return -ENODEV ; + } + +/*
drivers/of/property.c of_fwnode_device_get_match_data(const struct fwnode_handle *fwnode, · line 1050
Quoted 10 lines
drivers/of/property.c +10
-0+* Don't allow linking a device node as a consumer of one of its +* descendant nodes. By definition, a child node can't be a functional +* dependency for the parent node. +*/ +if (!of_is_ancestor_of (dev->of_node, sup_np)) { +dev_dbg (dev,"Not linking to %pOFP - is descendant\n" , sup_np); +of_node_put (sup_np); +return -EINVAL ; + } + sup_dev =of_find_device_by_node (sup_np);
What if the supplier isn't a platform_device? A regulator supply is quite likely not.
Rob
PATCH v10 3/7 driver core: Add sync_state driver/bus callback
In reply to Saravana KannanThis sync_state driver/bus callback is called once all the consumers of a supplier have probed successfully.
This allows the supplier device's driver/bus to sync the supplier device's state to the software state with the guarantee that all the consumers are actively managing the resources provided by the supplier device.
To maintain backwards compatibility and ease transition from existing frameworks and resource cleanup schemes, late_initcall_sync is the earliest when the sync_state callback might be called.
There is no upper bound on the time by which the sync_state callback has to be called. This is because if a consumer device never probes, the supplier has to maintain its resources in the state left by the bootloader. For example, if the bootloader leaves the display backlight at a fixed voltage and the backlight driver is never probed, you don't want the backlight to ever be turned off after boot up.
Also, when multiple devices are added after kernel init, some suppliers could be added before their consumer devices get added. In these instances, the supplier devices could get their sync_state callback called right after they probe because the consumers devices haven't had a chance to create device links to the suppliers.
To handle this correctly, this change also provides APIs to pause/resume sync state callbacks so that when multiple devices are added, their sync_state callback evaluation can be postponed to happen after all of them are added.
kbuild test robot reported missing documentation for device.state_synced
--- drivers/base/core.c | 65 ++++++++++++++++++++++++++++++++++++++++++ include/linux/device.h | 24 ++++++++++++++++ 2 files changed, 89 insertions(+)
drivers/base/core.c +65 -0
@@ -46,6 +46,8 @@ early_param("sysfs.deprecated", sysfs_deprecated_setup);/* Device links support. */ static LIST_HEAD (wait_for_suppliers);static DEFINE_MUTEX (wfs_lock); +static LIST_HEAD (deferred_sync); +static unsigned int supplier_sync_state_disabled;#ifdef CONFIG_SRCU static DEFINE_MUTEX (device_links_lock);
@@ -648,6 +650,62 @@ int device_links_check_suppliers(struct device *dev)return ret; } +static void __device_links_supplier_sync_state (struct device *dev) +{ +struct device_link *link; + +if (dev->state_synced) +return ; + +list_for_each_entry (link, &dev->links.consumers, s_node) { +if (!(link->flags &DL_FLAG_MANAGED )) +continue ; +if (link->status !=DL_STATE_ACTIVE ) +return ; + } + +if (dev->bus->sync_state) + dev->bus->sync_state (dev); +else if (dev->driver && dev->driver->sync_state) + dev->driver->sync_state (dev); + + dev->state_synced = true; +} + +void device_links_supplier_sync_state_pause (void ) +{ +device_links_write_lock (); + supplier_sync_state_disabled++; +device_links_write_unlock (); +} + +void device_links_supplier_sync_state_resume (void ) +{ +struct device *dev, *tmp; + +device_links_write_lock (); +if (!supplier_sync_state_disabled) { +WARN (true,"Unmatched sync_state pause/resume!" ); + goto out; + } + supplier_sync_state_disabled--; +if (supplier_sync_state_disabled) + goto out; + +list_for_each_entry_safe (dev, tmp, &deferred_sync, links.defer_sync) { +__device_links_supplier_sync_state (dev); +list_del_init (&dev->links.defer_sync); + } +out: +device_links_write_unlock (); +} + +static void __device_links_supplier_defer_sync (struct device *sup) +{ +if (list_empty (&sup->links.defer_sync)) +list_add_tail (&sup->links.defer_sync, &deferred_sync); +} +/** * device_links_driver_bound - Update device links after probing its driver. * @dev: Device to update the links for.
@@ -692,6 +750,11 @@ void device_links_driver_bound(struct device *dev)WARN_ON (link->status !=DL_STATE_CONSUMER_PROBE );WRITE_ONCE (link->status,DL_STATE_ACTIVE ); + +if (supplier_sync_state_disabled) +__device_links_supplier_defer_sync (link->supplier); +else +__device_links_supplier_sync_state (link->supplier); } dev->links.status =DL_DEV_DRIVER_BOUND ;
@@ -808,6 +871,7 @@ void device_links_driver_cleanup(struct device *dev)WRITE_ONCE (link->status,DL_STATE_DORMANT ); } +list_del_init (&dev->links.defer_sync);__device_links_no_driver (dev);device_links_write_unlock ();
@@ -1782,6 +1846,7 @@ void device_initialize(struct device *dev)INIT_LIST_HEAD (&dev->links.consumers);INIT_LIST_HEAD (&dev->links.suppliers);INIT_LIST_HEAD (&dev->links.needs_suppliers); +INIT_LIST_HEAD (&dev->links.defer_sync); dev->links.status =DL_DEV_NO_DRIVER ; }EXPORT_SYMBOL_GPL (device_initialize);
include/linux/device.h +24 -0
@@ -80,6 +80,13 @@ extern void bus_remove_file(struct bus_type *, struct bus_attribute *);* that generate uevents to add the environment variables. * @probe: Called when a new device or driver add to this bus, and callback * the specific driver's probe to initial the matched device. +* @sync_state: Called to sync device state to software state after all the +* state tracking consumers linked to this device (present at +* the time of late_initcall) have successfully bound to a +* driver. If the device has no consumers, this function will +* be called at late_initcall_sync level. If the device has +* consumers that are never bound to a driver, this function +* will never get called until they do. * @remove: Called when a device removed from this bus. * @shutdown: Called at shut-down time to quiesce the device. *
@@ -123,6 +130,7 @@ struct bus_type {int (*match)(struct device *dev,struct device_driver *drv);int (*uevent)(struct device *dev,struct kobj_uevent_env *env);int (*probe)(struct device *dev); +void (*sync_state)(struct device *dev);int (*remove)(struct device *dev);void (*shutdown)(struct device *dev);
@@ -340,6 +348,13 @@ enum probe_type {* @probe: Called to query the existence of a specific device, * whether this driver can work with it, and bind the driver * to a specific device. +* @sync_state: Called to sync device state to software state after all the +* state tracking consumers linked to this device (present at +* the time of late_initcall) have successfully bound to a +* driver. If the device has no consumers, this function will +* be called at late_initcall_sync level. If the device has +* consumers that are never bound to a driver, this function +* will never get called until they do. * @remove: Called when the device is removed from the system to * unbind a device from this driver. * @shutdown: Called at shut-down time to quiesce the device.
@@ -379,6 +394,7 @@ struct device_driver {const struct acpi_device_id *acpi_match_table;int (*probe) (struct device *dev); +void (*sync_state)(struct device *dev);int (*remove) (struct device *dev);void (*shutdown) (struct device *dev);int (*suspend) (struct device *dev,pm_message_t state);
@@ -1132,12 +1148,14 @@ enum dl_dev_state {* @suppliers: List of links to supplier devices. * @consumers: List of links to consumer devices. * @needs_suppliers: Hook to global list of devices waiting for suppliers. +* @defer_sync: Hook to global list of devices that have deferred sync_state. * @status: Driver status information. */ struct dev_links_info {struct list_head suppliers;struct list_head consumers;struct list_head needs_suppliers; +struct list_head defer_sync;enum dl_dev_state status; };
@@ -1213,6 +1231,9 @@ struct dev_links_info {* @offline: Set after successful invocation of bus type's .offline(). * @of_node_reused: Set if the device-tree node is shared with an ancestor * device. +* @state_synced: The hardware state of this device has been synced to match +* the software state of this device by calling the driver/bus +* sync_state() callback. * @dma_coherent: this particular device is dma coherent, even if the * architecture supports non-coherent devices. *
@@ -1309,6 +1330,7 @@ struct device { bool offline_disabled:1; bool offline:1; bool of_node_reused:1; + bool state_synced:1;#if defined(CONFIG_ARCH_HAS_SYNC_DMA_FOR_DEVICE ) || \ defined(CONFIG_ARCH_HAS_SYNC_DMA_FOR_CPU ) || \ defined(CONFIG_ARCH_HAS_SYNC_DMA_FOR_CPU_ALL )
@@ -1651,6 +1673,8 @@ 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_supplier_sync_state_pause (void ); +void device_links_supplier_sync_state_resume (void );#ifndef dev_fmt#define dev_fmt (fmt) fmt
Signature · 1 line
2.23.0.187.g17f5b7556c-goog
PATCH v10 4/7 of/platform: Pause/resume sync state during init and of_platform_populate()
In reply to Saravana KannanWhen all the top level devices are populated from DT during kernel init, the supplier devices could be added and probed before the consumer devices are added and linked to the suppliers. To avoid the sync_state() callback from being called prematurely, pause the sync_state() callbacks before populating the devices and resume them at late_initcall_sync().
Similarly, when children devices are populated from a module using of_platform_populate(), there could be supplier-consumer dependencies between the children devices that are populated. To avoid the same problem with sync_state() being called prematurely, pause and resume sync_state() callbacks across of_platform_populate().
--- drivers/of/platform.c | 12 ++++++++++++ 1 file changed, 12 insertions(+)
drivers/of/platform.c +12 -0
@@ -480,6 +480,7 @@ int of_platform_populate(struct device_node *root,pr_debug ("%s()\n" , __func__);pr_debug (" starting at: %pOF\n" , root); +device_links_supplier_sync_state_pause ();for_each_child_of_node (root, child) { rc =of_platform_bus_create (child, matches, lookup, parent, true);if (rc) {
@@ -487,6 +488,8 @@ int of_platform_populate(struct device_node *root,break ; } } +device_links_supplier_sync_state_resume (); +of_node_set_flag (root,OF_POPULATED_BUS );of_node_put (root);
@@ -518,6 +521,7 @@ static int __init of_platform_default_populate_init(void)if (!of_have_populated_dt ())return -ENODEV ; +device_links_supplier_sync_state_pause ();/* * Handle certain compatibles explicitly, since we don't want to create * platform_devices for every node in /reserved-memory with a
@@ -538,6 +542,14 @@ static int __init of_platform_default_populate_init(void) return 0; }arch_initcall_sync (of_platform_default_populate_init); + +static int __init of_platform_sync_state_init (void ) +{ +if (of_have_populated_dt ()) +device_links_supplier_sync_state_resume (); +return 0 ; +} +late_initcall_sync (of_platform_sync_state_init);#endif int of_platform_device_destroy (struct device *dev,void *data)
Signature · 1 line
2.23.0.187.g17f5b7556c-goog
PATCH v10 5/7 of: property: Create device links for all child-supplier depencencies
In reply to Saravana KannanA parent device can have child devices that it adds when it probes. But this probing of the parent device can happen way after kernel init is done -- for example, when the parent device's driver is loaded as a module.
In such cases, if the child devices depend on a supplier in the system, we need to make sure the supplier gets the sync_state() callback only after these child devices are added and probed.
To achieve this, when creating device links for a device by looking at its DT node, don't just look at DT references at the top node level. Look at DT references in all the descendant nodes too and create device links from the ancestor device to all these supplier devices.
This way, when the parent device probes and adds child devices, the child devices can then create their own device links to the suppliers and further delay the supplier's sync_state() callback to after the child devices are probed.
Example:
In this illustration, -> denotes DT references and indentation represents child status.
Device node A
Device node B -> D Device node C -> B, D
Device node D
Assume all these devices have their drivers loaded as modules.
Without this patch, this is the sequence of events:
1. D is added.
2. A is added.
3. Device D probes.
4. Device D gets its sync_state() callback.
5. Device B and C might malfunction because their resources got altered/turned off before they can make active requests for them.
With this patch, this is the sequence of events:
1. D is added.
2. A is added and creates device links to D.
3. Device link from A to B is not added because A is a parent of B.
4. Device D probes.
5. Device D does not get it's sync_state() callback because consumer A hasn't probed yet.
5. Device A probes.
5. a. Devices B and C are added.
5. b. Device links from B and C to D are added.
5. c. Device A's probe completes.
6. Device D does not get it's sync_state() callback because consumer A has probed but consumers B and C haven't probed yet.
7. Device B and C probe.
8. Device D gets it's sync_state() callback because all its consumers have probed.
9. None of the devices malfunction.
--- drivers/of/property.c | 4 ++++ 1 file changed, 4 insertions(+)
drivers/of/property.c +4 -0
@@ -1207,6 +1207,10 @@ static int __of_link_to_suppliers(struct device *dev,if (of_link_property (dev, con_np, p->name)) ret = -EAGAIN ; +for_each_child_of_node (con_np, child) +if (__of_link_to_suppliers (dev, child)) + ret = -EAGAIN ; +return ret; }
Signature · 1 line
2.23.0.187.g17f5b7556c-goog
PATCH v10 6/7 dt-bindings: Add depends-on property to break cyclic inferred dependencies
In reply to Saravana KannanThe functional dependencies of a device can be inferred by looking at the common devicetree bindings like clocks, interconnects and regulators.
However, this can sometimes result in cyclic dependencies where one of the inferred dependencies isn't really a functional dependency.
Add a depends-on property that can override inferred dependencies by explicitly listing the suppliers of a device and thereby allow breaking any cyclic inferred depenencies.
--- .../devicetree/bindings/depends-on.txt | 46 +++++++++++++++++++ 1 file changed, 46 insertions(+) create mode 100644 Documentation/devicetree/bindings/depends-on.txt
Documentation/devicetree/bindings/depends-on.txt new file +46 -0
@@ -0,0 +1,46 @@ +Explicit listing of dependencies +================================ + +Apart from parent-child relationships, devices (consumers) often have +functional dependencies on other devices (suppliers). Examples of common +suppliers are clocks, interconnects and regulators. + +The consumer-supplier dependencies of most devices can be inferred by +simply looking at the devicetree bindings of common suppliers like clocks, +interconnects and regulators. However, this can sometimes result in cyclic +dependencies where one of the inferred dependencies isn't really a +functional dependency. + +When there is an inferred cyclic dependency between devices, we need a way +to explicitly list the suppliers of one or more devices in the cycle so +that we can break the cycle. + +The depends-on property fills this need. It can be used to explicitly list +the suppliers of a device and override any inferred dependencies of that +device. + +This property shall be used ONLY to break cyclic dependencies. + +Optional properties: +- depends-on: A list of phandles to suppliers of the device. + +Examples: +Here, the inferred depencency would state that cc2 is dependent on cc1 and +cc3; and cc3 is dependent on cc1 and cc2. This creates a cycle between cc2 +and cc3. + +With the use of depends-on, cc2 is only dependent on cc1; and cc3 is still +dependent on cc1 and cc2. This breaks the cycle between cc2 and cc3. + +cc2: cc2@40031000 { + compatible = "cc2"; + reg = <0x40031000 0x1000>; + clocks = <&cc1 10>, <&cc3 7>; + depends-on = <&cc1>; +}; + +cc3: cc3@40034000 { + compatible = "cc3"; + reg = <0x40031000 0x1000>; + clocks = <&cc1 10>, <&cc2 7>; +};
Signature · 1 line
2.23.0.187.g17f5b7556c-goog
PATCH v10 7/7 of: property: Add "depends-on" parsing support to of_fwnode_add_links()
In reply to Saravana KannanIf dependencies inferred by of_fwnode_add_links() result in a cycle, it can prevent the probing of all the devices in the cycle. The depends-on property has been added to explicitly override inferred dependencies when they create a cycle.
Add depends-on parsing support to of_fwnode_add_links() so that platforms with cyclic dependencies can use "depends-on" to break the cycle and continue successfully probing devices.
--- drivers/of/property.c | 13 +++++++++++++ 1 file changed, 13 insertions(+)
drivers/of/property.c +13 -0
@@ -1106,6 +1106,12 @@ static struct device_node *parse_interconnects(struct device_node *np, "#interconnect-cells"); } +static struct device_node *parse_depends_on (struct device_node *np, +const char *prop_name,int index) +{ +return parse_prop_cells (np, prop_name, index,"depends-on" ,NULL ); +} +static int strcmp_suffix (const char *str,const char *suffix) {unsigned int len, suffix_len;
@@ -1151,6 +1157,7 @@ static const struct supplier_bindings bindings[] = { { .parse_prop = parse_clocks, }, { .parse_prop = parse_interconnects, }, { .parse_prop = parse_regulators, }, + { .parse_prop = parse_depends_on, }, {}, };
@@ -1203,6 +1210,12 @@ static int __of_link_to_suppliers(struct device *dev,struct property *p;int ret =0 ; +if (of_find_property (con_np,"depends-on" ,NULL )) { +if (of_link_property (dev, con_np,"depends-on" )) + ret = -EAGAIN ; +return ret; + } +for_each_property_of_node (con_np, p)if (of_link_property (dev, con_np, p->name)) ret = -EAGAIN ;
Signature · 1 line
2.23.0.187.g17f5b7556c-goog
Quoted 91 lines · Saravana Kannan
Add device-links to track functional dependencies between devices after they are created (but before they are probed) by looking at their common DT bindings like clocks, interconnects, etc.
Having functional dependencies automatically added before the devices are probed, provides the following benefits:
- Optimizes device probe order and avoids the useless work of attempting probes of devices that will not probe successfully (because their suppliers aren't present or haven't probed yet).
For example, in a commonly available mobile SoC, registering just one consumer device's driver at an initcall level earlier than the supplier device's driver causes 11 failed probe attempts before the consumer device probes successfully. This was with a kernel with all the drivers statically compiled in. This problem gets a lot worse if all the drivers are loaded as modules without direct symbol dependencies.
- Supplier devices like clock providers, interconnect providers, etc need to keep the resources they provide active and at a particular state(s) during boot up even if their current set of consumers don't request the resource to be active. This is because the rest of the consumers might not have probed yet and turning off the resource before all the consumers have probed could lead to a hang or undesired user experience.
Some frameworks (Eg: regulator) handle this today by turning off "unused" resources at
late_initcall_syncand hoping all the devices have probed by then. This is not a valid assumption for systems with loadable modules. Other frameworks (Eg: clock) just don't handle this due to the lack of a clear signal for when they can turn off resources. This leads to downstream hacks to handle cases like this that can easily be solved in the upstream kernel.By linking devices before they are probed, we give suppliers a clear count of the number of dependent consumers. Once all of the consumers are active, the suppliers can turn off the unused resources without making assumptions about the number of consumers.
By default we just add device-links to track "driver presence" (probe succeeded) of the supplier device. If any other functionality provided by device-links are needed, it is left to the consumer/supplier devices to change the link when they probe.
v1 -> v2:
- Drop patch to speed upof_find_device_by_node()
- Drop depends-on property and use existing bindingsv2 -> v3:
- Refactor the code to have driver core initiate the linking of devs
- Have driver core link consumers to supplier before it's probed
- Add support for drivers to edit the device links before probingv3 -> v4:
- Testededit_links()on system with cyclic dependency. Works.
- Added some checks to make sure device link isn't attempted from parent device node to child device node.
- Added way to pause/resumesync_statecallbacks acrossof_platform_populate().
- Recursively parse DT node to create device links from parent to suppliers of parent and all child nodes.v4 -> v5:
- Fixed copy-pasta bugs with linked list handling
- Walk up the phandle reference till I find an actual device (needed for regulators to work)
- Added support for linking devices from regulator DT bindings
- Tested the whole series again to make sure cyclic dependencies are broken withedit_links()and regulator links are created properly.v5 -> v6:
- Split, squashed and reordered some of the patches.
- Refactored the device linking code to follow the same code pattern for any property.v6 -> v7:
- No functional changes.
- Renamed i to index
- Added comment to clarify not having to check property name for every index
- Added "matched" variable to clarify code. No functional change.
- Added comments toinclude/linux/device.hforadd_links()v7 -> v8:
- Rebased on top of linux-next to handle device link changes in [1]v8 -> v9:
- Fixed kbuild test bot reported errors (docs and const)
Quoted 10 lines
v9->v10:
- Changes made based on reviews on LKML [2] and discussions at ELC [3]
- Dropped theedit_links()patch
- Dropped the patch that skips linking for default bus nodes
- 1/7: Changed frombus.add_links()tofwnode.ops.add_links()
- 1/7: Update device link doc
- 1/7: Lots of comments/fn doc updates
- 1/7: Renameddevice_link_check_waiting_consumers()todevice_link_add_missing_supplier_links()
- 2/7: Moved DT parsing/linking code fromof/platform.ctoof/property.c
Why? You'll notice that of/property.c doesn't know anything about platform_device (and struct device):
$ git grep platform_device -- drivers/of/property.c $
Everything related to platform_device goes in of/platform.c. Everything related to struct device only goes in of/device.c. I'd be okay with a new file for this too.
Rob
Quoted 107 lines · Rob Herring
Quoted 91 lines · Saravana Kannan
Add device-links to track functional dependencies between devices after they are created (but before they are probed) by looking at their common DT bindings like clocks, interconnects, etc.
Having functional dependencies automatically added before the devices are probed, provides the following benefits:
- Optimizes device probe order and avoids the useless work of attempting probes of devices that will not probe successfully (because their suppliers aren't present or haven't probed yet).
For example, in a commonly available mobile SoC, registering just one consumer device's driver at an initcall level earlier than the supplier device's driver causes 11 failed probe attempts before the consumer device probes successfully. This was with a kernel with all the drivers statically compiled in. This problem gets a lot worse if all the drivers are loaded as modules without direct symbol dependencies.
- Supplier devices like clock providers, interconnect providers, etc need to keep the resources they provide active and at a particular state(s) during boot up even if their current set of consumers don't request the resource to be active. This is because the rest of the consumers might not have probed yet and turning off the resource before all the consumers have probed could lead to a hang or undesired user experience.
Some frameworks (Eg: regulator) handle this today by turning off "unused" resources at
late_initcall_syncand hoping all the devices have probed by then. This is not a valid assumption for systems with loadable modules. Other frameworks (Eg: clock) just don't handle this due to the lack of a clear signal for when they can turn off resources. This leads to downstream hacks to handle cases like this that can easily be solved in the upstream kernel.By linking devices before they are probed, we give suppliers a clear count of the number of dependent consumers. Once all of the consumers are active, the suppliers can turn off the unused resources without making assumptions about the number of consumers.
By default we just add device-links to track "driver presence" (probe succeeded) of the supplier device. If any other functionality provided by device-links are needed, it is left to the consumer/supplier devices to change the link when they probe.
v1 -> v2:
- Drop patch to speed upof_find_device_by_node()
- Drop depends-on property and use existing bindingsv2 -> v3:
- Refactor the code to have driver core initiate the linking of devs
- Have driver core link consumers to supplier before it's probed
- Add support for drivers to edit the device links before probingv3 -> v4:
- Testededit_links()on system with cyclic dependency. Works.
- Added some checks to make sure device link isn't attempted from parent device node to child device node.
- Added way to pause/resumesync_statecallbacks acrossof_platform_populate().
- Recursively parse DT node to create device links from parent to suppliers of parent and all child nodes.v4 -> v5:
- Fixed copy-pasta bugs with linked list handling
- Walk up the phandle reference till I find an actual device (needed for regulators to work)
- Added support for linking devices from regulator DT bindings
- Tested the whole series again to make sure cyclic dependencies are broken withedit_links()and regulator links are created properly.v5 -> v6:
- Split, squashed and reordered some of the patches.
- Refactored the device linking code to follow the same code pattern for any property.v6 -> v7:
- No functional changes.
- Renamed i to index
- Added comment to clarify not having to check property name for every index
- Added "matched" variable to clarify code. No functional change.
- Added comments toinclude/linux/device.hforadd_links()v7 -> v8:
- Rebased on top of linux-next to handle device link changes in [1]v8 -> v9:
- Fixed kbuild test bot reported errors (docs and const)Quoted 10 lines
v9->v10:
- Changes made based on reviews on LKML [2] and discussions at ELC [3]
- Dropped theedit_links()patch
- Dropped the patch that skips linking for default bus nodes
- 1/7: Changed frombus.add_links()tofwnode.ops.add_links()
- 1/7: Update device link doc
- 1/7: Lots of comments/fn doc updates
- 1/7: Renameddevice_link_check_waiting_consumers()todevice_link_add_missing_supplier_links()
- 2/7: Moved DT parsing/linking code fromof/platform.ctoof/property.cWhy? You'll notice that
of/property.cdoesn't know anything aboutplatform_device(and struct device):
Quoted 6 lines
$ git grep platform_device -- drivers/of/property.c $Everything related to
platform_devicegoes inof/platform.c. Everything related to struct device only goes inof/device.c. I'd be okay with a new file for this too.
The only platform_device related code in what got moved to of/property.c is the call to of_find_device_by_node(). And that's because I forgot that function returns a platform_device --- it should really have been called of_find_plat_device_by_node() or something similar. Outside of that, of/property.c makes sense because that's where the fwnode ops are implemented.
As you mentioned in the other email, just searching platform_bus is not sufficient. So I'll have to figure something out for that. Once I do, I think the code will be fine in of/property.c as it shouldn't have any reference to platform_device.
Thanks for catching what I missed.
-Saravana