From mboxrd@z Thu Jan 1 00:00:00 1970 From: Dmitry Torokhov Date: Mon, 13 Jun 2005 21:07:51 +0000 Subject: Input sysbsystema and hotplug Message-Id: <200506131607.51736.dtor_core@ameritech.net> MIME-Version: 1 Content-Type: multipart/mixed; boundary="Boundary-00=_nWfrCD9nVbYwOMX" List-Id: To: linux-hotplug@vger.kernel.org --Boundary-00=_nWfrCD9nVbYwOMX Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit 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 --Boundary-00=_nWfrCD9nVbYwOMX Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: 7bit

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

--Boundary-00=_nWfrCD9nVbYwOMX-- ------------------------------------------------------- This SF.Net email is sponsored by: NEC IT Guy Games. How far can you shotput a projector? How fast can you ride your desk chair down the office luge track? If you want to score the big prize, get to know the little guy. 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