[lkml]   [2007]   [Oct]   [30]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
    Subject2.6.24 - self-destructing sysfs attributes
    I realized that in patch for ACPI battery I created perfect example of 
    self-destructing sysfs attributes. Basically, on every access to battery
    properties we check battery status. If ACPI reports battery not present, we
    remove sysfs power_supply object. I.e.

    -> user space queries e.g. .../PNP0C0A:00/power_supply/BAT1/energy_now
    -> call acpi_battery_update
    -> battery gone
    -> call power_supply_unregister(.../PNP0C0A:00/power_supply)

    I remember discussion about this but am not sure what final outcome is. So

    - is it legal in this form?
    - what is the proper way to manage such situation?
    - if I move (de-)registering of power_supply out of acpi_battery_update, is
    extra locking (refcounting) required to keep attributes alive or sysfs will
    ensure this?


    [unhandled content-type:application/pgp-signature]
     \ /
      Last update: 2007-10-30 20:37    [from the cache]
    ©2003-2014 Jasper Spaans. hosted at Digital Ocean