From: "Pali Rohár" <pali.rohar@gmail.com>
To: Richard Purdie <rpurdie@rpsys.net>,
Jacek Anaszewski <jacek.anaszewski@gmail.com>,
Pavel Machek <pavel@ucw.cz>,
linux-leds@vger.kernel.org, linux-kernel@vger.kernel.org,
Darren Hart <dvhart@infradead.org>,
platform-driver-x86@vger.kernel.org
Subject: LED devices & poll() for brightness attribute
Date: Wed, 22 Feb 2017 10:06:30 +0100 [thread overview]
Message-ID: <20170222090630.GB21558@pali> (raw)
Hello,
now in linus tree appeared new support for brightness_hw_changed sysfs
attribute which provides poll() for reporting brightness changes from
hardware itself.
But this support is useful just for one single central userspace
application which will control all leds in system other application
which will change state by /sys/class/leds/ will de-synchronize that one
central application.
On linux system it is normal that more userspace application could
change brightness level and to make them happy and synchronized with
kernel state all those application should know that there was change (by
other application) of brightness level. Currently they will know only
about change done by hardware itself.
So I think new ABI is not sufficient and I would propose to add poll()
support also for changes done by userspace, write() to attribute
/sys/class/leds/.../brightness.
--
Pali Rohár
pali.rohar@gmail.com
next reply other threads:[~2017-02-22 9:06 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-22 9:06 Pali Rohár [this message]
2017-02-22 12:25 ` LED devices & poll() for brightness attribute Pavel Machek
2017-02-22 12:39 ` Pali Rohár
2017-02-22 20:54 ` Pavel Machek
2017-02-22 21:16 ` Pali Rohár
2017-02-23 14:37 ` Pavel Machek
2017-02-23 14:48 ` Pali Rohár
2017-02-23 20:23 ` Pavel Machek
2017-02-23 20:44 ` Pali Rohár
2017-02-23 21:03 ` Pavel Machek
2017-02-24 8:50 ` Pali Rohár
2017-02-24 8:52 ` Hans de Goede
2017-02-24 8:58 ` Pali Rohár
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20170222090630.GB21558@pali \
--to=pali.rohar@gmail.com \
--cc=dvhart@infradead.org \
--cc=jacek.anaszewski@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-leds@vger.kernel.org \
--cc=pavel@ucw.cz \
--cc=platform-driver-x86@vger.kernel.org \
--cc=rpurdie@rpsys.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).