From: Dmitry Torokhov <dtor_core@ameritech.net>
To: linux-kernel@vger.kernel.org
Cc: Vojtech Pavlik <vojtech@suse.cz>, Pavel Machek <pavel@ucw.cz>,
Brian Perkins <bperkins@netspace.org>,
Karol Kozimor <sziwan@hell.org.pl>
Subject: Re: [PATCH 2.6 2/3] Take 2: resume support for i8042 (atkbd & psmouse)
Date: Sun, 7 Dec 2003 02:28:30 -0500 [thread overview]
Message-ID: <200312070228.31969.dtor_core@ameritech.net> (raw)
In-Reply-To: <200312070227.21460.dtor_core@ameritech.net>
===================================================================
ChangeSet@1.1515, 2003-12-07 01:57:52-05:00, dtor_core@ameritech.net
Input: Add reconnect method to atkbd to restore keyboard state
after suspend (to be called from i8042 resume function)
atkbd.c | 46 ++++++++++++++++++++++++++++++++++++++++++++++
1 files changed, 46 insertions(+)
===================================================================
diff -Nru a/drivers/input/keyboard/atkbd.c b/drivers/input/keyboard/atkbd.c
--- a/drivers/input/keyboard/atkbd.c Sun Dec 7 02:18:19 2003
+++ b/drivers/input/keyboard/atkbd.c Sun Dec 7 02:18:19 2003
@@ -686,10 +686,56 @@
printk(KERN_INFO "input: %s on %s\n", atkbd->name, serio->phys);
}
+/*
+ * atkbd_reconnect() tries to restore keyboard into a sane state and is
+ * most likely called on resume.
+ */
+
+static int atkbd_reconnect(struct serio *serio)
+{
+ struct atkbd *atkbd = serio->private;
+ struct serio_dev *dev = serio->dev;
+ int i;
+
+ if (!dev) {
+ printk(KERN_DEBUG "atkbd: reconnect request, but serio is disconnected, ignoring...\n");
+ return -1;
+ }
+
+ if (atkbd->write) {
+ if (atkbd_probe(atkbd))
+ return -1;
+
+ atkbd->set = atkbd_set_3(atkbd);
+ atkbd_enable(atkbd);
+ } else {
+ atkbd->set = 2;
+ atkbd->id = 0xab00;
+ }
+
+ /*
+ * Here we probably should check if the keyboard has the same set that
+ * it had before and bail out if it's different. But this will most likely
+ * cause new keyboard device be created... and for the user it will look
+ * like keyboard is lost
+ */
+
+ if (atkbd->set == 3)
+ memcpy(atkbd->keycode, atkbd_set3_keycode, sizeof(atkbd->keycode));
+ else
+ memcpy(atkbd->keycode, atkbd_set2_keycode, sizeof(atkbd->keycode));
+
+ for (i = 0; i < 512; i++)
+ if (atkbd->keycode[i] && atkbd->keycode[i] < 255)
+ set_bit(atkbd->keycode[i], atkbd->dev.keybit);
+
+ return 0;
+}
static struct serio_dev atkbd_dev = {
.interrupt = atkbd_interrupt,
.connect = atkbd_connect,
+ .reconnect = atkbd_reconnect,
.disconnect = atkbd_disconnect,
.cleanup = atkbd_cleanup,
};
next prev parent reply other threads:[~2003-12-07 7:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-07 7:27 [PATCH 2.6 1/3] Take 2: resume support for i8042 (atkbd & psmouse) Dmitry Torokhov
2003-12-07 7:28 ` Dmitry Torokhov [this message]
2003-12-07 7:29 ` [PATCH 2.6 2/3] " Dmitry Torokhov
2003-12-07 9:28 ` [PATCH 2.6 1/3] " Vojtech Pavlik
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=200312070228.31969.dtor_core@ameritech.net \
--to=dtor_core@ameritech.net \
--cc=bperkins@netspace.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pavel@ucw.cz \
--cc=sziwan@hell.org.pl \
--cc=vojtech@suse.cz \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.