From: Matthew Garrett <mjg@redhat.com>
To: Corentin Chary <corentin.chary@gmail.com>
Cc: platform-driver-x86@vger.kernel.org,
LKML <linux-kernel@vger.kernel.org>,
linux-input@vger.kernel.org
Subject: Re: Handling special keys in platform drivers
Date: Fri, 13 Jan 2012 22:42:11 +0000 [thread overview]
Message-ID: <20120113224211.GB29022@srcf.ucam.org> (raw)
In-Reply-To: <CAHR064jAJkQCd_Tsrx7NHe_RbaBbNcX4sMwy=zkZCZNUNo=fAw@mail.gmail.com>
On Mon, Jan 09, 2012 at 07:24:14AM +0100, Corentin Chary wrote:
> The real problem is that for keyboard backlight to work, it needs DE
> cooperation, and only gnome as implemented that right now, and other
> (except KDE) will probably neither have the resources to handle all
> the possible keys correctly. And of course, who should handle the keys
> when there is no DE running at all ?
The problem with handling this in kernel is that there isn't an
obviously correct policy. ACPI will typically only expose 16 or so
backlight levels so the behaviour is easy enough, but (depending on how
the hardware is wired up) i915 may expose around 20,000. Further, one
machine may expose different backlight controls for different displays,
and in that situation you need to know which one the input event is
expected to correspond to.
Doing backlight control properly involves a lot of policy work, and I'm
reluctant to argue that that ought to be in the kernel.
--
Matthew Garrett | mjg59@srcf.ucam.org
next prev parent reply other threads:[~2012-01-13 22:42 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-09 6:24 Handling special keys in platform drivers Corentin Chary
2012-01-09 7:09 ` joeyli
2012-01-09 7:34 ` Corentin Chary
2012-01-13 22:42 ` Matthew Garrett [this message]
2012-01-14 8:58 ` Corentin Chary
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=20120113224211.GB29022@srcf.ucam.org \
--to=mjg@redhat.com \
--cc=corentin.chary@gmail.com \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=platform-driver-x86@vger.kernel.org \
/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).