From: Dmitry Torokhov <dtor_core@ameritech.net>
To: linux-kernel@vger.kernel.org
Cc: Andrew Morton <akpm@osdl.org>, Vojtech Pavlik <vojtech@suse.cz>,
vojtech@ucw.cz
Subject: [PATCH 0/11] New set of input patches
Date: Fri, 18 Jun 2004 03:44:46 -0500 [thread overview]
Message-ID: <200406180344.46191.dtor_core@ameritech.net> (raw)
Hi,
Here is my new set of input patches, most important IMHO is serio sysfs
integration. It is not complete in sense that we need add attributes to
individual drivers (like rate and resolution and protocol to psmouse)
and create some platform devices for i8042, q40kbd, etc so serio ports
would have parents. But the core integration is done. Unfortunately I do
not have 90% hardware to test my changes so there could be some problems,
although I tried to compile everything I could.
The patches are against Vojtech's tree and should apply to -mm as well.
01-psmouse-kvm-sync.patch
- when getting partial packet (usually KVM resets mouse from IMPS/2
to bare PS/2 count it in out_of_sync counter so psmouse.resetafter
logic has a chance to reconnect and reestablish proper protocol;
set default value for psmouse.resetafter to 20 (was 0, disabled)
02-psmouse-state-locking.patch
- Acquire underlying serio lock when changing psmouse state to
prevent interrupt handler runniong on us
03-serio-connect-mandatory.patch
- Make serio driviers connect/disconnect methods mandatory as these
methods open/close serio ports and link ports and drivers together
04-serio-rename-1.patch
- Rename serio->driver to serio->port_data as with sysfs integration
driver is not the best name for arbitrary data
05-serio-rename-2.patch
- Rename serio_dev to serio_driver as they are drivers in sysfs sense
06-serio-dynamic-alloc.patch
- Switch from static to dynamic serio port allocation so serio ports
drivers can be freely unloaded even if not all references to ports
are dropped (sysfs req.)
07-serio-no-recursion.patch
- do not do recursive discovery of children ports, needed for sysfs
and generally better for stack
08-serio-sysfs.patch
- sysfs integration. register ports and drivers in driver model, link
them all together.
09-serio-rebind.patch
- allow user to disconnect or rebind serio port by writing appropriate
data to it's sysfs attribute:
echo -n "psmouse" > /sys/bus/serio/devices/serio0/driver
echo -n "none" > /sys/bus/serio/devices/serio0/driver
10-serio-manual-bind.patch
- allow marking some drivers as requiring manual bind (to be used when
driver does not do automatic HW discovery)
11-serio_raw.patch
- raw access to serio data ala 2.4 /dev/psaux
Vojtech, if you like some patches and want to pull any of it drop me a
note and I'll push it on bkbits.
--
Dmitry
next reply other threads:[~2004-06-18 9:06 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-18 8:44 Dmitry Torokhov [this message]
2004-06-18 9:21 ` [PATCH 0/11] New set of input patches Jan-Benedict Glaw
2004-06-18 13:02 ` Dmitry Torokhov
2004-06-18 20:01 ` Jan-Benedict Glaw
-- strict thread matches above, loose matches on Subject: below --
2004-06-18 20:33 Dmitry Torokhov
2004-06-18 20:52 ` Jan-Benedict Glaw
2004-06-19 20:05 ` Jan-Benedict Glaw
2004-06-20 3:17 ` 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=200406180344.46191.dtor_core@ameritech.net \
--to=dtor_core@ameritech.net \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=vojtech@suse.cz \
--cc=vojtech@ucw.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