From: Dmitry Torokhov <dtor_core@ameritech.net>
To: Vojtech Pavlik <vojtech@suse.cz>
Cc: akpm@osdl.org, petero2@telia.com, linux-kernel@vger.kernel.org
Subject: 2.6: New set of input patches
Date: Tue, 30 Sep 2003 01:24:15 -0500 [thread overview]
Message-ID: <200309300052.49908.dtor_core@ameritech.net> (raw)
Hi Vojtech,
I have a bunch of input patches that work quite nicely on my laptop,
would you please consider taking them?
1. SERIO: rename serio_{register|unregister}_slave_port to
__serio_{register|unregister}_port to better follow
locked/lockless naming convention.
2. SERIO: There is a possibility that serio might get deleted while there
are outstanding events involving that serio waiting for kseriod
to process them. Invalidate them so kseriod thread will just
drop dead events. (Resend)
3. Input: Introduce an optional blacklist field in input_handler structure.
When loading a new device or a new handler try to match device
against handler's black list before doing match on required
attributes.
This allows to get rid of "surprises" in connect functions, IMO
connect should only fail when it physically can not connect, not
because it decides it does not like device.
4. Input: Synaptics code cleanup and credit update. The switch in
synaptics_process_packet() was quite ugly.
5. SERIO: serio_reconnect added. Similar to serio_rescan but gives driver
a chance to re-initialize keeping the same input device. (Resend)
6. Input/Synaptics:
- Support for pass-through port moved from Synaptics driver to psmouse
itself, it is cleaner and should allow using it in other drivers if
needed.
- The driver makes use of new reconnect functionality in serio. It will
try to keep the same input device after resume or when it resets itself.
- If mouse is disconnected or other mouse plugged in while sleeping the
driver should correctly recognize that and create a new serio/input
device. (Resend, original patch split into 2 - #4 & #6)
Dmitry
next reply other threads:[~2003-09-30 6:32 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-30 6:24 Dmitry Torokhov [this message]
2003-09-30 6:06 ` [PATCH 1/6] serio: rename serio_[un]register_slave_port to __serio_[un]register_port Dmitry Torokhov
2003-09-30 6:15 ` [PATCH 2/6] serio: possible race between port removal and kseriod Dmitry Torokhov
2003-09-30 6:15 ` [PATCH 3/6] Add black list to handler<->device matching Dmitry Torokhov
2003-09-30 6:20 ` [PATCH 4/6] Synaptics: code cleanup Dmitry Torokhov
2003-09-30 6:23 ` [PATCH 5/6] serio: reconnect facility Dmitry Torokhov
2003-09-30 6:27 ` [PATCH 6/6] Synaptics: use serio_reconnect Dmitry Torokhov
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=200309300052.49908.dtor_core@ameritech.net \
--to=dtor_core@ameritech.net \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=petero2@telia.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox