* reseting an input device due to sleep/resume cycle @ 2007-06-16 21:03 Henrique de Moraes Holschuh [not found] ` <20070616210321.GA17379-ZGHd14iZgfaRjzvQDGKj+xxZW9W5cXbT@public.gmane.org> 0 siblings, 1 reply; 2+ messages in thread From: Henrique de Moraes Holschuh @ 2007-06-16 21:03 UTC (permalink / raw) To: Dmitry Torokhov; +Cc: linux-input, ibm-acpi-devel Dmitry, input gurus, When a ThinkPad does an sleep cycle, the firmware explicitly kills all pending hotkey state. That reminds me that I also need to do the same in thinkpad-acpi. How does one tell the input layer that it should clear its idea of the current state of all events in a input device? I couldn't find any input_reset() function... Or is such a reset not needed? The recent issue with ACPI and EV_SW SW_LID seems to indicate that in some cases these resets are indeed needed. For EV_SW, it appears that I'd have to interate over all my switches and reset them. But what about EV_KEY and the others? -- "One disk to rule them all, One disk to find them. One disk to bring them all and in the darkness grind them. In the Land of Redmond where the shadows lie." -- The Silicon Valley Tarot Henrique Holschuh ^ permalink raw reply [flat|nested] 2+ messages in thread
[parent not found: <20070616210321.GA17379-ZGHd14iZgfaRjzvQDGKj+xxZW9W5cXbT@public.gmane.org>]
* Re: reseting an input device due to sleep/resume cycle [not found] ` <20070616210321.GA17379-ZGHd14iZgfaRjzvQDGKj+xxZW9W5cXbT@public.gmane.org> @ 2007-06-18 13:48 ` Dmitry Torokhov 0 siblings, 0 replies; 2+ messages in thread From: Dmitry Torokhov @ 2007-06-18 13:48 UTC (permalink / raw) To: Henrique de Moraes Holschuh Cc: linux-input-jyMamyUUXNJG4ohzP4jBZS1Fcj925eT/, ibm-acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f Hi Henrique, On 6/16/07, Henrique de Moraes Holschuh <hmh-N3TV7GIv+o9fyO9Q7EP/yw@public.gmane.org> wrote: > Dmitry, input gurus, > > When a ThinkPad does an sleep cycle, the firmware explicitly kills all > pending hotkey state. That reminds me that I also need to do the same in > thinkpad-acpi. > > How does one tell the input layer that it should clear its idea of the > current state of all events in a input device? I couldn't find any > input_reset() function... > > Or is such a reset not needed? The recent issue with ACPI and EV_SW SW_LID > seems to indicate that in some cases these resets are indeed needed. For > EV_SW, it appears that I'd have to interate over all my switches and reset > them. But what about EV_KEY and the others? We do need to refresh switch state upon resume because use may change it while box is sleeping. With keys we shoudl just assume that they are all released at the time box is waking up. Now that I have input core converted to "struct device" I will add suspend/resume support to input devices to mark all keys as "released' unpon suspending and restore led state and repeat rate for keyboards upon resuming. -- Dmitry ------------------------------------------------------------------------- This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ ^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2007-06-18 13:48 UTC | newest] Thread overview: 2+ messages (download: mbox.gz follow: Atom feed -- links below jump to the message on this page -- 2007-06-16 21:03 reseting an input device due to sleep/resume cycle Henrique de Moraes Holschuh [not found] ` <20070616210321.GA17379-ZGHd14iZgfaRjzvQDGKj+xxZW9W5cXbT@public.gmane.org> 2007-06-18 13:48 ` Dmitry Torokhov
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for NNTP newsgroup(s).