From: Dmitry Torokhov <dtor@insightbb.com>
To: "Bruno Prémont" <bonbons@linux-vserver.org>
Cc: Linux Input <linux-input@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
"R. J. Wysocki" <Rafal.Wysocki@fuw.edu.pl>
Subject: Re: Input+S3: extra keycodes forgotten after suspend
Date: Tue, 27 May 2008 01:52:24 -0400 [thread overview]
Message-ID: <200805270152.25744.dtor@insightbb.com> (raw)
In-Reply-To: <20080523225714.3f0953f3@neptune.home>
On Friday 23 May 2008 16:57, Bruno Prémont wrote:
> On Fri, 23 May 2008 Dmitry Torokhov <dmitry.torokhov@gmail.com> wrote:
> > > Ah, ok, great.. I think we simply need to move dritek out of the
> > > place where you put it in so it does not interfere with our efforts
> > > to resume keyboard and mouse ;) I will see what I can do there..
> > >
> >
> > So what about the patch below? Does it work for you?
> >
> > Thanks!
>
> Hi Dmitry,
>
> Yes, this patch works for me (in combination with
> http://lkml.org/lkml/2008/5/16/430 ), see attached boot+suspend&resume
> log.
>
> You will eventually note the following lines during resume process:
> ...
> [ 150.588965] /usr/src/linux-2.6.25.4-orig/drivers/input/serio/i8042.c: 60 -> i8042 (command) [15985]
> [ 150.588965] /usr/src/linux-2.6.25.4-orig/drivers/input/serio/i8042.c: 47 -> i8042 (parameter) [15985]
> [ 150.588965] /usr/src/linux-2.6.25.4-orig/drivers/input/serio/i8042.c: 00 <- i8042 (interrupt, 0, 0) [15985]
> [ 150.588965] atkbd.c: Unknown key pressed (translated set 2, code 0x0 on isa0060/serio0).
> [ 150.588965] atkbd.c: Use 'setkeycodes 00 <keycode>' to make it known.
> [ 150.588965] /usr/src/linux-2.6.25.4-orig/drivers/input/serio/i8042.c: f2 -> i8042 (kbd-data) [15985]
> [ 150.609410] /usr/src/linux-2.6.25.4-orig/drivers/input/serio/i8042.c: fa <- i8042 (interrupt, 0, 1) [15987]
> ...
>
I see. Could you please try the patch below (in addition to the other
2 you have) and see if that 00 keycode is still reported?
Thanks!
--
Dmitry
Input: atkbd - mark keyboard as disabled when suspending/unloading
This will shut off garbage that may come from KBD port during resume.
Signed-off-by: Dmitry Torokhov <dtor@mail.ru>
---
drivers/input/keyboard/atkbd.c | 2 ++
1 file changed, 2 insertions(+)
Index: work/drivers/input/keyboard/atkbd.c
===================================================================
--- work.orig/drivers/input/keyboard/atkbd.c
+++ work/drivers/input/keyboard/atkbd.c
@@ -807,6 +807,8 @@ static int atkbd_activate(struct atkbd *
static void atkbd_cleanup(struct serio *serio)
{
struct atkbd *atkbd = serio_get_drvdata(serio);
+
+ atkbd_disable(atkbd);
ps2_command(&atkbd->ps2dev, NULL, ATKBD_CMD_RESET_BAT);
}
next prev parent reply other threads:[~2008-05-27 5:52 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-16 20:25 Input+S3: extra keycodes forgotten after suspend Bruno Prémont
2008-05-16 20:38 ` Dmitry Torokhov
2008-05-16 21:00 ` Bruno Prémont
2008-05-19 15:50 ` Dmitry Torokhov
2008-05-19 16:45 ` Bruno Prémont
2008-05-21 17:55 ` Dmitry Torokhov
2008-05-21 20:08 ` Bruno Prémont
2008-05-21 20:38 ` Dmitry Torokhov
2008-05-23 4:44 ` Dmitry Torokhov
2008-05-23 20:57 ` Bruno Prémont
2008-05-27 5:52 ` Dmitry Torokhov [this message]
2008-05-27 20:52 ` Bruno Prémont
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=200805270152.25744.dtor@insightbb.com \
--to=dtor@insightbb.com \
--cc=Rafal.Wysocki@fuw.edu.pl \
--cc=bonbons@linux-vserver.org \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.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