From: "Pali Rohár" <pali.rohar@gmail.com>
To: Hans de Goede <hdegoede@redhat.com>
Cc: Pavel Machek <pavel@ucw.cz>, Richard Purdie <rpurdie@rpsys.net>,
Jacek Anaszewski <jacek.anaszewski@gmail.com>,
linux-leds@vger.kernel.org, linux-kernel@vger.kernel.org,
Darren Hart <dvhart@infradead.org>,
platform-driver-x86@vger.kernel.org
Subject: Re: LED devices & poll() for brightness attribute
Date: Fri, 24 Feb 2017 09:58:14 +0100 [thread overview]
Message-ID: <20170224085814.GB2157@pali> (raw)
In-Reply-To: <e87ee6f8-8c7e-7370-33ae-6f420f91a582@redhat.com>
On Friday 24 February 2017 09:52:11 Hans de Goede wrote:
> Hi,
>
> On 24-02-17 09:50, Pali Rohár wrote:
> >On Thursday 23 February 2017 22:03:21 Pavel Machek wrote:
> >>So, if you seriously want to do this, can you
> >>
> >>1) write specification explaining how desktops should poll() the
> >>brightness files
> >>
> >>2) get someone to volunteer to implement that specification for at
> >>least GNOME and KDE?
> >
> >Hm... Probably I should try to implement it myself :-) and look deeply
> >what I'm proposing...
> >
> >Hans, you probably already did some changes for hw brightness changed
> >attribute... Do you have some links or application parts which handle
> >this for GNOME, KDE or other DE? So I could look at correct application?
> >
> >IIRC KDE4 uses upowerd for controlling keyboard backlight.
>
> Gnome uses upower too, and current upower master has patches to
> support brightness_hw_changed which you could use as a start.
Ok, thanks!
--
Pali Rohár
pali.rohar@gmail.com
prev parent reply other threads:[~2017-02-24 8:58 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-22 9:06 LED devices & poll() for brightness attribute Pali Rohár
2017-02-22 12:25 ` 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 [this message]
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=20170224085814.GB2157@pali \
--to=pali.rohar@gmail.com \
--cc=dvhart@infradead.org \
--cc=hdegoede@redhat.com \
--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).