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
| ||
|
Date: Thu, 15 Apr 2010 21:12:18 +0200 From: Pavel Machek <pavel@....cz> To: Takashi Iwai <tiwai@...e.de> Cc: Dmitry Torokhov <dmitry.torokhov@...il.com>, linux-input@...r.kernel.org, linux-kernel@...r.kernel.org Subject: Re: [PATCH 2/2] input: Add LED support to Synaptics device Hi! > The new Synaptics devices have an LED on the top-left corner. > This is controlled via the command 0x0a with parameters 0x88 or 0x10. > > The detection of the LED isn't clear yet. It should have been the new > capability bits that indicate the presence, but on real machines, it > doesn't fit. So, for the time being, the driver checks the product id > in the ext capability bits and assumes that LED exists on the known > devices. > > The support of LED is controlled via a normal input event with EV_LED > bit mask. It supports LED_MUTE bit. X driver can detect the LED > support by checking these bits. Could we use generic LED API for this? It is not really 'mute' led after all... Pavel -- (english) http://www.livejournal.com/~pavelmachek (cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html -- 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/
Powered by blists - more mailing lists