On Mon, 2010-07-05 at 09:28 +0800, Dmitry Torokhov wrote: > On Jul 4, 2010, at 6:09 PM, Zhang Rui <rui.zhang@xxxxxxxxx> wrote: > > > On Sun, 2010-07-04 at 16:35 +0800, Dmitry Torokhov wrote: > >> On Mon, Jun 21, 2010 at 09:56:37PM -0400, Len Brown wrote: > >>> Dmitry, > >>> Is there a reason not to simply add a "state" attribute > >>> to a LID input device? > >>> > >> > >> Len, > >> > >> There is no LED input device, there is an input device that happens > >> to > >> report EV_SW/SW_LID state. If we did that we'd need to add attributes > >> for all types of switches, keys, current values of REL and ABS axis, > >> min/max/fuzz/flat settings of ABS axis and so forth that input device > >> might report. I do not think it is a good idea. > >> > > I agree. > > How about adding a field in uevent file that reports the switch > > status? > > > > > I think if you can listen to uevents you can just as easily open /dev/ > input/eventX and listen to proper input events. > the question is users may want to get the lid switch STATUS, asynchronously. thank, rui -- To unsubscribe from this list: send the line "unsubscribe linux-acpi" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
