Re: Fuijtsu Lifebook RFKILL support

[Tony Vroon <tony@linx.net>]

[-- Attachment #1: Type: text/plain, Size: 1013 bytes --]

On Thu, 2008-12-11 at 14:52 -0200, Henrique de Moraes Holschuh wrote:
> That is an input device, that should issue EV_SW SW_RFKILL_ALL events (and
> not EV_KEY, etc).

Okay, glad I asked.
Can I combine EV_SW & EV_KEY on a single input device (as there is
already a FUJ02E3 input device within the device driver) or would that
break things?

Also, would there be a clear acknowledgement of an rfkill state change
in Gnome?

> So, you won't even #include <linux/rfkill.h>.

Noted, include removed. 

> The only pitfall I know of is that you have to re-sync the input layer at every point it could have missed
> a state change.  This means you must issue gratuitous EV_SW SW_RFKILL_ALL
> events with the current state of the switch after you created the input
> device, after resume (from S3/S4), and when you get the notifier from ACPI
> that the switch state could have changed.

Done at input device creation and when notified. I have no resume
callback to hook into.

Regards,
Tony V.

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 197 bytes --]