From mboxrd@z Thu Jan 1 00:00:00 1970 From: Hannes Reinecke Date: Tue, 14 Jun 2005 08:00:15 +0000 Subject: Re: Input sysbsystema and hotplug Message-Id: <42AE8E8F.5070404@suse.de> List-Id: References: <200506131607.51736.dtor_core@ameritech.net> <42AE8A9E.5040406@suse.de> <200506140252.42306.dtor_core@ameritech.net> In-Reply-To: <200506140252.42306.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: > On Tuesday 14 June 2005 02:43, Hannes Reinecke wrote: >>Dmitry Torokhov wrote: >>> =20 >>Hmm. I don't like it very much as it mixes two different types of >>devices (class devices and subclasses) into one directory. >> >=20 > If one could come up with a good name to group inputX under I think > it will be OK. We'd have XXX, mouse, joystick, event, ... as subclasses > and all class_devices will be on level below. OTOH input_devs are parents > for mice, joysticks etc so they might be on the higher level. >=20 >>I think it's cleaner to have two distinct class device types >>(one for input_dev and one for input). >> >=20 > I actually detest this practice: >=20 > [dtor@core ~]$ ls /sys/class/ > firmware ieee1394 ieee1394_protocol mem pci_bus sound= usb_host > graphics ieee1394_host input misc pcmcia_socket tty = vc > i2c-adapter ieee1394_node input_dev net printer usb > [dtor@core ~]$ >=20 > dtor@anvil ~]$ ls /sys/class/ > cpuid i2c-adapter ieee1394_host input msr printer so= und usb_host > firmware i2c-dev ieee1394_node mem net scsi_device tt= y vc > graphics ieee1394 ieee1394_protocol misc pci_bus scsi_host us= b video4linux > [dtor@anvil ~]$ >=20 > Firewire has 4 classes on the uppper level, I2C, USB, SCSI and Input got > 2 each. It would be much nicer IMHO if we merge them into trees of classes > with poarent class actually defining subsystem. =20 >=20 Correct. And this in indeed a shortcoming of the driver model, as it basically only knows about classes and devices. Maybe it's about time to introduce a subsystem? >>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 ... >> >=20 > We could have parent class define agent/subsystem name for all its childr= en. >=20 Hmm. We probably could. 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