linux-kernel - Handling special keys in platform drivers

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Message-ID: <CAHR064jAJkQCd_Tsrx7NHe_RbaBbNcX4sMwy=zkZCZNUNo=fAw@mail.gmail.com>
Date:	Mon, 9 Jan 2012 07:24:14 +0100
From:	Corentin Chary <corentin.chary@...il.com>
To:	platform-driver-x86@...r.kernel.org
Cc:	LKML <linux-kernel@...r.kernel.org>,
	Matthew Garrett <mjg@...hat.com>, linux-input@...r.kernel.org
Subject: Handling special keys in platform drivers

Hi,

Some of the platform drivers in platform/x86/ (and probably other) are
relaying keys to userspace and are also controlling the device
associated to these key. A simple example is screen brightness,
keyboard backlight or rfkill.

In this case the driver send a key to userspace, userspace has to
handle this key and control the right device.

Most of the time, this job is done by:
- ACPI scripts (legacy)
- DE (gnome-power-manager, kde's solid)

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 ?

So I was wondering if we could introduce an "auto" mode for this
drivers. For example, with this mode enabled, asus-wmi would filter
the keys and control keyboard backlight directly (and rfkill/screen
brightness ?).

What do you think about it ?

Thanks,

-- 
Corentin Chary
http://xf.iksaif.net
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/