Input sysbsystema and hotplug

[Dmitry Torokhov <dtor_core@ameritech.net>]

[-- Attachment #1: Type: text/plain, Size: 1262 bytes --]

Hi,

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.

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. 

Also, in the long run I would probably want to see something like this:

/sys/class/input---input0
		 |
		 |-input1
		 |
		 |-input2
		 |
		 |-mouse---mouse0
		 |	 |
		 |	 |-mouse1
		 |	 |
		 |	 --mice
		 |
		 |-event---event0
			 |
			 |-event1
			 |
			 |-event2

where inputX are class devices, mouse and event are subclasses of input
class and mouseX and eventX are again class devices.

Objections, suggestions, etc? 
	 
Thank you!

-- 
Dmitry

[-- Attachment #2: Type: text/html, Size: 1747 bytes --]