Ulf reported an issue[1] with fw_devlink. This series tries to fix that issue.
Subsystems (4)
cover Ulf reported an issue[1] with fw_devlink. This series tries to fix that issue.
Ulf, mind testing this?
Thanks,
Saravana
[1] - https://lore.kernel.org/lkml/CAPDyKFo9Bxremkb1dDrr4OcXSpE0keVze94Cm=zrkOVxHHxBmQ@mail.gmail.com/
Saravana Kannan (2):
driver core: Add support for FWNODE_FLAG_NEVER_PROBES
of: platform: Mark bus devices nodes with FWNODE_FLAG_NEVER_PROBES
drivers/base/core.c | 8 ++++++++ drivers/of/platform.c | 16 ++++++++++++++++ include/linux/fwnode.h | 8 +++++--- 3 files changed, 29 insertions(+), 3 deletions(-)
Signature · 1 line
2.33.0.259.gc128427fd7-goog
PATCH 1/2 driver core: Add support for FWNODE_FLAG_NEVER_PROBES
Add a fwnode flag to mark a device as one that will never be probed even though it's added to a bus.
--- drivers/base/core.c | 8 ++++++++ include/linux/fwnode.h | 8 +++++--- 2 files changed, 13 insertions(+), 3 deletions(-)
drivers/base/core.c +8 -0
@@ -1719,6 +1719,14 @@ static int fw_devlink_create_devlink(struct device *con,struct device *sup_dev;int ret =0 ; +/* +* If the consumer or supplier is a device that'll never be probed, +* don't create devices link for it. +*/ +if (con->fwnode->flags &FWNODE_FLAG_NEVER_PROBES || + sup_handle->flags &FWNODE_FLAG_NEVER_PROBES ) +return -EINVAL ; + sup_dev =get_dev_from_fwnode (sup_handle);if (sup_dev) {/*
include/linux/fwnode.h +5 -3
@@ -19,13 +19,15 @@ 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. -* INITIALIZED: The hardware corresponding to fwnode has been initialized. +* LINKS_ADDED: The fwnode has already be parsed to add fwnode links. +* NOT_DEVICE: The fwnode will never be populated as a struct device. +* INITIALIZED: The hardware corresponding to fwnode has been initialized. +* NEVER_PROBES: The device that corresponds to this fwnode will never probe. */ #define FWNODE_FLAG_LINKS_ADDED BIT(0)#define FWNODE_FLAG_NOT_DEVICE BIT(1)#define FWNODE_FLAG_INITIALIZED BIT(2) +#define FWNODE_FLAG_NEVER_PROBES BIT(3)struct fwnode_handle {struct fwnode_handle *secondary;
Signature · 1 line
2.33.0.259.gc128427fd7-goog
PATCH 2/2 of: platform: Mark bus devices nodes with FWNODE_FLAG_NEVER_PROBES
In reply to Saravana KannanWe don't want fw_devlink creating device links for bus devices as they'll never probe. So mark those device node with this flag.
--- drivers/of/platform.c | 16 ++++++++++++++++ 1 file changed, 16 insertions(+)
drivers/of/platform.c +16 -0
@@ -392,6 +392,22 @@ static int of_platform_bus_create(struct device_node *bus,if (!dev || !of_match_node (matches, bus))return 0 ; +/* +* If the bus node has only one compatible string value and it has +* matched as a bus node, it's never going to get probed by a device +* driver. So flag it as such so that fw_devlink knows not to create +* device links with this device. +* +* This doesn't catch all devices that'll never probe, but this is good +* enough for now. +* +* This doesn't really work for PPC because of how it uses +* of_platform_bus_probe() to add normal devices. So ignore PPC cases. +*/ +if (!IS_ENABLED (CONFIG_PPC ) && +of_property_count_strings (bus,"compatible" ) ==1 ) + bus->fwnode.flags |=FWNODE_FLAG_NOT_DEVICE ; +for_each_child_of_node (bus, child) {pr_debug (" create child: %pOF\n" , child); rc =of_platform_bus_create (child, matches, lookup, &dev->dev, strict);
Signature · 1 line
2.33.0.259.gc128427fd7-goog
Re: [PATCH v1 2/2] of: platform: Mark bus devices nodes with FWNODE_FLAG_NEVER_PROBES
Quoted 22 lines · Saravana Kannan
We don't want
fw_devlinkcreating device links for bus devices as they'll never probe. So mark those device node with this flag.Signed-off-by Saravana Kannan <[email protected]>--- drivers/of/platform.c | 16 ++++++++++++++++ 1 file changed, 16 insertions(+)drivers/of/platform.c +5
-0@@ -392,6 +392,22 @@ static int of_platform_bus_create(struct device_node *bus,if (!dev || !of_match_node (matches, bus))return 0 ; +/* +* If the bus node has only one compatible string value and it has +* matched as a bus node, it's never going to get probed by a device +* driver. So flag it as such so that fw_devlink knows not to create +* device links with this device.
drivers/of/platform.c static int of_platform_bus_create(struct device_node *bus, · line 409
Quoted 10 lines
drivers/of/platform.c +10
-0+* +* This doesn't catch all devices that'll never probe, but this is good +* enough for now. +* +* This doesn't really work for PPC because of how it uses +* of_platform_bus_probe() to add normal devices. So ignore PPC cases. +*/ +if (!IS_ENABLED (CONFIG_PPC ) && +of_property_count_strings (bus,"compatible" ) ==1 ) + bus->fwnode.flags |=FWNODE_FLAG_NOT_DEVICE ;
This looks fragile relying on 1 compatible string, and the DT flags in this code have been fragile too. I'm pretty sure we have cases of simple-bus or simple-mfd that also have another compatible.
Couldn't we solve this with a simple driver? Make 'simple-pm-bus' driver work for other cases? BTW, this patch doesn't even work for simple-pm-bus. A driver for simple-bus may cause issues if there's a more specific driver to bind to as we don't handle that. It's simply whichever matches first.
Rob
Re: [PATCH v1 2/2] of: platform: Mark bus devices nodes with FWNODE_FLAG_NEVER_PROBES
Quoted 39 lines · Rob Herring
Quoted 22 lines · Saravana Kannan
We don't want
fw_devlinkcreating device links for bus devices as they'll never probe. So mark those device node with this flag.Signed-off-by Saravana Kannan <[email protected]>--- drivers/of/platform.c | 16 ++++++++++++++++ 1 file changed, 16 insertions(+)drivers/of/platform.c +5
-0@@ -392,6 +392,22 @@ static int of_platform_bus_create(struct device_node *bus,if (!dev || !of_match_node (matches, bus))return 0 ; +/* +* If the bus node has only one compatible string value and it has +* matched as a bus node, it's never going to get probed by a device +* driver. So flag it as such so that fw_devlink knows not to create +* device links with this device. drivers/of/platform.c static int of_platform_bus_create(struct device_node *bus, · line 409
Quoted 10 lines
drivers/of/platform.c +10
-0+* +* This doesn't catch all devices that'll never probe, but this is good +* enough for now. +* +* This doesn't really work for PPC because of how it uses +* of_platform_bus_probe() to add normal devices. So ignore PPC cases. +*/ +if (!IS_ENABLED (CONFIG_PPC ) && +of_property_count_strings (bus,"compatible" ) ==1 ) + bus->fwnode.flags |=FWNODE_FLAG_NOT_DEVICE ;This looks fragile relying on 1 compatible string, and the DT flags in this code have been fragile too. I'm pretty sure we have cases of simple-bus or simple-mfd that also have another compatible.
Quoted 1 line
Couldn't we solve this with a simple driver?
Oh, I didn't think you'd like that. I'd lean towards that option too if we can address some of the other concerns below.
Quoted 5 lines
Make 'simple-pm-bus'
driver work for other cases?BTW, this patch doesn't even work for
simple-pm-bus.
How do you mean? Because simple-pm-bus already has a driver and doesn't set "matches" param when it calls of_platform_populate() and this flag won't be set. So at least for simple-pm-bus I don't see any issue.
I was trying to reuse of_default_bus_match_table without explicitly referring to it, but if it's confusing I can add a separate list of compatible strings and use those here instead of using "matches".
Quoted 3 lines
A driver for simple-bus may cause issues if there's a more specific driver to bind to as we don't handle that. It's simply whichever matches first.
Right, this is my worry. Especially for devices like this (there are plenty of cases like this) which have a driver that probes them but also lists simple-bus
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/arch/arm/boot/dts/arm-realview-pb11mp.dts?id=73f3af7b4611d77bdaea303fb639333eb28e37d7#n299
So as long as there's a compatible string that's not one of the "transparent" busses, this driver shouldn't match. So, I don't think I can get away from checking the compatible strings.
How about I check here to make sure all the "compatible" strings are from an approved transparent bus list, and if it's true, I use driver_override to force match it to a transparent bus driver? Would you be okay with that?
-Saravana
Re: [PATCH v1 2/2] of: platform: Mark bus devices nodes with FWNODE_FLAG_NEVER_PROBES
Quoted 49 lines · Saravana Kannan
Quoted 39 lines · Rob Herring
Quoted 22 lines · Saravana Kannan
We don't want
fw_devlinkcreating device links for bus devices as they'll never probe. So mark those device node with this flag.Signed-off-by Saravana Kannan <[email protected]>--- drivers/of/platform.c | 16 ++++++++++++++++ 1 file changed, 16 insertions(+)drivers/of/platform.c +5
-0@@ -392,6 +392,22 @@ static int of_platform_bus_create(struct device_node *bus,if (!dev || !of_match_node (matches, bus))return 0 ; +/* +* If the bus node has only one compatible string value and it has +* matched as a bus node, it's never going to get probed by a device +* driver. So flag it as such so that fw_devlink knows not to create +* device links with this device. drivers/of/platform.c static int of_platform_bus_create(struct device_node *bus, · line 409
Quoted 10 lines
drivers/of/platform.c +10
-0+* +* This doesn't catch all devices that'll never probe, but this is good +* enough for now. +* +* This doesn't really work for PPC because of how it uses +* of_platform_bus_probe() to add normal devices. So ignore PPC cases. +*/ +if (!IS_ENABLED (CONFIG_PPC ) && +of_property_count_strings (bus,"compatible" ) ==1 ) + bus->fwnode.flags |=FWNODE_FLAG_NOT_DEVICE ;This looks fragile relying on 1 compatible string, and the DT flags in this code have been fragile too. I'm pretty sure we have cases of simple-bus or simple-mfd that also have another compatible.
Quoted 1 line
Couldn't we solve this with a simple driver?
Oh, I didn't think you'd like that. I'd lean towards that option too if we can address some of the other concerns below.
Quoted 2 lines
Make 'simple-pm-bus'
driver work for other cases?
Quoted 7 lines
Quoted 2 lines
BTW, this patch doesn't even work for
simple-pm-bus.How do you mean? Because simple-pm-bus already has a driver and doesn't set "matches" param when it calls
of_platform_populate()and this flag won't be set. So at least for simple-pm-bus I don't see any issue.
You're right.
Quoted 3 lines
I was trying to reuse
of_default_bus_match_tablewithout explicitly referring to it, but if it's confusing I can add a separate list of compatible strings and use those here instead of using "matches".
What happens with a non-default table? I'm not sure we can assume the same behavior.
Quoted 8 lines
Quoted 3 lines
A driver for simple-bus may cause issues if there's a more specific driver to bind to as we don't handle that. It's simply whichever matches first.
Right, this is my worry. Especially for devices like this (there are plenty of cases like this) which have a driver that probes them but also lists simple-bus
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/arch/arm/boot/dts/arm-realview-pb11mp.dts?id=73f3af7b4611d77bdaea303fb639333eb28e37d7#n299
Uhh, that one is certainly a leakage of wanting an soc_device in the hierarchy, not any real bus structure reflecting the h/w. I'm not a fan of the soc_device stuff and its optional nature. Everything is an SoC, so it should always be there? Or your device hierarchy should change when you decide to add a soc_device?
Quoted 8 lines
So as long as there's a compatible string that's not one of the "transparent" busses, this driver shouldn't match. So, I don't think I can get away from checking the compatible strings.
How about I check here to make sure all the "compatible" strings are from an approved transparent bus list, and if it's true, I use
driver_overrideto force match it to a transparent bus driver? Would you be okay with that?
Can't we do that within a driver? We check this and fail probe if there's a more specific compatible. Then another driver can match and probe.
Rob
Re: [PATCH v1 2/2] of: platform: Mark bus devices nodes with FWNODE_FLAG_NEVER_PROBES
Quoted 87 lines · Rob Herring
Quoted 49 lines · Saravana Kannan
Quoted 39 lines · Rob Herring
Quoted 22 lines · Saravana Kannan
We don't want
fw_devlinkcreating device links for bus devices as they'll never probe. So mark those device node with this flag.Signed-off-by Saravana Kannan <[email protected]>--- drivers/of/platform.c | 16 ++++++++++++++++ 1 file changed, 16 insertions(+)drivers/of/platform.c +5
-0@@ -392,6 +392,22 @@ static int of_platform_bus_create(struct device_node *bus,if (!dev || !of_match_node (matches, bus))return 0 ; +/* +* If the bus node has only one compatible string value and it has +* matched as a bus node, it's never going to get probed by a device +* driver. So flag it as such so that fw_devlink knows not to create +* device links with this device. drivers/of/platform.c static int of_platform_bus_create(struct device_node *bus, · line 409
Quoted 10 lines
drivers/of/platform.c +10
-0+* +* This doesn't catch all devices that'll never probe, but this is good +* enough for now. +* +* This doesn't really work for PPC because of how it uses +* of_platform_bus_probe() to add normal devices. So ignore PPC cases. +*/ +if (!IS_ENABLED (CONFIG_PPC ) && +of_property_count_strings (bus,"compatible" ) ==1 ) + bus->fwnode.flags |=FWNODE_FLAG_NOT_DEVICE ;This looks fragile relying on 1 compatible string, and the DT flags in this code have been fragile too. I'm pretty sure we have cases of simple-bus or simple-mfd that also have another compatible.
Quoted 1 line
Couldn't we solve this with a simple driver?
Oh, I didn't think you'd like that. I'd lean towards that option too if we can address some of the other concerns below.
Quoted 2 lines
Make 'simple-pm-bus'
driver work for other cases?Quoted 7 lines
Quoted 2 lines
BTW, this patch doesn't even work for
simple-pm-bus.How do you mean? Because simple-pm-bus already has a driver and doesn't set "matches" param when it calls
of_platform_populate()and this flag won't be set. So at least for simple-pm-bus I don't see any issue.You're right.
Quoted 3 lines
I was trying to reuse
of_default_bus_match_tablewithout explicitly referring to it, but if it's confusing I can add a separate list of compatible strings and use those here instead of using "matches".What happens with a non-default table? I'm not sure we can assume the same behavior.
Quoted 8 lines
Quoted 3 lines
A driver for simple-bus may cause issues if there's a more specific driver to bind to as we don't handle that. It's simply whichever matches first.
Right, this is my worry. Especially for devices like this (there are plenty of cases like this) which have a driver that probes them but also lists simple-bus
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/arch/arm/boot/dts/arm-realview-pb11mp.dts?id=73f3af7b4611d77bdaea303fb639333eb28e37d7#n299Uhh, that one is certainly a leakage of wanting an
soc_devicein the hierarchy, not any real bus structure reflecting the h/w. I'm not a fan of thesoc_devicestuff and its optional nature. Everything is an SoC, so it should always be there? Or your device hierarchy should change when you decide to add asoc_device?Quoted 4 lines
So as long as there's a compatible string that's not one of the "transparent" busses, this driver shouldn't match. So, I don't think I can get away from checking the compatible strings.
Quoted 8 lines
Quoted 4 lines
How about I check here to make sure all the "compatible" strings are from an approved transparent bus list, and if it's true, I use
driver_overrideto force match it to a transparent bus driver? Would you be okay with that?Can't we do that within a driver? We check this and fail probe if there's a more specific compatible. Then another driver can match and probe.
I was thinking that initially, but if we fail a probe, the driver core will permanently give up (won't search further) or might end up retrying with the same driver and never get to the other driver. I'll send out a v2 with what I described above. It's not too bad and it will also allow us to handle the PPC cases (we'll just need to keep adding the simple-bus equivalent entries to a table).
-Saravana
Re: [PATCH v1 2/2] of: platform: Mark bus devices nodes with FWNODE_FLAG_NEVER_PROBES
Quoted 98 lines · Saravana Kannan
Quoted 87 lines · Rob Herring
Quoted 49 lines · Saravana Kannan
Quoted 39 lines · Rob Herring
Quoted 22 lines · Saravana Kannan
We don't want
fw_devlinkcreating device links for bus devices as they'll never probe. So mark those device node with this flag.Signed-off-by Saravana Kannan <[email protected]>--- drivers/of/platform.c | 16 ++++++++++++++++ 1 file changed, 16 insertions(+)drivers/of/platform.c +5
-0@@ -392,6 +392,22 @@ static int of_platform_bus_create(struct device_node *bus,if (!dev || !of_match_node (matches, bus))return 0 ; +/* +* If the bus node has only one compatible string value and it has +* matched as a bus node, it's never going to get probed by a device +* driver. So flag it as such so that fw_devlink knows not to create +* device links with this device. drivers/of/platform.c static int of_platform_bus_create(struct device_node *bus, · line 409
Quoted 10 lines
drivers/of/platform.c +10
-0+* +* This doesn't catch all devices that'll never probe, but this is good +* enough for now. +* +* This doesn't really work for PPC because of how it uses +* of_platform_bus_probe() to add normal devices. So ignore PPC cases. +*/ +if (!IS_ENABLED (CONFIG_PPC ) && +of_property_count_strings (bus,"compatible" ) ==1 ) + bus->fwnode.flags |=FWNODE_FLAG_NOT_DEVICE ;This looks fragile relying on 1 compatible string, and the DT flags in this code have been fragile too. I'm pretty sure we have cases of simple-bus or simple-mfd that also have another compatible.
Quoted 1 line
Couldn't we solve this with a simple driver?
Oh, I didn't think you'd like that. I'd lean towards that option too if we can address some of the other concerns below.
Quoted 2 lines
Make 'simple-pm-bus'
driver work for other cases?Quoted 7 lines
Quoted 2 lines
BTW, this patch doesn't even work for
simple-pm-bus.How do you mean? Because simple-pm-bus already has a driver and doesn't set "matches" param when it calls
of_platform_populate()and this flag won't be set. So at least for simple-pm-bus I don't see any issue.You're right.
Quoted 3 lines
I was trying to reuse
of_default_bus_match_tablewithout explicitly referring to it, but if it's confusing I can add a separate list of compatible strings and use those here instead of using "matches".What happens with a non-default table? I'm not sure we can assume the same behavior.
Quoted 8 lines
Quoted 3 lines
A driver for simple-bus may cause issues if there's a more specific driver to bind to as we don't handle that. It's simply whichever matches first.
Right, this is my worry. Especially for devices like this (there are plenty of cases like this) which have a driver that probes them but also lists simple-bus
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/arch/arm/boot/dts/arm-realview-pb11mp.dts?id=73f3af7b4611d77bdaea303fb639333eb28e37d7#n299Uhh, that one is certainly a leakage of wanting an
soc_devicein the hierarchy, not any real bus structure reflecting the h/w. I'm not a fan of thesoc_devicestuff and its optional nature. Everything is an SoC, so it should always be there? Or your device hierarchy should change when you decide to add asoc_device?Quoted 4 lines
So as long as there's a compatible string that's not one of the "transparent" busses, this driver shouldn't match. So, I don't think I can get away from checking the compatible strings.
Quoted 8 lines
Quoted 4 lines
How about I check here to make sure all the "compatible" strings are from an approved transparent bus list, and if it's true, I use
driver_overrideto force match it to a transparent bus driver? Would you be okay with that?Can't we do that within a driver? We check this and fail probe if there's a more specific compatible. Then another driver can match and probe.
Quoted 6 lines
I was thinking that initially, but if we fail a probe, the driver core will permanently give up (won't search further) or might end up retrying with the same driver and never get to the other driver. I'll send out a v2 with what I described above. It's not too bad and it will also allow us to handle the PPC cases (we'll just need to keep adding the simple-bus equivalent entries to a table).
I wasn't sure, but I traced the calls and it looks like based on __driver_attach() that if a driver fails probe another one matching should get to probe:
/*
* Ignore errors returned by ->probe so that the next driver can try
* its luck.
*/
The PPC case is about descending nodes without a compatible string.
Rob
Re: [PATCH v1 2/2] of: platform: Mark bus devices nodes with FWNODE_FLAG_NEVER_PROBES
Quoted 107 lines · Rob Herring
Quoted 98 lines · Saravana Kannan
Quoted 87 lines · Rob Herring
Quoted 49 lines · Saravana Kannan
Quoted 39 lines · Rob Herring
Quoted 22 lines · Saravana Kannan
We don't want
fw_devlinkcreating device links for bus devices as they'll never probe. So mark those device node with this flag.Signed-off-by Saravana Kannan <[email protected]>--- drivers/of/platform.c | 16 ++++++++++++++++ 1 file changed, 16 insertions(+)drivers/of/platform.c +5
-0@@ -392,6 +392,22 @@ static int of_platform_bus_create(struct device_node *bus,if (!dev || !of_match_node (matches, bus))return 0 ; +/* +* If the bus node has only one compatible string value and it has +* matched as a bus node, it's never going to get probed by a device +* driver. So flag it as such so that fw_devlink knows not to create +* device links with this device. drivers/of/platform.c static int of_platform_bus_create(struct device_node *bus, · line 409
Quoted 10 lines
drivers/of/platform.c +10
-0+* +* This doesn't catch all devices that'll never probe, but this is good +* enough for now. +* +* This doesn't really work for PPC because of how it uses +* of_platform_bus_probe() to add normal devices. So ignore PPC cases. +*/ +if (!IS_ENABLED (CONFIG_PPC ) && +of_property_count_strings (bus,"compatible" ) ==1 ) + bus->fwnode.flags |=FWNODE_FLAG_NOT_DEVICE ;This looks fragile relying on 1 compatible string, and the DT flags in this code have been fragile too. I'm pretty sure we have cases of simple-bus or simple-mfd that also have another compatible.
Quoted 1 line
Couldn't we solve this with a simple driver?
Oh, I didn't think you'd like that. I'd lean towards that option too if we can address some of the other concerns below.
Quoted 2 lines
Make 'simple-pm-bus'
driver work for other cases?Quoted 7 lines
Quoted 2 lines
BTW, this patch doesn't even work for
simple-pm-bus.How do you mean? Because simple-pm-bus already has a driver and doesn't set "matches" param when it calls
of_platform_populate()and this flag won't be set. So at least for simple-pm-bus I don't see any issue.You're right.
Quoted 3 lines
I was trying to reuse
of_default_bus_match_tablewithout explicitly referring to it, but if it's confusing I can add a separate list of compatible strings and use those here instead of using "matches".What happens with a non-default table? I'm not sure we can assume the same behavior.
Quoted 8 lines
Quoted 3 lines
A driver for simple-bus may cause issues if there's a more specific driver to bind to as we don't handle that. It's simply whichever matches first.
Right, this is my worry. Especially for devices like this (there are plenty of cases like this) which have a driver that probes them but also lists simple-bus
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/arch/arm/boot/dts/arm-realview-pb11mp.dts?id=73f3af7b4611d77bdaea303fb639333eb28e37d7#n299Uhh, that one is certainly a leakage of wanting an
soc_devicein the hierarchy, not any real bus structure reflecting the h/w. I'm not a fan of thesoc_devicestuff and its optional nature. Everything is an SoC, so it should always be there? Or your device hierarchy should change when you decide to add asoc_device?Quoted 4 lines
So as long as there's a compatible string that's not one of the "transparent" busses, this driver shouldn't match. So, I don't think I can get away from checking the compatible strings.
Quoted 8 lines
Quoted 4 lines
How about I check here to make sure all the "compatible" strings are from an approved transparent bus list, and if it's true, I use
driver_overrideto force match it to a transparent bus driver? Would you be okay with that?Can't we do that within a driver? We check this and fail probe if there's a more specific compatible. Then another driver can match and probe.
Quoted 6 lines
I was thinking that initially, but if we fail a probe, the driver core will permanently give up (won't search further) or might end up retrying with the same driver and never get to the other driver. I'll send out a v2 with what I described above. It's not too bad and it will also allow us to handle the PPC cases (we'll just need to keep adding the simple-bus equivalent entries to a table).
Quoted 3 lines
I wasn't sure, but I traced the calls and it looks like based on
__driver_attach()that if a driver fails probe another one matching should get to probe:
__driver_attach() is called over every device already in a bus. It's called only when a new driver is registered. So it makes sense that one ignores the error returned from probe(). You don't want to fail driver registration because one specific device needs to defer probe.
The comment is actually from __device_attach_driver()
Quoted 5 lines
/*
* Ignore errors returned by ->probe so that the next driver can try
* its luck.
*/
I saw that comment too, but isn't the comment wrong/stale?
bus_probe_device() -> device_initial_probe() -> __device_attach().
In __device_attach() we have:
ret = bus_for_each_drv(dev->bus, NULL, &data, __device_attach_driver);
If you look at bus_for_each_drv()'s comment:
* ...... If @fn returns anything but 0, we break out
* and return it. If @start is not NULL, we use it as the head
* of the list.
Inside __device_attach_driver() we see:
/*
* Ignore errors returned by ->probe so that the next driver can try
* its luck.
*/
ret = driver_probe_device(drv, dev);
if (ret < 0)
return ret;So if probe() returned an error, we'd return it right back out. And then bus_for_each_drv() will stop searching for more drivers that match.
So I don't think one driver can give up after a match and have another driver give a device a shot.
Quoted 2 lines
The PPC case is about descending nodes without a compatible string.
That whole thing is kinda confusing, but if PPC has more "simple" busses, they can just add to the list I'm maintaining in the v2 series.
-Saravana
Re: [PATCH v1 2/2] of: platform: Mark bus devices nodes with FWNODE_FLAG_NEVER_PROBES
Quoted 109 lines · Saravana Kannan
Quoted 107 lines · Rob Herring
Quoted 104 lines · Saravana Kannan
Quoted 87 lines · Rob Herring
Quoted 49 lines · Saravana Kannan
Quoted 39 lines · Rob Herring
Quoted 22 lines · Saravana Kannan
We don't want
fw_devlinkcreating device links for bus devices as they'll never probe. So mark those device node with this flag.Signed-off-by Saravana Kannan <[email protected]>--- drivers/of/platform.c | 16 ++++++++++++++++ 1 file changed, 16 insertions(+)drivers/of/platform.c +5
-0@@ -392,6 +392,22 @@ static int of_platform_bus_create(struct device_node *bus,if (!dev || !of_match_node (matches, bus))return 0 ; +/* +* If the bus node has only one compatible string value and it has +* matched as a bus node, it's never going to get probed by a device +* driver. So flag it as such so that fw_devlink knows not to create +* device links with this device. drivers/of/platform.c static int of_platform_bus_create(struct device_node *bus, · line 409
Quoted 10 lines
drivers/of/platform.c +10
-0+* +* This doesn't catch all devices that'll never probe, but this is good +* enough for now. +* +* This doesn't really work for PPC because of how it uses +* of_platform_bus_probe() to add normal devices. So ignore PPC cases. +*/ +if (!IS_ENABLED (CONFIG_PPC ) && +of_property_count_strings (bus,"compatible" ) ==1 ) + bus->fwnode.flags |=FWNODE_FLAG_NOT_DEVICE ;This looks fragile relying on 1 compatible string, and the DT flags in this code have been fragile too. I'm pretty sure we have cases of simple-bus or simple-mfd that also have another compatible.
Quoted 1 line
Couldn't we solve this with a simple driver?
Oh, I didn't think you'd like that. I'd lean towards that option too if we can address some of the other concerns below.
Quoted 2 lines
Make 'simple-pm-bus'
driver work for other cases?Quoted 7 lines
Quoted 2 lines
BTW, this patch doesn't even work for
simple-pm-bus.How do you mean? Because simple-pm-bus already has a driver and doesn't set "matches" param when it calls
of_platform_populate()and this flag won't be set. So at least for simple-pm-bus I don't see any issue.You're right.
Quoted 3 lines
I was trying to reuse
of_default_bus_match_tablewithout explicitly referring to it, but if it's confusing I can add a separate list of compatible strings and use those here instead of using "matches".What happens with a non-default table? I'm not sure we can assume the same behavior.
Quoted 8 lines
Quoted 3 lines
A driver for simple-bus may cause issues if there's a more specific driver to bind to as we don't handle that. It's simply whichever matches first.
Right, this is my worry. Especially for devices like this (there are plenty of cases like this) which have a driver that probes them but also lists simple-bus
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/arch/arm/boot/dts/arm-realview-pb11mp.dts?id=73f3af7b4611d77bdaea303fb639333eb28e37d7#n299Uhh, that one is certainly a leakage of wanting an
soc_devicein the hierarchy, not any real bus structure reflecting the h/w. I'm not a fan of thesoc_devicestuff and its optional nature. Everything is an SoC, so it should always be there? Or your device hierarchy should change when you decide to add asoc_device?Quoted 4 lines
So as long as there's a compatible string that's not one of the "transparent" busses, this driver shouldn't match. So, I don't think I can get away from checking the compatible strings.
Quoted 8 lines
Quoted 4 lines
How about I check here to make sure all the "compatible" strings are from an approved transparent bus list, and if it's true, I use
driver_overrideto force match it to a transparent bus driver? Would you be okay with that?Can't we do that within a driver? We check this and fail probe if there's a more specific compatible. Then another driver can match and probe.
I was thinking that initially, but if we fail a probe, the driver core will permanently give up (won't search further) or might end up retrying with the same driver and never get to the other driver. I'll send out a v2 with what I described above. It's not too bad and it will also allow us to handle the PPC cases (we'll just need to keep adding the simple-bus equivalent entries to a table).
Quoted 8 lines
Quoted 3 lines
I wasn't sure, but I traced the calls and it looks like based on
__driver_attach()that if a driver fails probe another one matching should get to probe:
__driver_attach()is called over every device already in a bus. It's called only when a new driver is registered. So it makes sense that one ignores the error returned fromprobe(). You don't want to fail driver registration because one specific device needs to defer probe.
The behavior should be the same no matter whether the device or driver is registered first.
Deferred probe errors are handled differently AFAICT.
Quoted 10 lines
The comment is actually from
__device_attach_driver()Quoted 5 lines
/*
* Ignore errors returned by ->probe so that the next driver can try
* its luck.
*/I saw that comment too, but isn't the comment wrong/stale?
I don't know...
Quoted 20 lines
bus_probe_device()->device_initial_probe()->__device_attach().In
__device_attach()we have:
ret =bus_for_each_drv(dev->bus, NULL, &data, __device_attach_driver);If you look at bus_for_each_drv()'s comment:
* ...... If @fn returns anything but 0, we break out
* and return it. If @start is not NULL, we use it as the head
* of the list.Inside
__device_attach_driver()we see:/* * Ignore errors returned by ->probe so that the next driver can try * its luck. */ ret = driver_probe_device(drv, dev); if (ret < 0) return ret;
Quoted 3 lines
So if
probe()returned an error, we'd return it right back out. And thenbus_for_each_drv()will stop searching for more drivers that match.
With the exception of deferred probe, probe errors are made positive and then ignored.
Quoted 2 lines
So I don't think one driver can give up after a match and have another driver give a device a shot.
I think it just needs to be tried out...
I would like the above to work because it at least partially solves the problem of multiple drivers matching. It only works if the fallback driver knows there's a better match though which is this case. If we don't know then a better match would have to unbind the first driver and bind to the better match. I'm not sure that could ever work generically.
Rob
Re: [PATCH v1 2/2] of: platform: Mark bus devices nodes with FWNODE_FLAG_NEVER_PROBES
Quoted 158 lines · Rob Herring
Quoted 109 lines · Saravana Kannan
Quoted 107 lines · Rob Herring
Quoted 104 lines · Saravana Kannan
Quoted 87 lines · Rob Herring
Quoted 49 lines · Saravana Kannan
Quoted 39 lines · Rob Herring
Quoted 22 lines · Saravana Kannan
We don't want
fw_devlinkcreating device links for bus devices as they'll never probe. So mark those device node with this flag.Signed-off-by Saravana Kannan <[email protected]>--- drivers/of/platform.c | 16 ++++++++++++++++ 1 file changed, 16 insertions(+)drivers/of/platform.c +5
-0@@ -392,6 +392,22 @@ static int of_platform_bus_create(struct device_node *bus,if (!dev || !of_match_node (matches, bus))return 0 ; +/* +* If the bus node has only one compatible string value and it has +* matched as a bus node, it's never going to get probed by a device +* driver. So flag it as such so that fw_devlink knows not to create +* device links with this device. drivers/of/platform.c static int of_platform_bus_create(struct device_node *bus, · line 409
Quoted 10 lines
drivers/of/platform.c +10
-0+* +* This doesn't catch all devices that'll never probe, but this is good +* enough for now. +* +* This doesn't really work for PPC because of how it uses +* of_platform_bus_probe() to add normal devices. So ignore PPC cases. +*/ +if (!IS_ENABLED (CONFIG_PPC ) && +of_property_count_strings (bus,"compatible" ) ==1 ) + bus->fwnode.flags |=FWNODE_FLAG_NOT_DEVICE ;This looks fragile relying on 1 compatible string, and the DT flags in this code have been fragile too. I'm pretty sure we have cases of simple-bus or simple-mfd that also have another compatible.
Quoted 1 line
Couldn't we solve this with a simple driver?
Oh, I didn't think you'd like that. I'd lean towards that option too if we can address some of the other concerns below.
Quoted 2 lines
Make 'simple-pm-bus'
driver work for other cases?Quoted 7 lines
Quoted 2 lines
BTW, this patch doesn't even work for
simple-pm-bus.How do you mean? Because simple-pm-bus already has a driver and doesn't set "matches" param when it calls
of_platform_populate()and this flag won't be set. So at least for simple-pm-bus I don't see any issue.You're right.
Quoted 3 lines
I was trying to reuse
of_default_bus_match_tablewithout explicitly referring to it, but if it's confusing I can add a separate list of compatible strings and use those here instead of using "matches".What happens with a non-default table? I'm not sure we can assume the same behavior.
Quoted 8 lines
Quoted 3 lines
A driver for simple-bus may cause issues if there's a more specific driver to bind to as we don't handle that. It's simply whichever matches first.
Right, this is my worry. Especially for devices like this (there are plenty of cases like this) which have a driver that probes them but also lists simple-bus
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/arch/arm/boot/dts/arm-realview-pb11mp.dts?id=73f3af7b4611d77bdaea303fb639333eb28e37d7#n299Uhh, that one is certainly a leakage of wanting an
soc_devicein the hierarchy, not any real bus structure reflecting the h/w. I'm not a fan of thesoc_devicestuff and its optional nature. Everything is an SoC, so it should always be there? Or your device hierarchy should change when you decide to add asoc_device?Quoted 4 lines
So as long as there's a compatible string that's not one of the "transparent" busses, this driver shouldn't match. So, I don't think I can get away from checking the compatible strings.
Quoted 8 lines
Quoted 4 lines
How about I check here to make sure all the "compatible" strings are from an approved transparent bus list, and if it's true, I use
driver_overrideto force match it to a transparent bus driver? Would you be okay with that?Can't we do that within a driver? We check this and fail probe if there's a more specific compatible. Then another driver can match and probe.
I was thinking that initially, but if we fail a probe, the driver core will permanently give up (won't search further) or might end up retrying with the same driver and never get to the other driver. I'll send out a v2 with what I described above. It's not too bad and it will also allow us to handle the PPC cases (we'll just need to keep adding the simple-bus equivalent entries to a table).
Quoted 8 lines
Quoted 3 lines
I wasn't sure, but I traced the calls and it looks like based on
__driver_attach()that if a driver fails probe another one matching should get to probe:
__driver_attach()is called over every device already in a bus. It's called only when a new driver is registered. So it makes sense that one ignores the error returned fromprobe(). You don't want to fail driver registration because one specific device needs to defer probe.The behavior should be the same no matter whether the device or driver is registered first.
Deferred probe errors are handled differently AFAICT.
Quoted 10 lines
The comment is actually from
__device_attach_driver()Quoted 5 lines
/*
* Ignore errors returned by ->probe so that the next driver can try
* its luck.
*/I saw that comment too, but isn't the comment wrong/stale?
I don't know...
Quoted 20 lines
bus_probe_device()->device_initial_probe()->__device_attach().In
__device_attach()we have:
ret =bus_for_each_drv(dev->bus, NULL, &data, __device_attach_driver);If you look at bus_for_each_drv()'s comment:
* ...... If @fn returns anything but 0, we break out
* and return it. If @start is not NULL, we use it as the head
* of the list.Inside
__device_attach_driver()we see:/* * Ignore errors returned by ->probe so that the next driver can try * its luck. */ ret = driver_probe_device(drv, dev); if (ret < 0) return ret;
Quoted 6 lines
Quoted 3 lines
So if
probe()returned an error, we'd return it right back out. And thenbus_for_each_drv()will stop searching for more drivers that match.With the exception of deferred probe, probe errors are made positive and then ignored.
Oh I totally missed this!
Quoted 5 lines
Quoted 3 lines
So I don't think one driver can give up after a match and have another driver give a device a shot.
I think it just needs to be tried out...
Oh yeah, it would definitely work and would be a lot nicer. I'll rework this.
-Saravana
Rafael J. Wysocki
maintainerRe: [PATCH v1 2/2] of: platform: Mark bus devices nodes with FWNODE_FLAG_NEVER_PROBES
In reply to Saravana KannanQuoted 147 lines · Saravana Kannan
Quoted 107 lines · Rob Herring
Quoted 98 lines · Saravana Kannan
Quoted 87 lines · Rob Herring
Quoted 49 lines · Saravana Kannan
Quoted 39 lines · Rob Herring
Quoted 22 lines · Saravana Kannan
We don't want
fw_devlinkcreating device links for bus devices as they'll never probe. So mark those device node with this flag.Signed-off-by Saravana Kannan <[email protected]>--- drivers/of/platform.c | 16 ++++++++++++++++ 1 file changed, 16 insertions(+)drivers/of/platform.c +5
-0@@ -392,6 +392,22 @@ static int of_platform_bus_create(struct device_node *bus,if (!dev || !of_match_node (matches, bus))return 0 ; +/* +* If the bus node has only one compatible string value and it has +* matched as a bus node, it's never going to get probed by a device +* driver. So flag it as such so that fw_devlink knows not to create +* device links with this device. drivers/of/platform.c static int of_platform_bus_create(struct device_node *bus, · line 409
Quoted 10 lines
drivers/of/platform.c +10
-0+* +* This doesn't catch all devices that'll never probe, but this is good +* enough for now. +* +* This doesn't really work for PPC because of how it uses +* of_platform_bus_probe() to add normal devices. So ignore PPC cases. +*/ +if (!IS_ENABLED (CONFIG_PPC ) && +of_property_count_strings (bus,"compatible" ) ==1 ) + bus->fwnode.flags |=FWNODE_FLAG_NOT_DEVICE ;This looks fragile relying on 1 compatible string, and the DT flags in this code have been fragile too. I'm pretty sure we have cases of simple-bus or simple-mfd that also have another compatible.
Quoted 1 line
Couldn't we solve this with a simple driver?
Oh, I didn't think you'd like that. I'd lean towards that option too if we can address some of the other concerns below.
Quoted 2 lines
Make 'simple-pm-bus'
driver work for other cases?Quoted 7 lines
Quoted 2 lines
BTW, this patch doesn't even work for
simple-pm-bus.How do you mean? Because simple-pm-bus already has a driver and doesn't set "matches" param when it calls
of_platform_populate()and this flag won't be set. So at least for simple-pm-bus I don't see any issue.You're right.
Quoted 3 lines
I was trying to reuse
of_default_bus_match_tablewithout explicitly referring to it, but if it's confusing I can add a separate list of compatible strings and use those here instead of using "matches".What happens with a non-default table? I'm not sure we can assume the same behavior.
Quoted 8 lines
Quoted 3 lines
A driver for simple-bus may cause issues if there's a more specific driver to bind to as we don't handle that. It's simply whichever matches first.
Right, this is my worry. Especially for devices like this (there are plenty of cases like this) which have a driver that probes them but also lists simple-bus
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/arch/arm/boot/dts/arm-realview-pb11mp.dts?id=73f3af7b4611d77bdaea303fb639333eb28e37d7#n299Uhh, that one is certainly a leakage of wanting an
soc_devicein the hierarchy, not any real bus structure reflecting the h/w. I'm not a fan of thesoc_devicestuff and its optional nature. Everything is an SoC, so it should always be there? Or your device hierarchy should change when you decide to add asoc_device?Quoted 4 lines
So as long as there's a compatible string that's not one of the "transparent" busses, this driver shouldn't match. So, I don't think I can get away from checking the compatible strings.
Quoted 8 lines
Quoted 4 lines
How about I check here to make sure all the "compatible" strings are from an approved transparent bus list, and if it's true, I use
driver_overrideto force match it to a transparent bus driver? Would you be okay with that?Can't we do that within a driver? We check this and fail probe if there's a more specific compatible. Then another driver can match and probe.
Quoted 6 lines
I was thinking that initially, but if we fail a probe, the driver core will permanently give up (won't search further) or might end up retrying with the same driver and never get to the other driver. I'll send out a v2 with what I described above. It's not too bad and it will also allow us to handle the PPC cases (we'll just need to keep adding the simple-bus equivalent entries to a table).
Quoted 3 lines
I wasn't sure, but I traced the calls and it looks like based on
__driver_attach()that if a driver fails probe another one matching should get to probe:
__driver_attach()is called over every device already in a bus. It's called only when a new driver is registered. So it makes sense that one ignores the error returned fromprobe(). You don't want to fail driver registration because one specific device needs to defer probe.The comment is actually from
__device_attach_driver()Quoted 5 lines
/*
* Ignore errors returned by ->probe so that the next driver can try
* its luck.
*/I saw that comment too, but isn't the comment wrong/stale?
bus_probe_device()->device_initial_probe()->__device_attach().In
__device_attach()we have:
ret =bus_for_each_drv(dev->bus, NULL, &data, __device_attach_driver);If you look at bus_for_each_drv()'s comment:
* ...... If @fn returns anything but 0, we break out
* and return it. If @start is not NULL, we use it as the head
* of the list.Inside
__device_attach_driver()we see:/* * Ignore errors returned by ->probe so that the next driver can try * its luck. */ ret = driver_probe_device(drv, dev); if (ret < 0) return ret;
Quoted 3 lines
So if
probe()returned an error, we'd return it right back out. And thenbus_for_each_drv()will stop searching for more drivers that match.
Well, not quite.
If ->probe() returns an error, really_probe() will convert it into a positive number. __driver_probe_device() will then return as is and driver_probe_device() doesn't touch that value.
Bottom line: you'll see a positive number here, so the check above will not trigger and 0 is returned, so bus_for_each_drv() will actually continue searching.
Quoted 2 lines
So I don't think one driver can give up after a match and have another driver give a device a shot.
Yes, it can.
Re: [PATCH v1 2/2] of: platform: Mark bus devices nodes with FWNODE_FLAG_NEVER_PROBES
In reply to Saravana KannanQuoted 22 lines · Saravana Kannan
We don't want
fw_devlinkcreating device links for bus devices as they'll never probe. So mark those device node with this flag.Signed-off-by Saravana Kannan <[email protected]>--- drivers/of/platform.c | 16 ++++++++++++++++ 1 file changed, 16 insertions(+)drivers/of/platform.c +5
-0@@ -392,6 +392,22 @@ static int of_platform_bus_create(struct device_node *bus,if (!dev || !of_match_node (matches, bus))return 0 ; +/* +* If the bus node has only one compatible string value and it has +* matched as a bus node, it's never going to get probed by a device +* driver. So flag it as such so that fw_devlink knows not to create +* device links with this device.
drivers/of/platform.c static int of_platform_bus_create(struct device_node *bus, · line 409
Quoted 10 lines
drivers/of/platform.c +10
-0+* +* This doesn't catch all devices that'll never probe, but this is good +* enough for now. +* +* This doesn't really work for PPC because of how it uses +* of_platform_bus_probe() to add normal devices. So ignore PPC cases. +*/ +if (!IS_ENABLED (CONFIG_PPC ) && +of_property_count_strings (bus,"compatible" ) ==1 ) + bus->fwnode.flags |=FWNODE_FLAG_NOT_DEVICE ;
This patch is wrong. This flag should have been FWNODE_FLAG_NEVER_PROBES.
-Saravana
Quoted 7 lines
drivers/of/platform.c +1
-1+for_each_child_of_node (bus, child) {pr_debug (" create child: %pOF\n" , child); rc =of_platform_bus_create (child, matches, lookup, &dev->dev, strict); --2.33.0.259.gc128427fd7-goog
Oops, forgot to use a proper subject. Sorry.
-Saravana
Quoted 21 lines · Saravana Kannan
Ulf, mind testing this?
Thanks,
Saravana
[1] - https://lore.kernel.org/lkml/CAPDyKFo9Bxremkb1dDrr4OcXSpE0keVze94Cm=zrkOVxHHxBmQ@mail.gmail.com/Cc Ulf Hansson <[email protected]>Saravana Kannan (2):
driver core: Add support forFWNODE_FLAG_NEVER_PROBES
of: platform: Mark bus devices nodes withFWNODE_FLAG_NEVER_PROBESdrivers/base/core.c | 8 ++++++++ drivers/of/platform.c | 16 ++++++++++++++++ include/linux/fwnode.h | 8 +++++--- 3 files changed, 29 insertions(+), 3 deletions(-)--
2.33.0.259.gc128427fd7-goog
Rafael J. Wysocki
maintainerQuoted 2 lines · Saravana Kannan
Oops, forgot to use a proper subject. Sorry.
Is this a replacement for the "Fix rtl8366rb issues with fw_devlink=on " series?
Quoted 22 lines · Saravana Kannan
Quoted 21 lines
Ulf, mind testing this?
Thanks,
Saravana
[1] - https://lore.kernel.org/lkml/CAPDyKFo9Bxremkb1dDrr4OcXSpE0keVze94Cm=zrkOVxHHxBmQ@mail.gmail.com/Cc Ulf Hansson <[email protected]>Saravana Kannan (2):
driver core: Add support forFWNODE_FLAG_NEVER_PROBES
of: platform: Mark bus devices nodes withFWNODE_FLAG_NEVER_PROBESdrivers/base/core.c | 8 ++++++++ drivers/of/platform.c | 16 ++++++++++++++++ include/linux/fwnode.h | 8 +++++--- 3 files changed, 29 insertions(+), 3 deletions(-)--
2.33.0.259.gc128427fd7-goog
Quoted 6 lines · Rafael J. Wysocki
Quoted 2 lines · Saravana Kannan
Oops, forgot to use a proper subject. Sorry.
Is this a replacement for the "Fix rtl8366rb issues with fw_devlink=on " series?
No. This is unrelated to that. This is the issue I'm trying to fix:
https://lore.kernel.org/lkml/CAPDyKFo9Bxremkb1dDrr4OcXSpE0keVze94Cm=zrkOVxHHxBmQ@mail.gmail.com/
This is kind of a replacement to, but the patch below might be needed in general (needs more thought):
https://lore.kernel.org/lkml/CAGETcx9U2M5i1CAx605fG3Qwm1xwjH2uy4kY4vrAF7YSRSSg+w@mail.gmail.com/
-Saravana
Quoted 24 lines
Quoted 24 lines · Saravana Kannan
Quoted 21 lines
Ulf, mind testing this?
Thanks,
Saravana
[1] - https://lore.kernel.org/lkml/CAPDyKFo9Bxremkb1dDrr4OcXSpE0keVze94Cm=zrkOVxHHxBmQ@mail.gmail.com/Cc Ulf Hansson <[email protected]>Saravana Kannan (2):
driver core: Add support forFWNODE_FLAG_NEVER_PROBES
of: platform: Mark bus devices nodes withFWNODE_FLAG_NEVER_PROBESdrivers/base/core.c | 8 ++++++++ drivers/of/platform.c | 16 ++++++++++++++++ include/linux/fwnode.h | 8 +++++--- 3 files changed, 29 insertions(+), 3 deletions(-)--
2.33.0.259.gc128427fd7-goog
Rafael J. Wysocki
maintainerQuoted 11 lines · Saravana Kannan
Quoted 6 lines · Rafael J. Wysocki
Quoted 2 lines · Saravana Kannan
Oops, forgot to use a proper subject. Sorry.
Is this a replacement for the "Fix rtl8366rb issues with fw_devlink=on " series?
No. This is unrelated to that. This is the issue I'm trying to fix:
https://lore.kernel.org/lkml/CAPDyKFo9Bxremkb1dDrr4OcXSpE0keVze94Cm=zrkOVxHHxBmQ@mail.gmail.com/
Allright, thanks!
Quoted 3 lines
This is kind of a replacement to, but the patch below might be needed in general (needs more thought):
https://lore.kernel.org/lkml/CAGETcx9U2M5i1CAx605fG3Qwm1xwjH2uy4kY4vrAF7YSRSSg+w@mail.gmail.com/
I see.
Quoted 22 lines
Quoted 22 lines
Quoted 22 lines · Saravana Kannan
Quoted 21 lines
Ulf, mind testing this?
Thanks,
Saravana
[1] - https://lore.kernel.org/lkml/CAPDyKFo9Bxremkb1dDrr4OcXSpE0keVze94Cm=zrkOVxHHxBmQ@mail.gmail.com/Cc Ulf Hansson <[email protected]>Saravana Kannan (2):
driver core: Add support forFWNODE_FLAG_NEVER_PROBES
of: platform: Mark bus devices nodes withFWNODE_FLAG_NEVER_PROBESdrivers/base/core.c | 8 ++++++++ drivers/of/platform.c | 16 ++++++++++++++++ include/linux/fwnode.h | 8 +++++--- 3 files changed, 29 insertions(+), 3 deletions(-)--
2.33.0.259.gc128427fd7-goog