linux-input.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: Pavel Machek <pavel@ucw.cz>
Cc: Alan Jenkins <sourcejedi.lkml@googlemail.com>,
	linux-input@vger.kernel.org,
	linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] Input: serio - re-add thaw (and add freeze)
Date: Wed, 24 Feb 2010 23:38:49 -0800	[thread overview]
Message-ID: <201002242338.49873.dmitry.torokhov@gmail.com> (raw)
In-Reply-To: <20100225070302.GB1601@ucw.cz>

On Wednesday 24 February 2010 11:03:03 pm Pavel Machek wrote:
> On Tue 2010-02-16 09:22:33, Dmitry Torokhov wrote:
> > On Tue, Feb 16, 2010 at 04:48:30PM +0000, Alan Jenkins wrote:
> > > On 2/4/10, Alan Jenkins <alan-jenkins@tuffmail.co.uk> wrote:
> > > > Dmitry Torokhov wrote:
> > > >> On Wed, Feb 03, 2010 at 06:59:54PM +0000, Alan Jenkins wrote:
> > > >>> 633aae2 "Input: i8042 - switch to using dev_pm_ops"
> > > >>> removed handling for PMSG_THAW, causing obscure breakage.
> > > >>> 
> > > >>> It can break if you press keys during hibernation,
> > > >>> which causes subsequent keypresses to be lost -
> > > >>> so you can't cancel s2disk by pressing backspace -
> > > >>> and then just before system poweroff you get
> > > >>> "psmouse.c: Failed to deactivate mouse".
> > > >>> 
> > > >>> So let's add the thaw handler back.
> > > >>> 
> > > >>> Also set the freeze handler.  It looks like PMSG_FREEZE
> > > >>> didn't do anything in the past, but I think that must
> > > >>> have been an oversight.
> > > >> 
> > > >> We do not need to do anything special at freeze time that is why
> > > >> there wasn't freeze handler. And so thaw should be pretty much noop
> > > >> as well.
> > > 
> > > Ok, so I did some more mindless fiddling.  It seems that all it needs
> > > is to call the interrupt handler at thaw time.
> > 
> > Yep, this makes more sense. If you happen to press the key(s) while
> > interrupts are off the keyboard controller becomes "jammed". Your sign
> > off please?
> 
> Dmitry wants your Signed-off-by: line, to easily apply the patch.
>

Pavel, I already have it and it is in mainline.

Thanks.

-- 
Dmitry

      reply	other threads:[~2010-02-25  7:38 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-03 18:59 [PATCH] Input: serio - re-add thaw (and add freeze) Alan Jenkins
2010-02-03 19:11 ` Dmitry Torokhov
2010-02-04 10:22   ` Alan Jenkins
2010-02-16 16:48     ` Alan Jenkins
2010-02-16 17:22       ` Dmitry Torokhov
2010-02-25  7:03         ` Pavel Machek
2010-02-25  7:38           ` 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=201002242338.49873.dmitry.torokhov@gmail.com \
    --to=dmitry.torokhov@gmail.com \
    --cc=linux-input@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pavel@ucw.cz \
    --cc=sourcejedi.lkml@googlemail.com \
    /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).