From: "Dmitry Torokhov" <dmitry.torokhov-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: Henrique de Moraes Holschuh
<hmh-N3TV7GIv+o9fyO9Q7EP/yw@public.gmane.org>
Cc: linux-input-jyMamyUUXNJG4ohzP4jBZS1Fcj925eT/@public.gmane.org,
ibm-acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: Re: reseting an input device due to sleep/resume cycle
Date: Mon, 18 Jun 2007 09:48:37 -0400 [thread overview]
Message-ID: <d120d5000706180648sac84927k2c11f070ede41122@mail.gmail.com> (raw)
In-Reply-To: <20070616210321.GA17379-ZGHd14iZgfaRjzvQDGKj+xxZW9W5cXbT@public.gmane.org>
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/
prev parent reply other threads:[~2007-06-18 13:48 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
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 message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=d120d5000706180648sac84927k2c11f070ede41122@mail.gmail.com \
--to=dmitry.torokhov-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
--cc=hmh-N3TV7GIv+o9fyO9Q7EP/yw@public.gmane.org \
--cc=ibm-acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
--cc=linux-input-jyMamyUUXNJG4ohzP4jBZS1Fcj925eT/@public.gmane.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
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).