Messages in this thread | | | From | Rob Herring <> | Date | Thu, 12 Jan 2017 11:27:01 -0600 | Subject | sysfs deferred_probe attribute |
| |
I just noticed that we have a new device attribute 'deferred_probe' added in 4.10 with this commit:
commit 6751667a29d6fd64afb9ce30567ad616b68ed789 Author: Ben Hutchings <ben.hutchings@codethink.co.uk> Date: Tue Aug 16 14:34:18 2016 +0100
driver core: Add deferred_probe attribute to devices in sysfs
It is sometimes useful to know that a device is on the deferred probe list rather than, say, not having a driver available. Expose this information to user-space.
Signed-off-by: Ben Hutchings <ben.hutchings@codethink.co.uk> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
It seems like a bad idea to add an ABI for an internal kernel feature. When/if we replace deferred probe with something better based on functional dependencies are we going to keep this attr around? Or remove it and assume no userspace uses it? Perhaps it should be hidden behind CONFIG_DEBUG or just make a debugfs file that lists the deferred list. Then you wouldn't have to hunt for what got deferred.
Rob
| |