From: Hannes Reinecke <hare@suse.de>
To: Dmitry Torokhov <dtor_core@ameritech.net>
Cc: linux-hotplug-devel@lists.sourceforge.net,
Greg KH <gregkh@suse.de>, Vojtech Pavlik <vojtech@suse.cz>,
Kay Sievers <kay.sievers@vrfy.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: Input sysbsystema and hotplug
Date: Tue, 14 Jun 2005 09:43:26 +0200 [thread overview]
Message-ID: <42AE8A9E.5040406@suse.de> (raw)
In-Reply-To: <200506131607.51736.dtor_core@ameritech.net>
Dmitry Torokhov wrote:
> 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?
>
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
--
Dr. Hannes Reinecke hare@suse.de
SuSE Linux AG S390 & zSeries
Maxfeldstraße 5 +49 911 74053 688
90409 Nürnberg http://www.suse.de
next prev parent reply other threads:[~2005-06-14 7:44 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200506131607.51736.dtor_core@ameritech.net>
2005-06-13 21:26 ` Input sysbsystema and hotplug Kay Sievers
2005-06-13 21:38 ` Dmitry Torokhov
2005-06-13 22:17 ` Greg KH
2005-06-14 6:14 ` Dmitry Torokhov
2005-06-13 21:58 ` Dmitry Torokhov
2005-06-13 22:05 ` Dmitry Torokhov
2005-06-13 22:15 ` Greg KH
2005-06-14 6:08 ` Dmitry Torokhov
2005-06-13 22:21 ` Kay Sievers
2005-06-14 7:32 ` Hannes Reinecke
2005-06-14 7:42 ` Dmitry Torokhov
2005-06-14 7:47 ` Hannes Reinecke
2005-06-14 7:56 ` Dmitry Torokhov
2005-06-19 14:46 ` David Brownell
2005-06-13 22:16 ` Greg KH
2005-06-14 4:26 ` Dmitry Torokhov
2005-06-14 6:21 ` Jon Smirl
2005-06-14 6:38 ` Greg KH
2005-06-14 13:41 ` Jon Smirl
2005-06-14 15:02 ` Jon Smirl
2005-06-14 18:16 ` Dmitry Torokhov
2005-06-14 7:43 ` Hannes Reinecke [this message]
2005-06-14 7:52 ` Dmitry Torokhov
2005-06-14 8:00 ` Hannes Reinecke
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=42AE8A9E.5040406@suse.de \
--to=hare@suse.de \
--cc=dtor_core@ameritech.net \
--cc=gregkh@suse.de \
--cc=kay.sievers@vrfy.org \
--cc=linux-hotplug-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=vojtech@suse.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