[lkml]   [2010]   [Dec]   [7]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
    Subject[RFC] bind/unbind uevent

    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?


     \ /
      Last update: 2010-12-07 17:21    [W:0.031 / U:6.984 seconds]
    ©2003-2016 Jasper Spaans. hosted at Digital OceanAdvertise on this site