public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: Pavel Machek <pavel@ucw.cz>
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: Thu, 5 Jun 2003 14:17:13 -0700	[thread overview]
Message-ID: <20030605211713.GB7029@kroah.com> (raw)
In-Reply-To: <20030605211258.GA705@elf.ucw.cz>

On Thu, Jun 05, 2003 at 11:12:58PM +0200, Pavel Machek wrote:
> 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
:)

thanks,

greg k-h

  reply	other threads:[~2003-06-05 21:06 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 [this message]
2003-06-05 22:07     ` Pavel Machek
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=20030605211713.GB7029@kroah.com \
    --to=greg@kroah.com \
    --cc=hannal@us.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mochel@osdl.org \
    --cc=pavel@ucw.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