RE: [RFC] [PATCH] Make ACPI button driver an input device

>> > There are keyboards with power/sleep buttons. It makes 
>sense they have
>> > the same behavior than ACPI buttons.
>> Agree, make them behave like ACPI buttons -- remove them 
>from input stream, as they do not belong there...
>
>What if there is no ACPI? What if I want to remap the button to do
>something else? Input layer is the proper place for them.

If you define input layer as a universe place to all manual input 
activity, then I agree to port some type of ACPI event into
input layer.  But it shouldn't be a fake keyboard scancode,
My suggestion is to have a separate input event type,e.g. EV_ACPI
for acpi event layer.

>
>--
>Dmitry

Thanks,
Luming
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

---

• Follow-Ups:
  • Re: [RFC] [PATCH] Make ACPI button driver an input device
    • From: Pavel Machek <[email protected]>
  • Re: [RFC] [PATCH] Make ACPI button driver an input device
    • From: "Dmitry Torokhov" <[email protected]>
  • Re: [RFC] [PATCH] Make ACPI button driver an input device
    • From: Martin Mares <[email protected]>

• Prev by Date: Re: kfree(NULL)
• Next by Date: Re: [patch 1/5] mm: remap_vmalloc_range
• Previous by thread: Re: [RFC] [PATCH] Make ACPI button driver an input device
• Next by thread: Re: [RFC] [PATCH] Make ACPI button driver an input device
• Index(es):
  • Date
  • Thread

[Index of Archives]     [Kernel Newbies]     [Netfilter]     [Bugtraq]     [Photo]     [Stuff]     [Gimp]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Video 4 Linux]     [Linux for the blind]     [Linux Resources]