From: Pavel Machek <pavel@suse.cz>
To: Greg KH <greg@kroah.com>
Cc: Hanna Linder <hannal@us.ibm.com>,
linux-kernel@vger.kernel.org, mochel@osdl.org
Subject: Re: [RFT/C 2.5.70] Input class hook up to driver model/sysfs
Date: Fri, 6 Jun 2003 00:07:16 +0200 [thread overview]
Message-ID: <20030605220716.GF608@elf.ucw.cz> (raw)
In-Reply-To: <20030605211713.GB7029@kroah.com>
Hi!
> > > I did this once before but due to some infrastructure changes
> > > it had to be written again. Here it is, pretty simple. Now
> > > you can see your input devices (except keyboard) listed under
> > > /sys/class/input like this (yes, I do have two mice attached).
> > > At the moment the dev file is created and it contains the
> > > hex value of the major and minor number.
> >
> > *very* nice, and urgently needed for suspend/resume support.
>
> No, classes have nothing to do with suspend/resume, that's devices.
> > But should not structure be /bus/sys/keyboard_controller/mouse0? Mouse
> > needs to be suspended before keyboard controller...
>
> Yes, but this patch is putting stuff in /sys/class/input, not /sys/bus
> :)
Okay, that means that another patch is needed to create hierarchy for
power managment... This sysfs stuff is getting hairy.
Pavel
--
When do you have a heart between your knees?
[Johanka's followup: and *two* hearts?]
next prev parent reply other threads:[~2003-06-05 21:55 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-28 1:04 [RFT/C 2.5.70] Input class hook up to driver model/sysfs Hanna Linder
2003-05-28 23:11 ` Hanna Linder
2003-05-29 7:30 ` Greg KH
2003-05-29 9:30 ` Christoph Hellwig
2003-06-05 21:12 ` Pavel Machek
2003-06-05 21:17 ` Greg KH
2003-06-05 22:07 ` Pavel Machek [this message]
2003-06-05 22:12 ` Patrick Mochel
2003-06-05 22:45 ` Pavel Machek
2003-06-05 22:56 ` Andrew Morton
2003-06-05 23:41 ` viro
2003-06-06 0:03 ` Hanna Linder
2003-06-05 22:16 ` Greg KH
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=20030605220716.GF608@elf.ucw.cz \
--to=pavel@suse.cz \
--cc=greg@kroah.com \
--cc=hannal@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mochel@osdl.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.