On Tue 2016-11-15 11:58:06, Jacek Anaszewski wrote: > On 11/15/2016 11:31 AM, Pavel Machek wrote: > >Hi! > > > >>>Hmm, v4 still calls led_notify_brightness_change(led_cdev) > >>>from both __led_set_brightness() and __led_set_brightness_blocking(). > >> > >>Ugh, I see I accidentally send a v4 twice, instead of > >>calling the version which dropped those called v5 as > >>I should have, sorry. > >> > >>The v4 which I would like to see merged, the one with > >>those calls dropped, is here: > >> > >>https://patchwork.kernel.org/patch/9423093/ > > > >Please, lets fix this properly. > > > >The LED you are talking about _has_ a trigger, implemented in > >hardware. That trigger can change LED brightness behind kernel's (and > >userspace's) back. Don't pretend the trigger does not exist, it does. > > > >And when you do that, you'll have nice place to report changes to > >userspace -- trigger can now export that information, and offer poll() > >interface. > > Well, that sounds interesting. It is logically justifiable. Thanks. > I initially proposed exactly this solution, with recently > added userspace LED being a trigger listener. It seems a bit > awkward though. How would you listen to the trigger events? Trigger exposes a file in sysfs, with poll() working on that file (and probably read exposing the current brightness). Key difference is that only triggers where this makes sense (keyboard backlight) expose it and carry the overhead. CPU trigger would definitely not do this. Best regards, Pavel -- (english) http://www.livejournal.com/~pavelmachek (cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
Attachment:
signature.asc
Description: Digital signature
