Make fw_devlink=on more forgiving
Subsystems (4)
v2 cover Make fw_devlink=on more forgiving
This patch series solves two general issues with fw_devlink=on
Patch 1/3 and 3/3 addresses the issue of firmware nodes that look like they'll have struct devices created for them, but will never actually have struct devices added for them. For example, DT nodes with a compatible property that don't have devices added for them.
Patch 2/2 address (for static kernels) the issue of optional suppliers that'll never have a driver registered for them. So, if the device could have probed with fw_devlink=permissive with a static kernel, this patch should allow those devices to probe with a fw_devlink=on. This doesn't solve it for the case where modules are enabled because there's no way to tell if a driver will never be registered or it's just about to be registered. I have some other ideas for that, but it'll have to come later thinking about it a bit.
Marek, Geert,
I don't expect v2 to do any better for your cases.
This series not making any difference for Marek is still a mystery to me. I guess one of the consumers doesn't take too well to its probe (and it's consumers' probe) being delayed till late_initcall(). I'll continue looking into it.
Marc,
This v2 should do better than v1 with gpiolib stub driver reverted. I forgot to take care of the case where more suppliers could link after I went and deleted some of the links. v2 handles that now.
Tudor,
You should still make the clock driver fix (because it's a bug), but I think this series will fix your issue too (even without the clock driver fix). Can you please give this a shot?
Martin,
If you tested this series, can you please give a Tested-by?
Thanks,
Saravana
v1 -> v2:
Patch 1: Added a flag to fwnodes that aren't devices.
Patch 3: New patch to ise the flag set in patch 1 to not create bad links.
Saravana Kannan (3):
driver core: fw_devlink: Detect supplier devices that will never be
added
driver core: fw_devlink: Handle missing drivers for optional suppliers
of: property: Don't add links to absent suppliers
drivers/base/base.h | 2 + drivers/base/core.c | 135 +++++++++++++++++++++++++++++++++++------ drivers/base/dd.c | 5 ++ drivers/of/property.c | 4 +- include/linux/fwnode.h | 2 + 5 files changed, 127 insertions(+), 21 deletions(-)
Signature · 1 line
2.30.0.365.g02bc693789-goog
PATCH v2 1/3 driver core: fw_devlink: Detect supplier devices that will never be added
During the initial parsing of firmware by fw_devlink, fw_devlink might infer that some supplier firmware nodes would get populated as devices. But the inference is not always correct. This patch tries to logically detect and fix such mistakes as boot progresses or more devices probe.
fw_devlink makes a fundamental assumption that once a device binds to a driver, it will populate (i.e: add as struct devices) all the child firmware nodes that could be populated as devices (if they aren't populated already).
So, whenever a device probes, we check all its child firmware nodes. If a child firmware node has a corresponding device populated, we don't modify the child node or its descendants. However, if a child firmware node has not been populated as a device, we delete all the fwnode links where the child node or its descendants are suppliers. This ensures that no other device is blocked on a firmware node that will never be populated as a device. We also mark such fwnodes as NOT_DEVICE, so that no new fwnode links are created with these nodes as suppliers.
--- drivers/base/core.c | 31 ++++++++++++++++++++++++++++--- include/linux/fwnode.h | 2 ++ 2 files changed, 30 insertions(+), 3 deletions(-)
drivers/base/core.c +28 -3
@@ -148,6 +148,21 @@ void fwnode_links_purge(struct fwnode_handle *fwnode)fwnode_links_purge_consumers (fwnode); } +static void fw_devlink_purge_absent_suppliers (struct fwnode_handle *fwnode) +{ +struct fwnode_handle *child; + +/* Don't purge consumer links of an added child */ +if (fwnode->dev) +return ; + + fwnode->flags |=FWNODE_FLAG_NOT_DEVICE ; +fwnode_links_purge_consumers (fwnode); + +fwnode_for_each_available_child_node (fwnode, child) +fw_devlink_purge_absent_suppliers (child); +} +#ifdef CONFIG_SRCU static DEFINE_MUTEX (device_links_lock);DEFINE_STATIC_SRCU (device_links_srcu);
@@ -1154,12 +1169,22 @@ void device_links_driver_bound(struct device *dev)LIST_HEAD (sync_list);/* -* If a device probes successfully, it's expected to have created all +* If a device binds successfully, it's expected to have created all * the device links it needs to or make new device links as it needs -* them. So, it no longer needs to wait on any suppliers. +* them. So, fw_devlink no longer needs to create device links to any +* of the device's suppliers. +* +* Also, if a child firmware node of this bound device is not added as +* a device by now, assume it is never going to be added and make sure +* other devices don't defer probe indefinitely by waiting for such a +* child device. */ -if (dev->fwnode && dev->fwnode->dev == dev) +if (dev->fwnode && dev->fwnode->dev == dev) { +struct fwnode_handle *child;fwnode_links_purge_suppliers (dev->fwnode); +fwnode_for_each_available_child_node (dev->fwnode, child) +fw_devlink_purge_absent_suppliers (child); + }device_remove_file (dev, &dev_attr_waiting_for_supplier);device_links_write_lock ();
include/linux/fwnode.h +2 -0
@@ -19,8 +19,10 @@ struct device;* fwnode link flags * * LINKS_ADDED: The fwnode has already be parsed to add fwnode links. +* NOT_DEVICE: The fwnode will never be populated as a struct device. */ #define FWNODE_FLAG_LINKS_ADDED BIT(0) +#define FWNODE_FLAG_NOT_DEVICE BIT(1)struct fwnode_handle {struct fwnode_handle *secondary;
Signature · 1 line
2.30.0.365.g02bc693789-goog
Rafael J. Wysocki
maintainerRe: [PATCH v2 1/3] driver core: fw_devlink: Detect supplier devices that will never be added
Quoted 20 lines · Saravana Kannan
During the initial parsing of firmware by
fw_devlink,fw_devlinkmight infer that some supplier firmware nodes would get populated as devices. But the inference is not always correct. This patch tries to logically detect and fix such mistakes as boot progresses or more devices probe.
fw_devlinkmakes a fundamental assumption that once a device binds to a driver, it will populate (i.e: add as struct devices) all the child firmware nodes that could be populated as devices (if they aren't populated already).So, whenever a device probes, we check all its child firmware nodes. If a child firmware node has a corresponding device populated, we don't modify the child node or its descendants. However, if a child firmware node has not been populated as a device, we delete all the fwnode links where the child node or its descendants are suppliers. This ensures that no other device is blocked on a firmware node that will never be populated as a device. We also mark such fwnodes as
NOT_DEVICE, so that no new fwnode links are created with these nodes as suppliers.
Quoted 2 lines
Fixes e590474768f1 ("driver core: Set fw_devlink=on by default")Signed-off-by Saravana Kannan <[email protected]>
Still ACKed.
Quoted 75 lines
--- drivers/base/core.c | 31 ++++++++++++++++++++++++++++--- include/linux/fwnode.h | 2 ++ 2 files changed, 30 insertions(+), 3 deletions(-)drivers/base/core.c +28
-3@@ -148,6 +148,21 @@ void fwnode_links_purge(struct fwnode_handle *fwnode)fwnode_links_purge_consumers (fwnode); } +static void fw_devlink_purge_absent_suppliers (struct fwnode_handle *fwnode) +{ +struct fwnode_handle *child; + +/* Don't purge consumer links of an added child */ +if (fwnode->dev) +return ; + + fwnode->flags |=FWNODE_FLAG_NOT_DEVICE ; +fwnode_links_purge_consumers (fwnode); + +fwnode_for_each_available_child_node (fwnode, child) +fw_devlink_purge_absent_suppliers (child); +} +#ifdef CONFIG_SRCU static DEFINE_MUTEX (device_links_lock);DEFINE_STATIC_SRCU (device_links_srcu);@@ -1154,12 +1169,22 @@ void device_links_driver_bound(struct device *dev)LIST_HEAD (sync_list);/* -* If a device probes successfully, it's expected to have created all +* If a device binds successfully, it's expected to have created all * the device links it needs to or make new device links as it needs -* them. So, it no longer needs to wait on any suppliers. +* them. So, fw_devlink no longer needs to create device links to any +* of the device's suppliers. +* +* Also, if a child firmware node of this bound device is not added as +* a device by now, assume it is never going to be added and make sure +* other devices don't defer probe indefinitely by waiting for such a +* child device. */ -if (dev->fwnode && dev->fwnode->dev == dev) +if (dev->fwnode && dev->fwnode->dev == dev) { +struct fwnode_handle *child;fwnode_links_purge_suppliers (dev->fwnode); +fwnode_for_each_available_child_node (dev->fwnode, child) +fw_devlink_purge_absent_suppliers (child); + }device_remove_file (dev, &dev_attr_waiting_for_supplier);device_links_write_lock ();include/linux/fwnode.h +2
-1@@ -19,8 +19,10 @@ struct device;* fwnode link flags * * LINKS_ADDED: The fwnode has already be parsed to add fwnode links. +* NOT_DEVICE: The fwnode will never be populated as a struct device. */ #define FWNODE_FLAG_LINKS_ADDED BIT(0) +#define FWNODE_FLAG_NOT_DEVICE BIT(1)struct fwnode_handle {struct fwnode_handle *secondary; --2.30.0.365.g02bc693789-goog
Re: [PATCH v2 1/3] driver core: fw_devlink: Detect supplier devices that will never be added
Quoted 22 lines · Rafael J. Wysocki
Quoted 20 lines · Saravana Kannan
During the initial parsing of firmware by
fw_devlink,fw_devlinkmight infer that some supplier firmware nodes would get populated as devices. But the inference is not always correct. This patch tries to logically detect and fix such mistakes as boot progresses or more devices probe.
fw_devlinkmakes a fundamental assumption that once a device binds to a driver, it will populate (i.e: add as struct devices) all the child firmware nodes that could be populated as devices (if they aren't populated already).So, whenever a device probes, we check all its child firmware nodes. If a child firmware node has a corresponding device populated, we don't modify the child node or its descendants. However, if a child firmware node has not been populated as a device, we delete all the fwnode links where the child node or its descendants are suppliers. This ensures that no other device is blocked on a firmware node that will never be populated as a device. We also mark such fwnodes as
NOT_DEVICE, so that no new fwnode links are created with these nodes as suppliers.
Quoted 4 lines
Quoted 2 lines
Fixes e590474768f1 ("driver core: Set fw_devlink=on by default")Signed-off-by Saravana Kannan <[email protected]>Still ACKed.
Thanks. I didn't want to add your Ack when I made changes since your Ack.
-Saravana
PATCH v2 2/3 driver core: fw_devlink: Handle missing drivers for optional suppliers
In reply to Saravana KannanAfter a deferred probe attempt has exhaused all the devices that can be bound, any device that remains unbound has one/both of these conditions true:
(1) It is waiting on its supplier to bind
(2) It does not have a matching driver
So, to make fw_devlink=on more forgiving of missing drivers for optional suppliers, after we've done a full deferred probe attempt, this patch deletes all device links created by fw_devlink where the supplier hasn't probed yet and the supplier itself is not waiting on any of its suppliers. This allows consumers to probe during another deferred probe attempt if they were waiting on optional suppliers.
When modules are enabled, we can't differentiate between a driver that'll never be registered vs a driver that'll be registered soon by loading a module. So, this patch doesn't do anything for the case where modules are enabled.
--- drivers/base/base.h | 2 + drivers/base/core.c | 104 ++++++++++++++++++++++++++++++++++++-------- drivers/base/dd.c | 5 +++ 3 files changed, 94 insertions(+), 17 deletions(-)
drivers/base/base.h +2 -0
@@ -186,6 +186,8 @@ extern void device_links_no_driver(struct device *dev);extern bool device_links_busy (struct device *dev);extern void device_links_unbind_consumers (struct device *dev); +bool fw_devlink_deferred_probe_retry (void ); +/* device pm support */ void device_pm_move_to_tail (struct device *dev);
drivers/base/core.c +87 -17
150 lines not on this page · raw message
drivers/base/dd.c +5 -0
@@ -317,6 +317,11 @@ static int deferred_probe_initcall(void)driver_deferred_probe_trigger ();/* Sort as many dependencies as possible before exiting initcalls */ flush_work (&deferred_probe_work); + +if (fw_devlink_deferred_probe_retry ()) { +driver_deferred_probe_trigger (); +flush_work (&deferred_probe_work); + } initcalls_done = true;/*
Signature · 1 line
2.30.0.365.g02bc693789-goog
Rafael J. Wysocki
maintainerRe: [PATCH v2 2/3] driver core: fw_devlink: Handle missing drivers for optional suppliers
Quoted 82 lines · Saravana Kannan
After a deferred probe attempt has exhaused all the devices that can be bound, any device that remains unbound has one/both of these conditions true:
(1) It is waiting on its supplier to bind
(2) It does not have a matching driverSo, to make fw_devlink=on more forgiving of missing drivers for optional suppliers, after we've done a full deferred probe attempt, this patch deletes all device links created by
fw_devlinkwhere the supplier hasn't probed yet and the supplier itself is not waiting on any of its suppliers. This allows consumers to probe during another deferred probe attempt if they were waiting on optional suppliers.When modules are enabled, we can't differentiate between a driver that'll never be registered vs a driver that'll be registered soon by loading a module. So, this patch doesn't do anything for the case where modules are enabled.
Fixes e590474768f1 ("driver core: Set fw_devlink=on by default")Signed-off-by Saravana Kannan <[email protected]>--- drivers/base/base.h | 2 + drivers/base/core.c | 104 ++++++++++++++++++++++++++++++++++++-------- drivers/base/dd.c | 5 +++ 3 files changed, 94 insertions(+), 17 deletions(-)drivers/base/base.h +2
-0@@ -186,6 +186,8 @@ extern void device_links_no_driver(struct device *dev);extern bool device_links_busy (struct device *dev);extern void device_links_unbind_consumers (struct device *dev); +bool fw_devlink_deferred_probe_retry (void ); +/* device pm support */ void device_pm_move_to_tail (struct device *dev);drivers/base/core.c +19
-0@@ -50,6 +50,7 @@ static LIST_HEAD(deferred_sync);static unsigned int defer_sync_state_count =1 ;static DEFINE_MUTEX (fwnode_link_lock);static bool fw_devlink_is_permissive (void ); +static bool fw_devlink_def_probe_retry;/** * fwnode_link_add - Create a link between two fwnode_handles. @@ -881,6 +882,13 @@ static void device_link_put_kref(struct device_link *link)WARN (1 ,"Unable to drop a managed device link reference\n" ); } +static void device_link_drop_managed (struct device_link *link) +{ + link->flags &= ~DL_FLAG_MANAGED ; +WRITE_ONCE (link->status,DL_STATE_NONE ); +kref_put (&link->kref, __device_link_del); +} +/** * device_link_del - Delete a stateless link between two devices. * @link: Device link to delete. @@ -943,6 +951,29 @@ static void device_links_missing_supplier(struct device *dev) } } +/** +* device_links_probe_blocked_by - Return first supplier blocking probe +* @dev: Consumer device. +* +* Checks if the probe of @dev is blocked by a supplier without a driver. If +* yes, return that supplier dev. Otherwise, return NULL. +*/ +static struct device *device_links_probe_blocked_by (struct device *dev) +{ +struct device_link *link; +
drivers/base/core.c static void device_links_missing_supplier(struct device *dev) · line 974
Quoted 10 lines
drivers/base/core.c +10
-0+list_for_each_entry (link, &dev->links.suppliers, c_node) { +if (!(link->flags &DL_FLAG_MANAGED ) || + link->flags &DL_FLAG_SYNC_STATE_ONLY ) +continue ; + +if (link->status !=DL_STATE_AVAILABLE ) +return link->supplier; + } + +return NULL ;
This is slightly confusing, because you don't actually use the returned device pointer, but simply check it against NULL.
AFAICS this function can return bool and I'd call it device_links_probe_blocked().
Quoted 46 lines
drivers/base/core.c +20
-9+} +/** * device_links_check_suppliers - Check presence of supplier drivers. * @dev: Consumer device. @@ -961,7 +992,7 @@ static void device_links_missing_supplier(struct device *dev)*/ int device_links_check_suppliers (struct device *dev) { -struct device_link *link; +struct device_link *link, *tmp;int ret =0 ;/* @@ -982,19 +1013,47 @@ int device_links_check_suppliers(struct device *dev)device_links_write_lock (); -list_for_each_entry (link, &dev->links.suppliers, c_node) { +list_for_each_entry_safe (link, tmp, &dev->links.suppliers, c_node) {if (!(link->flags &DL_FLAG_MANAGED ))continue ; -if (link->status !=DL_STATE_AVAILABLE && - !(link->flags &DL_FLAG_SYNC_STATE_ONLY )) { -device_links_missing_supplier (dev); -dev_dbg (dev,"probe deferral - supplier %s not ready\n" , -dev_name (link->supplier)); - ret = -EPROBE_DEFER ; -break ; + +if (link->status ==DL_STATE_AVAILABLE || + link->flags &DL_FLAG_SYNC_STATE_ONLY ) { +WRITE_ONCE (link->status,DL_STATE_CONSUMER_PROBE ); +continue ; + } + +/* +* After a deferred probe attempt has exhaused all the devices +* that can be bound, any device that remains unbound has +* one/both of these conditions true: +* +* (1) It is waiting on its supplier to bind +* (2) It does not have a matching driver +* +* If this device is waiting on a supplier to bind to a driver,
drivers/base/core.c int device_links_check_suppliers(struct device *dev) · line 1045
Quoted 10 lines
drivers/base/core.c +10
-0+* we make sure condition (1) above is not true for the +* supplier. In which case, condition (2) has to be true for +* the supplier. That is, the supplier doesn't have a matching +* driver. +* +* When we find such a supplier, we delete the device link if +* it was created by fw_devlink. This it to allow the consumer +* to probe in case the supplier is an optional. +*/ + if (fw_devlink_def_probe_retry &&
I would put a IS_ENABLED(CONFIG_MODULES) check here to let the compiler optimize out the code depending on it and make it clear that this is a NOP if there are modules.
Quoted 30 lines
drivers/base/core.c +10
-8+ link->flags & DL_FLAG_INFERRED && + !device_links_probe_blocked_by(link->supplier)) { +device_link_drop_managed (link); +continue ; } -WRITE_ONCE (link->status,DL_STATE_CONSUMER_PROBE ); + +device_links_missing_supplier (dev); +dev_dbg (dev,"probe deferral - supplier %s not ready\n" , +dev_name (link->supplier)); + ret = -EPROBE_DEFER ; +break ; } dev->links.status =DL_DEV_PROBING ;@@ -1132,13 +1191,6 @@ static void __device_links_supplier_defer_sync(struct device *sup)list_add_tail (&sup->links.defer_sync, &deferred_sync); } -static void device_link_drop_managed (struct device_link *link) -{ - link->flags &= ~DL_FLAG_MANAGED ; -WRITE_ONCE (link->status,DL_STATE_NONE ); -kref_put (&link->kref, __device_link_del); -} -static ssize_t waiting_for_supplier_show (struct device *dev,struct device_attribute *attr,char *buf)
drivers/base/core.c static int fw_devlink_relax_cycle(struct device *con, void *sup) · line 1652
Quoted 4 lines
drivers/base/core.c +1
-0@@ -1597,6 +1649,24 @@ static int fw_devlink_relax_cycle(struct device *con, void *sup)return ret; } +/** fw_devlink_deferred_probe_retry - Set up fw_devlink for probe retries
Kerneldoc format mistake.
drivers/base/core.c static int fw_devlink_relax_cycle(struct device *con, void *sup) · line 1664
Quoted 12 lines
drivers/base/core.c +12
-0+* +* This function requests fw_devlink to set itself up for a deferred probe +* retry. This allows fw_devlink to ignore device links it created to +* suppliers that'll never probe. This is necessary in case some of the +* suppliers are optional and their consumers can probe without them. +* +* Returns true if deferred probe retry is likely to make any difference. +*/ +bool fw_devlink_deferred_probe_retry (void ) +{ +if (IS_ENABLED (CONFIG_MODULES )) +return false;
To make the above more visible, I'd fold this function into the caller.
Quoted 15 lines
drivers/base/core.c +5
-0+ + fw_devlink_def_probe_retry = true; +return fw_devlink_get_flags () && !fw_devlink_is_permissive (); +} +/** * fw_devlink_create_devlink - Create a device link from a consumer to fwnode * @con - Consumer device for the device link drivers/base/dd.c +0
-0@@ -317,6 +317,11 @@ static int deferred_probe_initcall(void)driver_deferred_probe_trigger ();/* Sort as many dependencies as possible before exiting initcalls */
drivers/base/dd.c static int deferred_probe_initcall(void)
Quoted 10 lines
drivers/base/dd.c +5
-1flush_work (&deferred_probe_work); + +if (fw_devlink_deferred_probe_retry ()) { +driver_deferred_probe_trigger (); +flush_work (&deferred_probe_work); + } initcalls_done = true;/* --
Overall, the "let's do nothing if modules are not enabled" approach is a bit disappointing, because what if somebody builds all of the drivers needed for boot in and enables modules anyway, for example to allow USB drivers to be probed dynamically?
They surely can be forgiven for expecting to get the right ordering then, like in the "no modules" case ...
Re: [PATCH v2 2/3] driver core: fw_devlink: Handle missing drivers for optional suppliers
Quoted 98 lines · Rafael J. Wysocki
Quoted 82 lines · Saravana Kannan
After a deferred probe attempt has exhaused all the devices that can be bound, any device that remains unbound has one/both of these conditions true:
(1) It is waiting on its supplier to bind
(2) It does not have a matching driverSo, to make fw_devlink=on more forgiving of missing drivers for optional suppliers, after we've done a full deferred probe attempt, this patch deletes all device links created by
fw_devlinkwhere the supplier hasn't probed yet and the supplier itself is not waiting on any of its suppliers. This allows consumers to probe during another deferred probe attempt if they were waiting on optional suppliers.When modules are enabled, we can't differentiate between a driver that'll never be registered vs a driver that'll be registered soon by loading a module. So, this patch doesn't do anything for the case where modules are enabled.
Fixes e590474768f1 ("driver core: Set fw_devlink=on by default")Signed-off-by Saravana Kannan <[email protected]>--- drivers/base/base.h | 2 + drivers/base/core.c | 104 ++++++++++++++++++++++++++++++++++++-------- drivers/base/dd.c | 5 +++ 3 files changed, 94 insertions(+), 17 deletions(-)drivers/base/base.h +2
-0@@ -186,6 +186,8 @@ extern void device_links_no_driver(struct device *dev);extern bool device_links_busy (struct device *dev);extern void device_links_unbind_consumers (struct device *dev); +bool fw_devlink_deferred_probe_retry (void ); +/* device pm support */ void device_pm_move_to_tail (struct device *dev);drivers/base/core.c +19
-0@@ -50,6 +50,7 @@ static LIST_HEAD(deferred_sync);static unsigned int defer_sync_state_count =1 ;static DEFINE_MUTEX (fwnode_link_lock);static bool fw_devlink_is_permissive (void ); +static bool fw_devlink_def_probe_retry;/** * fwnode_link_add - Create a link between two fwnode_handles. @@ -881,6 +882,13 @@ static void device_link_put_kref(struct device_link *link)WARN (1 ,"Unable to drop a managed device link reference\n" ); } +static void device_link_drop_managed (struct device_link *link) +{ + link->flags &= ~DL_FLAG_MANAGED ; +WRITE_ONCE (link->status,DL_STATE_NONE ); +kref_put (&link->kref, __device_link_del); +} +/** * device_link_del - Delete a stateless link between two devices. * @link: Device link to delete. @@ -943,6 +951,29 @@ static void device_links_missing_supplier(struct device *dev) } } +/** +* device_links_probe_blocked_by - Return first supplier blocking probe +* @dev: Consumer device. +* +* Checks if the probe of @dev is blocked by a supplier without a driver. If +* yes, return that supplier dev. Otherwise, return NULL. +*/ +static struct device *device_links_probe_blocked_by (struct device *dev) +{ +struct device_link *link; +drivers/base/core.c static void device_links_missing_supplier(struct device *dev) · line 974
Quoted 10 lines
drivers/base/core.c +10
-0+list_for_each_entry (link, &dev->links.suppliers, c_node) { +if (!(link->flags &DL_FLAG_MANAGED ) || + link->flags &DL_FLAG_SYNC_STATE_ONLY ) +continue ; + +if (link->status !=DL_STATE_AVAILABLE ) +return link->supplier; + } + +return NULL ;This is slightly confusing, because you don't actually use the returned device pointer, but simply check it against NULL.
Quoted 2 lines
AFAICS this function can return bool and I'd call it
device_links_probe_blocked().
Yeah, I was writing it this way because I had other future uses for this. But yeah, I'll just make it a bool and change it later when I need to.
Quoted 53 lines
Quoted 53 lines
drivers/base/core.c +26
-9+} +/** * device_links_check_suppliers - Check presence of supplier drivers. * @dev: Consumer device. @@ -961,7 +992,7 @@ static void device_links_missing_supplier(struct device *dev)*/ int device_links_check_suppliers (struct device *dev) { -struct device_link *link; +struct device_link *link, *tmp;int ret =0 ;/* @@ -982,19 +1013,47 @@ int device_links_check_suppliers(struct device *dev)device_links_write_lock (); -list_for_each_entry (link, &dev->links.suppliers, c_node) { +list_for_each_entry_safe (link, tmp, &dev->links.suppliers, c_node) {if (!(link->flags &DL_FLAG_MANAGED ))continue ; -if (link->status !=DL_STATE_AVAILABLE && - !(link->flags &DL_FLAG_SYNC_STATE_ONLY )) { -device_links_missing_supplier (dev); -dev_dbg (dev,"probe deferral - supplier %s not ready\n" , -dev_name (link->supplier)); - ret = -EPROBE_DEFER ; -break ; + +if (link->status ==DL_STATE_AVAILABLE || + link->flags &DL_FLAG_SYNC_STATE_ONLY ) { +WRITE_ONCE (link->status,DL_STATE_CONSUMER_PROBE ); +continue ; + } + +/* +* After a deferred probe attempt has exhaused all the devices +* that can be bound, any device that remains unbound has +* one/both of these conditions true: +* +* (1) It is waiting on its supplier to bind +* (2) It does not have a matching driver +* +* If this device is waiting on a supplier to bind to a driver, +* we make sure condition (1) above is not true for the +* supplier. In which case, condition (2) has to be true for +* the supplier. That is, the supplier doesn't have a matching +* driver. +* +* When we find such a supplier, we delete the device link if
Quoted 8 lines
drivers/base/core.c int device_links_check_suppliers(struct device *dev) · line 1045
Quoted 4 lines
drivers/base/core.c +4
-0+* it was created by fw_devlink. This it to allow the consumer +* to probe in case the supplier is an optional. +*/ + if (fw_devlink_def_probe_retry &&I would put a
IS_ENABLED(CONFIG_MODULES)check here to let the compiler optimize out the code depending on it and make it clear that this is a NOP if there are modules.
Will do.
Quoted 34 lines
Quoted 34 lines
drivers/base/core.c +10
-8+ link->flags & DL_FLAG_INFERRED && + !device_links_probe_blocked_by(link->supplier)) { +device_link_drop_managed (link); +continue ; } -WRITE_ONCE (link->status,DL_STATE_CONSUMER_PROBE ); + +device_links_missing_supplier (dev); +dev_dbg (dev,"probe deferral - supplier %s not ready\n" , +dev_name (link->supplier)); + ret = -EPROBE_DEFER ; +break ; } dev->links.status =DL_DEV_PROBING ;@@ -1132,13 +1191,6 @@ static void __device_links_supplier_defer_sync(struct device *sup)list_add_tail (&sup->links.defer_sync, &deferred_sync); } -static void device_link_drop_managed (struct device_link *link) -{ - link->flags &= ~DL_FLAG_MANAGED ; -WRITE_ONCE (link->status,DL_STATE_NONE ); -kref_put (&link->kref, __device_link_del); -} -static ssize_t waiting_for_supplier_show (struct device *dev,struct device_attribute *attr,char *buf)@@ -1597,6 +1649,24 @@ static int fw_devlink_relax_cycle(struct device *con, void *sup)return ret; }
Quoted 3 lines
drivers/base/core.c static int fw_devlink_relax_cycle(struct device *con, void *sup) · line 1652
Quoted 1 line
drivers/base/core.c +1
-0+/** fw_devlink_deferred_probe_retry - Set up fw_devlink for probe retries Kerneldoc format mistake.
Ack
Quoted 15 lines
drivers/base/core.c static int fw_devlink_relax_cycle(struct device *con, void *sup) · line 1664
Quoted 13 lines
drivers/base/core.c +12
-0+* +* This function requests fw_devlink to set itself up for a deferred probe +* retry. This allows fw_devlink to ignore device links it created to +* suppliers that'll never probe. This is necessary in case some of the +* suppliers are optional and their consumers can probe without them. +* +* Returns true if deferred probe retry is likely to make any difference. +*/ +bool fw_devlink_deferred_probe_retry (void ) +{ +if (IS_ENABLED (CONFIG_MODULES )) +return false;To make the above more visible, I'd fold this function into the caller.
I had written it this way because I'm thinking of adding a timeout heuristic for MODULES in here. I can move it to the caller if you feel strongly about it.
Quoted 24 lines
Quoted 24 lines
drivers/base/core.c +5
-0+ + fw_devlink_def_probe_retry = true; +return fw_devlink_get_flags () && !fw_devlink_is_permissive (); +} +/** * fw_devlink_create_devlink - Create a device link from a consumer to fwnode * @con - Consumer device for the device link drivers/base/dd.c +5
-0@@ -317,6 +317,11 @@ static int deferred_probe_initcall(void)driver_deferred_probe_trigger ();/* Sort as many dependencies as possible before exiting initcalls */ flush_work (&deferred_probe_work); + +if (fw_devlink_deferred_probe_retry ()) { +driver_deferred_probe_trigger (); +flush_work (&deferred_probe_work); + } initcalls_done = true;
Quoted 7 lines
drivers/base/dd.c static int deferred_probe_initcall(void)
Quoted 2 lines
drivers/base/dd.c +0
-1/* -- Overall, the "let's do nothing if modules are not enabled" approach is a bit disappointing, because what if somebody builds all of the drivers needed for boot in and enables modules anyway, for example to allow USB drivers to be probed dynamically?
Yeah, I'm disappointed too :( But I'm trying to get it to work for !MODULES so that we can enable fw_devlink=on by default at least for !MODULES to make sure drivers don't introduce more issues going forward. And then I plan to continue working on making it work correctly for MODULES case too.
Getting fw_devlink=on to work perfectly for MODULES and !MODULES is not a problem at all. But it needs fixing a bunch of drivers (mostly simple fixes like setting the right flag, handling deferred probes correctly, etc), but I'm hitting a catch-22 here. I can't find the drivers without setting fw_devlink=on by default. But if I did that, it's going to break a bunch of boards.
What's your thought on leaving fw_devlink=on by default on 5.12 and fixing drivers as issues are reported? If that's a no, do you have any other ideas on how to deal with this catch-22?
Thanks,
Saravana
Rafael J. Wysocki
maintainerRe: [PATCH v2 2/3] driver core: fw_devlink: Handle missing drivers for optional suppliers
Quoted 5 lines · Saravana Kannan
Quoted 3 lines · Rafael J. Wysocki
Quoted 1 line · Saravana Kannan
[cut]
Quoted 16 lines
Quoted 15 lines
drivers/base/core.c static int fw_devlink_relax_cycle(struct device *con, void *sup) · line 1664
Quoted 13 lines
+ *
+ * This function requestsfw_devlinkto set itself up for a deferred probe
+ * retry. This allowsfw_devlinkto ignore device links it created to
+ * suppliers that'll never probe. This is necessary in case some of the
+ * suppliers are optional and their consumers can probe without them.
+ *
+ * Returns true if deferred probe retry is likely to make any difference.
+ */drivers/base/core.c +4
-0+bool fw_devlink_deferred_probe_retry (void ) +{ +if (IS_ENABLED (CONFIG_MODULES )) +return false;To make the above more visible, I'd fold this function into the caller.
Quoted 3 lines
I had written it this way because I'm thinking of adding a timeout heuristic for MODULES in here. I can move it to the caller if you feel strongly about it.
Not really strongly, but then moving it back when you need doesn't sound particularly troublesome to me. :-)
Quoted 45 lines
Quoted 24 lines
Quoted 24 lines
drivers/base/core.c +5
-0+ + fw_devlink_def_probe_retry = true; +return fw_devlink_get_flags () && !fw_devlink_is_permissive (); +} +/** * fw_devlink_create_devlink - Create a device link from a consumer to fwnode * @con - Consumer device for the device link drivers/base/dd.c +5
-0@@ -317,6 +317,11 @@ static int deferred_probe_initcall(void)driver_deferred_probe_trigger ();/* Sort as many dependencies as possible before exiting initcalls */ flush_work (&deferred_probe_work); + +if (fw_devlink_deferred_probe_retry ()) { +driver_deferred_probe_trigger (); +flush_work (&deferred_probe_work); + } initcalls_done = true;Quoted 7 lines
drivers/base/dd.c static int deferred_probe_initcall(void)
Quoted 2 lines
drivers/base/dd.c +0
-1/* -- Overall, the "let's do nothing if modules are not enabled" approach is a bit disappointing, because what if somebody builds all of the drivers needed for boot in and enables modules anyway, for example to allow USB drivers to be probed dynamically?
Yeah, I'm disappointed too :( But I'm trying to get it to work for !MODULES so that we can enable fw_devlink=on by default at least for !MODULES to make sure drivers don't introduce more issues going forward. And then I plan to continue working on making it work correctly for MODULES case too.
Getting fw_devlink=on to work perfectly for MODULES and !MODULES is not a problem at all. But it needs fixing a bunch of drivers (mostly simple fixes like setting the right flag, handling deferred probes correctly, etc), but I'm hitting a catch-22 here. I can't find the drivers without setting fw_devlink=on by default. But if I did that, it's going to break a bunch of boards.
Quoted 2 lines
What's your thought on leaving fw_devlink=on by default on 5.12 and fixing drivers as issues are reported?
If there are any issues known today that need to be addressed, I'd fix them first and then try to enable fw_devlink=on maybe just for !MODULES to start with.
Quoted 1 line
If that's a no, do you have any other ideas on how to deal with this catch-22?
Try to enable, fix issues as they show up in linux-next. If there are still outstanding issues before the next release, back off and try in the next cycle. Repeat.
This doesn't sound particularly attractive, but I don't have any better idea, sorry.
Re: [PATCH v2 2/3] driver core: fw_devlink: Handle missing drivers for optional suppliers
Quoted 26 lines · Rafael J. Wysocki
Quoted 5 lines · Saravana Kannan
Quoted 3 lines · Rafael J. Wysocki
Quoted 1 line · Saravana Kannan
[cut]
Quoted 16 lines
Quoted 15 lines
drivers/base/core.c static int fw_devlink_relax_cycle(struct device *con, void *sup) · line 1664
Quoted 13 lines
+ *
+ * This function requestsfw_devlinkto set itself up for a deferred probe
+ * retry. This allowsfw_devlinkto ignore device links it created to
+ * suppliers that'll never probe. This is necessary in case some of the
+ * suppliers are optional and their consumers can probe without them.
+ *
+ * Returns true if deferred probe retry is likely to make any difference.
+ */drivers/base/core.c +4
-0+bool fw_devlink_deferred_probe_retry (void ) +{ +if (IS_ENABLED (CONFIG_MODULES )) +return false;To make the above more visible, I'd fold this function into the caller.
Quoted 6 lines
Quoted 3 lines
I had written it this way because I'm thinking of adding a timeout heuristic for MODULES in here. I can move it to the caller if you feel strongly about it.
Not really strongly, but then moving it back when you need doesn't sound particularly troublesome to me. :-)
Ok, will move it. I'm also rewriting this patch. So we'll see where this lands.
Quoted 46 lines
Quoted 46 lines
Quoted 25 lines
Quoted 25 lines
drivers/base/core.c +5
-0+ + fw_devlink_def_probe_retry = true; +return fw_devlink_get_flags () && !fw_devlink_is_permissive (); +} +/** * fw_devlink_create_devlink - Create a device link from a consumer to fwnode * @con - Consumer device for the device link drivers/base/dd.c +5
-0@@ -317,6 +317,11 @@ static int deferred_probe_initcall(void)driver_deferred_probe_trigger ();/* Sort as many dependencies as possible before exiting initcalls */ flush_work (&deferred_probe_work); + +if (fw_devlink_deferred_probe_retry ()) { +driver_deferred_probe_trigger (); +flush_work (&deferred_probe_work); + } initcalls_done = true;Quoted 7 lines
drivers/base/dd.c static int deferred_probe_initcall(void)
Quoted 2 lines
drivers/base/dd.c +0
-1/* -- Overall, the "let's do nothing if modules are not enabled" approach is a bit disappointing, because what if somebody builds all of the drivers needed for boot in and enables modules anyway, for example to allow USB drivers to be probed dynamically?
Yeah, I'm disappointed too :( But I'm trying to get it to work for !MODULES so that we can enable fw_devlink=on by default at least for !MODULES to make sure drivers don't introduce more issues going forward. And then I plan to continue working on making it work correctly for MODULES case too.
Getting fw_devlink=on to work perfectly for MODULES and !MODULES is not a problem at all. But it needs fixing a bunch of drivers (mostly simple fixes like setting the right flag, handling deferred probes correctly, etc), but I'm hitting a catch-22 here. I can't find the drivers without setting fw_devlink=on by default. But if I did that, it's going to break a bunch of boards.
Quoted 6 lines
Quoted 2 lines
What's your thought on leaving fw_devlink=on by default on 5.12 and fixing drivers as issues are reported?
If there are any issues known today that need to be addressed, I'd fix them first and then try to enable fw_devlink=on maybe just for !MODULES to start with.
Yeah, that's what I'm thinking of for now.
Quoted 5 lines
Quoted 1 line
If that's a no, do you have any other ideas on how to deal with this catch-22?
Try to enable, fix issues as they show up in linux-next. If there are still outstanding issues before the next release, back off and try in the next cycle. Repeat.
If it's just dealing with outstanding issues that are reported, I'm hoping I can do that. The biggest headache right now is dealing with devices that have drivers that directly parse the fwnode AND still have a struct device. So the struct device remains unbound even if the driver has initialized the device.
Quoted 3 lines
This doesn't sound particularly attractive, but I don't have any better idea, sorry.
:'( Yeah, another approach I'm thinking of is to have a separate "strict mode" for fw_devlink=on or above. Where it'll try it's best till kernel late init and then fallback to permissive. But it's becoming a headache to deal with some corner cases.
-Saravana
PATCH v2 3/3 of: property: Don't add links to absent suppliers
In reply to Saravana KannanIf driver core marks a firmware node as not a device, don't add fwnode links where it's a supplier.
--- drivers/of/property.c | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-)
drivers/of/property.c +3 -1
@@ -1103,7 +1103,9 @@ static int of_link_to_phandle(struct device_node *con_np,* created for them. */ sup_dev =get_dev_from_fwnode (&sup_np->fwnode); -if (!sup_dev &&of_node_check_flag (sup_np,OF_POPULATED )) { +if (!sup_dev && + (of_node_check_flag (sup_np,OF_POPULATED ) || + sup_np->fwnode.flags &FWNODE_FLAG_NOT_DEVICE )) {pr_debug ("Not linking %pOFP to %pOFP - No struct device\n" , con_np, sup_np);of_node_put (sup_np);
Signature · 1 line
2.30.0.365.g02bc693789-goog
Re: [PATCH v2 3/3] of: property: Don't add links to absent suppliers
Quoted 26 lines · Saravana Kannan
If driver core marks a firmware node as not a device, don't add fwnode links where it's a supplier.
Fixes e590474768f1 ("driver core: Set fw_devlink=on by default")Signed-off-by Saravana Kannan <[email protected]>--- drivers/of/property.c | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-)drivers/of/property.c +3
-2@@ -1103,7 +1103,9 @@ static int of_link_to_phandle(struct device_node *con_np,* created for them. */ sup_dev =get_dev_from_fwnode (&sup_np->fwnode); -if (!sup_dev &&of_node_check_flag (sup_np,OF_POPULATED )) { +if (!sup_dev && + (of_node_check_flag (sup_np,OF_POPULATED ) || + sup_np->fwnode.flags &FWNODE_FLAG_NOT_DEVICE )) {pr_debug ("Not linking %pOFP to %pOFP - No struct device\n" , con_np, sup_np);of_node_put (sup_np); --
Quoted 2 lines
2.30.0.365.g02bc693789-goog
Rob, Can I get an Ack or reviewed-by for this? I want to land this patch and another one on driver-core.
Thanks,
Saravana
Hi, Saravana,
Quoted 33 lines · Saravana Kannan
EXTERNAL EMAIL: Do not click links or open attachments unless you know the content is safe
This patch series solves two general issues with fw_devlink=on
Patch 1/3 and 3/3 addresses the issue of firmware nodes that look like they'll have struct devices created for them, but will never actually have struct devices added for them. For example, DT nodes with a compatible property that don't have devices added for them.
Patch 2/2 address (for static kernels) the issue of optional suppliers that'll never have a driver registered for them. So, if the device could have probed with fw_devlink=permissive with a static kernel, this patch should allow those devices to probe with a fw_devlink=on. This doesn't solve it for the case where modules are enabled because there's no way to tell if a driver will never be registered or it's just about to be registered. I have some other ideas for that, but it'll have to come later thinking about it a bit.
Marek, Geert,
I don't expect v2 to do any better for your cases.
This series not making any difference for Marek is still a mystery to me. I guess one of the consumers doesn't take too well to its probe (and it's consumers' probe) being delayed till
late_initcall(). I'll continue looking into it.Marc,
This v2 should do better than v1 with gpiolib stub driver reverted. I forgot to take care of the case where more suppliers could link after I went and deleted some of the links. v2 handles that now.
Quoted 6 lines
Tudor,
You should still make the clock driver fix (because it's a bug), but I think this series will fix your issue too (even without the clock driver fix). Can you please give this a shot?
Did the following tests (using sama5_defconfig and at91-sama5d2_xplained.dts):
1/ modular kernel with your v2 on top of next-20210202, and without the clock driver fix: the problem persists.
2/ static kernel with your v2 on top of next-20210202, and without the clock driver fix: the problem persists. Comparing to the previous test, I see that the links to pmc are dropped. I can see the following only with early printk enabled:
platform fc008000.serial: Dropping the link to f0014000.pmc
But later on, the serial still gets deferred waiting for the dma controller this time:
platform f8020000.serial: probe deferral - supplier f0010000.dma-controller not ready I'll check what happens in the dma-controller.
3/ modular kernel with your v2 and the clock driver fix on top of next-20210202:
I can boot the board and I have access to the console. I still have some probe deferrals that I need to check:
root@sama5d2-xplained-sd:~# dmesg | grep -i defer [ 4.335625] platform b0000000.sdio-host: probe deferral - wait for supplier pmic@5b [ 4.474559] platform fc030000.adc: probe deferral - wait for supplier pmic@5b [ 4.884315] calling deferred_probe_initcall+0x0/0xd8 @ 1 [ 4.889206] platform fc030000.adc: probe deferral - wait for supplier pmic@5b [ 5.139447] initcall deferred_probe_initcall+0x0/0xd8 returned 0 after 245132 usecs root@sama5d2-xplained-sd:~# dmesg | grep -i linked [ 4.916342] platform fc030000.adc: Linked as a consumer to 0-005b [ 4.921298] platform b0000000.sdio-host: Linked as a consumer to 0-005b [ 4.926817] i2c 0-005b: Linked as a sync state only consumer to fc038000.pinctrl [ 4.990246] platform act8945a-charger: Linked as a consumer to fc038000.pinctrl [ 5.078488] at24 1-0054: Linked as a consumer to regulator.0 [ 5.111533] at91-sama5d2_adc fc030000.adc: Linked as a consumer to regulator.5 [ 5.118969] sdhci-at91 b0000000.sdio-host: Linked as a consumer to regulator.3 root@sama5d2-xplained-sd:~# dmesg | grep -i drop [ 5.014026] act8945a 0-005b: Dropping the link to fc038000.pinctrl
4/ static kernel with your v2 and the clock driver fix on top of next-20210202:
I can boot the board and I have access to the console. The probe deferrals are the same as in test 3/.
Cheers,
ta
Quoted 48 lines · On Tue, Feb 2, 2021 at 10:52 AM <[email protected]> wrote:
Hi, Saravana,
Quoted 33 lines · Saravana Kannan
EXTERNAL EMAIL: Do not click links or open attachments unless you know the content is safe
This patch series solves two general issues with fw_devlink=on
Patch 1/3 and 3/3 addresses the issue of firmware nodes that look like they'll have struct devices created for them, but will never actually have struct devices added for them. For example, DT nodes with a compatible property that don't have devices added for them.
Patch 2/2 address (for static kernels) the issue of optional suppliers that'll never have a driver registered for them. So, if the device could have probed with fw_devlink=permissive with a static kernel, this patch should allow those devices to probe with a fw_devlink=on. This doesn't solve it for the case where modules are enabled because there's no way to tell if a driver will never be registered or it's just about to be registered. I have some other ideas for that, but it'll have to come later thinking about it a bit.
Marek, Geert,
I don't expect v2 to do any better for your cases.
This series not making any difference for Marek is still a mystery to me. I guess one of the consumers doesn't take too well to its probe (and it's consumers' probe) being delayed till
late_initcall(). I'll continue looking into it.Marc,
This v2 should do better than v1 with gpiolib stub driver reverted. I forgot to take care of the case where more suppliers could link after I went and deleted some of the links. v2 handles that now.
Quoted 6 lines
Tudor,
You should still make the clock driver fix (because it's a bug), but I think this series will fix your issue too (even without the clock driver fix). Can you please give this a shot?
Did the following tests (using
sama5_defconfigandat91-sama5d2_xplained.dts):
1/ modular kernel with your v2 on top of next-20210202, and without the clock driver fix: the problem persists.
Quoted 9 lines
2/ static kernel with your v2 on top of next-20210202, and without the clock driver fix: the problem persists. Comparing to the previous test, I see that the links to pmc are dropped. I can see the following only with early printk enabled:
platform fc008000.serial: Dropping the link to f0014000.pmc
But later on, the serial still gets deferred waiting for the dma controller this time:
platform f8020000.serial: probe deferral - supplier f0010000.dma-controller not ready I'll check what happens in the dma-controller.
Not sure if it's the case here, but some serial drivers use DMA only when available and decide that on open() rather than probe. How is devlinks going to deal with that?
Rob
Quoted 60 lines · Rob Herring
Quoted 48 lines · On Tue, Feb 2, 2021 at 10:52 AM <[email protected]> wrote:
Hi, Saravana,
Quoted 33 lines · Saravana Kannan
EXTERNAL EMAIL: Do not click links or open attachments unless you know the content is safe
This patch series solves two general issues with fw_devlink=on
Patch 1/3 and 3/3 addresses the issue of firmware nodes that look like they'll have struct devices created for them, but will never actually have struct devices added for them. For example, DT nodes with a compatible property that don't have devices added for them.
Patch 2/2 address (for static kernels) the issue of optional suppliers that'll never have a driver registered for them. So, if the device could have probed with fw_devlink=permissive with a static kernel, this patch should allow those devices to probe with a fw_devlink=on. This doesn't solve it for the case where modules are enabled because there's no way to tell if a driver will never be registered or it's just about to be registered. I have some other ideas for that, but it'll have to come later thinking about it a bit.
Marek, Geert,
I don't expect v2 to do any better for your cases.
This series not making any difference for Marek is still a mystery to me. I guess one of the consumers doesn't take too well to its probe (and it's consumers' probe) being delayed till
late_initcall(). I'll continue looking into it.Marc,
This v2 should do better than v1 with gpiolib stub driver reverted. I forgot to take care of the case where more suppliers could link after I went and deleted some of the links. v2 handles that now.
Quoted 6 lines
Tudor,
You should still make the clock driver fix (because it's a bug), but I think this series will fix your issue too (even without the clock driver fix). Can you please give this a shot?
Did the following tests (using
sama5_defconfigandat91-sama5d2_xplained.dts):
1/ modular kernel with your v2 on top of next-20210202, and without the clock driver fix: the problem persists.Quoted 9 lines
2/ static kernel with your v2 on top of next-20210202, and without the clock driver fix: the problem persists. Comparing to the previous test, I see that the links to pmc are dropped. I can see the following only with early printk enabled:
platform fc008000.serial: Dropping the link to f0014000.pmc
But later on, the serial still gets deferred waiting for the dma controller this time:
platform f8020000.serial: probe deferral - supplier f0010000.dma-controller not ready I'll check what happens in the dma-controller.
Quoted 3 lines
Not sure if it's the case here, but some serial drivers use DMA only when available and decide that on
open()rather than probe. How is devlinks going to deal with that?
That's kinda what I'm trying to work out here :) but in a more generic fashion.
-Saravana
Hi Saravana,
Thus wrote Saravana Kannan ([email protected]):
Quoted 3 lines
Martin,
If you tested this series, can you please give a Tested-by?
I tested this v2 series on top of next-20210202 (without the fsl,avic patch).
If modules are enabled, the kernel doesn't boot on my imx25 board. This is expected, I guess.
With modules disabled, the kernel boots but probe fails for some (non-mainline) drivers in my tree. All of those drivers have a gpio in their device-tree node, such as
my_driver {
gpio_test1 = <&gpio1 0 0>;
...
};
with gpio1 from arch/arm/boot/dts/imx25.dtsi.
The probe function calls
of_get_named_gpio(np, "gpio_test1", 0);
to get the gpio. This fails with -EINVAL.
Best regards,
Martin
Quoted 9 lines · Martin Kaiser
Hi Saravana,
Thus wrote Saravana Kannan ([email protected]):
Quoted 3 lines
Martin,
If you tested this series, can you please give a Tested-by?
Quoted 8 lines
I tested this v2 series on top of next-20210202 (without the fsl,avic patch).
If modules are enabled, the kernel doesn't boot on my imx25 board. This is expected, I guess.
With modules disabled, the kernel boots but probe fails for some (non-mainline) drivers in my tree.
Thanks Martin!
Quoted 8 lines
All of those drivers have a gpio in
their device-tree node, such asmy_driver { gpio_test1 = <&gpio1 0 0>; ... };
Quoted 7 lines
with gpio1 from
arch/arm/boot/dts/imx25.dtsi.The probe function calls
of_get_named_gpio(np, "gpio_test1", 0);to get the gpio. This fails with
-EINVAL.
And you didn't see this issue with the fsl,avic patch?
The property you are using is not a standard GPIO binding (-gpios, gpio, gpios) and I'm not surprised it's not working. The gpio1 is probably getting probe deferred and ends up running after "my_driver".
-Saravana
Quoted 16 lines · Saravana Kannan
Quoted 15 lines · Martin Kaiser
Thus wrote Saravana Kannan ([email protected]):
All of those drivers have a gpio in
their device-tree node, such asmy_driver { gpio_test1 = <&gpio1 0 0>; ... };with gpio1 from
arch/arm/boot/dts/imx25.dtsi.The probe function calls
of_get_named_gpio(np, "gpio_test1", 0);
Quoted 7 lines
Quoted 1 line
to get the gpio. This fails with
-EINVAL.And you didn't see this issue with the fsl,avic patch?
The property you are using is not a standard GPIO binding (-gpios, gpio, gpios) and I'm not surprised it's not working. The gpio1 is probably getting probe deferred and ends up running after "
my_driver".
So my_driver doesn't support deferred probe, as of_get_named_gpio() returns -EINVAL instead of -EPROBE_DEFER?
Converting my_driver from of_get_named_gpio() to the gpiod_*() API should at least make the driver support probe deferral, after which I expect it to start working again on reprobe?
Gr{oetje,eeting}s,
Geert
Signature · 5 lines
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- [email protected] In personal conversations with technical people, I call myself a hacker. But when I'm talking to journalists I just say "programmer" or something like that. -- Linus Torvalds
Quoted 26 lines · Geert Uytterhoeven
Quoted 16 lines · Saravana Kannan
Quoted 15 lines · Martin Kaiser
Thus wrote Saravana Kannan ([email protected]):
All of those drivers have a gpio in
their device-tree node, such asmy_driver { gpio_test1 = <&gpio1 0 0>; ... };with gpio1 from
arch/arm/boot/dts/imx25.dtsi.The probe function calls
of_get_named_gpio(np, "gpio_test1", 0);Quoted 7 lines
Quoted 1 line
to get the gpio. This fails with
-EINVAL.And you didn't see this issue with the fsl,avic patch?
The property you are using is not a standard GPIO binding (-gpios, gpio, gpios) and I'm not surprised it's not working. The gpio1 is probably getting probe deferred and ends up running after "
my_driver".
Quoted 5 lines
So
my_driverdoesn't support deferred probe, asof_get_named_gpio()returns-EINVALinstead of -EPROBE_DEFER?
Convertingmy_driverfromof_get_named_gpio()to the gpiod_*() API should at least make the driver support probe deferral, after which I expect it to start working again on reprobe?
The way I understood the API/example, you can't just change the code and have it work. The DT itself isn't using standard bindings. And we can't make kernel changes that assume the DT has been changed to match the code. So, the best we could do is have of_get_named_gpio() return -EPROBE_DEFER if it doesn't find the GPIO -- assuming that doesn't break other users. Or have this specific driver remap the -EINVAL to -EPROBE_DEFER.
-Saravana
Hi Saravana,
Quoted 26 lines · Saravana Kannan
Quoted 25 lines · Geert Uytterhoeven
Quoted 23 lines · Saravana Kannan
Quoted 9 lines · Martin Kaiser
Thus wrote Saravana Kannan ([email protected]):
All of those drivers have a gpio in
their device-tree node, such asmy_driver { gpio_test1 = <&gpio1 0 0>; ... };Quoted 7 lines
with gpio1 from
arch/arm/boot/dts/imx25.dtsi.The probe function calls
of_get_named_gpio(np, "gpio_test1", 0);to get the gpio. This fails with
-EINVAL.And you didn't see this issue with the fsl,avic patch?
The property you are using is not a standard GPIO binding (-gpios, gpio, gpios) and I'm not surprised it's not working. The gpio1 is probably getting probe deferred and ends up running after "
my_driver".
Quoted 8 lines
Quoted 5 lines
So
my_driverdoesn't support deferred probe, asof_get_named_gpio()returns-EINVALinstead of -EPROBE_DEFER?
Convertingmy_driverfromof_get_named_gpio()to the gpiod_*() API should at least make the driver support probe deferral, after which I expect it to start working again on reprobe?The way I understood the API/example, you can't just change the code and have it work. The DT itself isn't using standard bindings. And we
Oh, right.
Quoted 5 lines
can't make kernel changes that assume the DT has been changed to match the code. So, the best we could do is have
of_get_named_gpio()return -EPROBE_DEFER if it doesn't find the GPIO -- assuming that doesn't break other users. Or have this specific driver remap the-EINVALto -EPROBE_DEFER.
The latter would hide real errors, too, and would cause futile reprobes.
Gr{oetje,eeting}s,
Geert
Signature · 5 lines
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- [email protected] In personal conversations with technical people, I call myself a hacker. But when I'm talking to journalists I just say "programmer" or something like that. -- Linus Torvalds
Thus wrote Geert Uytterhoeven ([email protected]):
Quoted 5 lines
Quoted 3 lines
The property you are using is not a standard GPIO binding (-gpios, gpio, gpios) and I'm not surprised it's not working. The gpio1 is probably getting probe deferred and ends up running after "
my_driver".So
my_driverdoesn't support deferred probe,
I know that the gpio definition in the device-tree is non-standard (and should have been done differently).
Apart from this, the driver uses module_platform_driver_probe. My understanding is that this prevents probe deferral.
Does this mean that from now on, a driver which requests a gpio must not use module_platform_driver_probe?
Thanks,
Martin
Thus wrote Saravana Kannan ([email protected]):
Quoted 15 lines
Quoted 2 lines
With modules disabled, the kernel boots but probe fails for some (non-mainline) drivers in my tree.
Thanks Martin!
Quoted 9 lines
All of those drivers have a gpio in
their device-tree node, such asmy_driver { gpio_test1 = <&gpio1 0 0>; ... };with gpio1 from
arch/arm/boot/dts/imx25.dtsi.
Quoted 7 lines
Quoted 5 lines
The probe function calls
of_get_named_gpio(np, "gpio_test1", 0);to get the gpio. This fails with
-EINVAL.And you didn't see this issue with the fsl,avic patch?
No. With the fsl,avic patch in place, all drivers are probed correctly.
Quoted 2 lines
The property you are using is not a standard GPIO binding (-gpios, gpio, gpios) and I'm not surprised it's not working.
I know that I should be using the gpiod API as suggested by Geert.
BTW is this definition ok? Could its driver be converted to using the gpiod api?
rtc: rtc {
compatible = "moxa,moxart-rtc";
gpio-rtc-sclk = <&gpio 5 0>;
...
Quoted 2 lines
The gpio1 is probably getting probe deferred and ends up running after "
my_driver".
I added a debug print in the probe function. It turned out that the driver for gpio1 is probed for the first time after my_driver.
I removed the interrupt-controller property for gpio2 for testing. gpio2 was then probed much earlier.
Best regards,
Martin
Quoted 33 lines · Martin Kaiser
Thus wrote Saravana Kannan ([email protected]):
Quoted 15 lines
Quoted 2 lines
With modules disabled, the kernel boots but probe fails for some (non-mainline) drivers in my tree.
Thanks Martin!
Quoted 9 lines
All of those drivers have a gpio in
their device-tree node, such asmy_driver { gpio_test1 = <&gpio1 0 0>; ... };with gpio1 from
arch/arm/boot/dts/imx25.dtsi.Quoted 7 lines
Quoted 5 lines
The probe function calls
of_get_named_gpio(np, "gpio_test1", 0);to get the gpio. This fails with
-EINVAL.And you didn't see this issue with the fsl,avic patch?
No. With the fsl,avic patch in place, all drivers are probed correctly.
Quoted 2 lines
The property you are using is not a standard GPIO binding (-gpios, gpio, gpios) and I'm not surprised it's not working.
I know that I should be using the gpiod API as suggested by Geert.
Quoted 7 lines
BTW is this definition ok? Could its driver be converted to using the gpiod api?
rtc: rtc { compatible = "moxa,moxart-rtc"; gpio-rtc-sclk = <&gpio 5 0>;...
The correct non-deprecated binding AFAIK is something-gpios. Not gpio-something. And then you can use different APIs to get the GPIO (I forget what it's called).
-Saravana
Quoted 10 lines
Quoted 4 lines
The gpio1 is probably getting probe deferred and ends up running after "
my_driver".I added a debug print in the probe function. It turned out that the driver for gpio1 is probed for the first time after
my_driver.I removed the interrupt-controller property for gpio2 for testing. gpio2 was then probed much earlier.