Messages in this thread | | | Date | Tue, 7 Dec 2010 17:18:27 +0100 (CET) | From | Sebastian Ott <> | Subject | [RFC] bind/unbind uevent |
| |
Hi,
There is currently no generic trigger for userspace to know when a driver is bound to a device. Such a trigger may be required in cases where setup steps must be performed in userspace after the device is bound, e.g. because the driver adds sysfs attributes in its probe function.
I can imagine 3 possible ways to solve this problem: * add a bus specific change event (triggered by BUS_NOTIFY_BOUND_DRIVER) - this may result in duplicated code for each bus * dissable autoprobing and "manually" probe the device from userspace triggered by the add event - this duplicates logic already implemented in the kernel * add a generic bind/unbind uevent
Which one is preferred from a driver core perspective?
Regards, Sebastian
| |