From mboxrd@z Thu Jan 1 00:00:00 1970 From: Hannes Reinecke Date: Tue, 14 Jun 2005 07:43:26 +0000 Subject: Re: Input sysbsystema and hotplug Message-Id: <42AE8A9E.5040406@suse.de> List-Id: References: <200506131607.51736.dtor_core@ameritech.net> In-Reply-To: <200506131607.51736.dtor_core@ameritech.net> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable To: Dmitry Torokhov Cc: linux-hotplug-devel@lists.sourceforge.net, Greg KH , Vojtech Pavlik , Kay Sievers , LKML Dmitry Torokhov wrote: > Hi, >=20 > I am trying to convert input systsem to play nicely with sysfs and I am > having trouble with hotplug agent. The old hotplug mechanism was using > "input" as agent/subsystem name, unfortunately I can't simply use "input" > class because when Greg added class_simple support to input handlers > (evdev, mousedev, joydev, etc) he used that name. So currently stock > kernel gets 2 types of hotplug events (from input core and from input > handlers) with completely different arguments processed by the same > input agent. >=20 > So I guess my question is: is there anyone who uses hotplug events > for input interface devices (as in mouseX, eventX) as opposed to > parent input devices (inputX). If not then I could rename Greg's class > to "input_dev" and my new class to "input" and that will be compatible > with older installations.=20 >=20 > Also, in the long run I would probably want to see something like this: >=20 > /sys/class/input---input0 > | > |-input1 > | > |-input2 > | > |-mouse---mouse0 > | | > | |-mouse1 > | | > | --mice > | > |-event---event0 > | > |-event1 > | > |-event2 >=20 > where inputX are class devices, mouse and event are subclasses of input > class and mouseX and eventX are again class devices. >=20 > Objections, suggestions, etc?=20 > =20 Hmm. I don't like it very much as it mixes two different types of devices (class devices and subclasses) into one directory. I think it's cleaner to have two distinct class device types (one for input_dev and one for input). subclasses for the input class devices are a neat idea; but I fear the hotplug event name will change for each subclass device ('input' will become eg 'mouse'), so we again have to change all hotplug handlers. And I don't see an easy solution for that ... Cheers, Hannes --=20 Dr. Hannes Reinecke hare@suse.de SuSE Linux AG S390 & zSeries Maxfeldstra=DFe 5 +49 911 74053 688 90409 N=FCrnberg http://www.suse.de ------------------------------------------------------- This SF.Net email is sponsored by: NEC IT Guy Games. How far can you shotp= ut a projector? How fast can you ride your desk chair down the office luge tra= ck? If you want to score the big prize, get to know the little guy. =20 Play to win an NEC 61" plasma display: http://www.necitguy.com/?r=20 _______________________________________________ Linux-hotplug-devel mailing list http://linux-hotplug.sourceforge.net Linux-hotplug-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel