From: Dmitry Torokhov <dtor_core@ameritech.net>
To: Greg KH <gregkh@suse.de>
Cc: linux-hotplug-devel@lists.sourceforge.net,
Kay Sievers <kay.sievers@vrfy.org>,
Vojtech Pavlik <vojtech@suse.cz>,
LKML <linux-kernel@vger.kernel.org>,
Hannes Reinecke <hare@suse.de>
Subject: Re: Input sysbsystema and hotplug
Date: Tue, 14 Jun 2005 01:14:38 -0500 [thread overview]
Message-ID: <200506140114.39398.dtor_core@ameritech.net> (raw)
In-Reply-To: <20050613221736.GC15381@suse.de>
On Monday 13 June 2005 17:17, Greg KH wrote:
> On Mon, Jun 13, 2005 at 04:38:08PM -0500, Dmitry Torokhov wrote:
> > On Monday 13 June 2005 16:26, Kay Sievers wrote:
> > > On Mon, Jun 13, 2005 at 04:07:51PM -0500, Dmitry Torokhov wrote:
> > > >
> > > > where inputX are class devices, mouse and event are subclasses of input
> > > > class and mouseX and eventX are again class devices.
> > >
> > > We don't support childs of class devices until now. Would be nice maybe, but
> > > someone needs to add that to the driver-core first and we would need to make
> > > a bunch of userspace stuff aware of it ...
> > >
> >
> > Something like patch below will suffice I think (not tested).
>
> No, you need to increment the parent when you register the child. Look
> at the device code for what's needed for this.
>
Don't quite follow what you are saying. If you are saying that it needs
to call class_get(parent) I don't think it's necessary as kobject code
will grab the reference (to class's subsystem kset).
All in all it seems to be working:
[dtor@core ~]$ ls /sys/class/input_dev/
input0 input3 input4 input_dev_subclass
[dtor@core ~]$
--
Dmitry
next prev parent reply other threads:[~2005-06-14 6:14 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 [this message]
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
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=200506140114.39398.dtor_core@ameritech.net \
--to=dtor_core@ameritech.net \
--cc=gregkh@suse.de \
--cc=hare@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