linux-input.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Pavel Machek <pavel@suse.cz>
To: Oliver Neukum <oliver@neukum.org>
Cc: Jiri Kosina <jkosina@suse.cz>,
	linux-input@vger.kernel.org,
	Dmitry Torokhov <dmitry.torokhov@gmail.com>,
	David Brownell <david-b@pacbell.net>,
	Alan Stern <stern@rowland.harvard.edu>,
	"Rafael J. Wysocki" <rjw@sisk.pl>, Jiri Slaby <jslaby@suse.cz>,
	linux-pm@vger.kernel.org
Subject: Re: proposal on runtime power management in hid
Date: Sat, 1 Nov 2008 19:30:24 +0100	[thread overview]
Message-ID: <20081101183024.GA1531@ucw.cz> (raw)
In-Reply-To: <200810311026.29916.oliver@neukum.org>

Hi!

> > I think the simple and working solution would be never suspedning devices 
> > that have interface open through hidraw, unless user explicitly allows 
> > this through respective power/autosuspend setting in sysfs (which will by 
> > default be set to 'off' for HID devices anyway, right?).
> 
> That we already have. That's the simple copout. Do not enable autosuspend
> if you allow hidraw for a device. However, if normal users shall be able to use
> the hidraw device that means that autosuspend can never be enabled for the
> device, as we don't know when someone will use the device.
> 
> For hiddev we can do better, the device is not autosuspended while it is
> open. This allows allowing ordinary users to use the device. Doing so for
> hidraw would require to extended the low level hid API. But not as extensively
> as I suggested.
> 
> But I consider this to be a lost opportunity.
> Currently the ll driver must assume that the device is required to be fully
> operational when it is open. This means different things for ordinary input
> devices and "raw" devices. Raw devices must not be autosuspended when
> open at all. Ordinary devices must be able to process input.
> 
> But that is often overkill. In many situations, for example when a the screen
> saver is running, you only care that a key has been pressed, not which key.
> Drivers can save more power if they know this.


...way more power in some cases. Yes, I'd love to see interface like
that.

-- 
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html

      parent reply	other threads:[~2008-11-01 18:30 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-30 16:03 proposal on runtime power management in hid Oliver Neukum
2008-10-30 17:01 ` Alan Stern
2008-10-30 23:17 ` Jiri Kosina
2008-10-31  9:26   ` Oliver Neukum
     [not found]     ` <d7e40be30810311553s579db3abiea69be2c2f30cf4e@mail.gmail.com>
2008-10-31 23:59       ` Oliver Neukum
2008-11-01 18:30     ` Pavel Machek [this message]

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=20081101183024.GA1531@ucw.cz \
    --to=pavel@suse.cz \
    --cc=david-b@pacbell.net \
    --cc=dmitry.torokhov@gmail.com \
    --cc=jkosina@suse.cz \
    --cc=jslaby@suse.cz \
    --cc=linux-input@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=oliver@neukum.org \
    --cc=rjw@sisk.pl \
    --cc=stern@rowland.harvard.edu \
    /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;
as well as URLs for NNTP newsgroup(s).