From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: Alan Stern <stern@rowland.harvard.edu>
Cc: Dmitry Torokhov <dmitry.torokhov@gmail.com>,
"linux-input@vger.kernel.org" <linux-input@vger.kernel.org>,
Linux-pm mailing list <linux-pm@lists.linux-foundation.org>
Subject: Re: [linux-pm] [RFC] input: syfs switches for SKE keypad
Date: Tue, 12 Oct 2010 20:46:46 +0200 [thread overview]
Message-ID: <201010122046.46562.rjw@sisk.pl> (raw)
In-Reply-To: <Pine.LNX.4.44L0.1010111958400.21557-100000@netrider.rowland.org>
On Tuesday, October 12, 2010, Alan Stern wrote:
> On Tue, 12 Oct 2010, Rafael J. Wysocki wrote:
>
> > It seems to me that for some devices it might be more convenient to have
> > an "execute pm_runtime_idle() for this device right now" sysfs trigger
> > (and analogously for resume).
>
> Indeed, or even "execute pm_runtime_suspend()". If the driver uses
> autosuspend then the runtime_idle callback will call
> pm_runtime_autosuspend, which won't do what you want.
>
> > Anyway, please note that the scenario in which the driver detects inactivity
> > and suspends the device in response is not the only one possible. The other
> > one is that the driver is told to suspend the device and then blocks apps
> > wanting to access it until resumed.
>
> But it initiates a resume as soon as an app tries to use the device,
> right? Otherwise you've got a "sticky off", as Dmitry would say.
Yes, that's the "sticky off" thing.
Rafael
next prev parent reply other threads:[~2010-10-12 18:47 UTC|newest]
Thread overview: 55+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-05 16:54 [RFC] input: syfs switches for SKE keypad Sundar R IYER
2010-10-05 17:41 ` Dmitry Torokhov
2010-10-06 8:32 ` Trilok Soni
2010-10-06 8:56 ` Sundar R IYER
2010-10-06 9:48 ` Onkalo Samu
2010-10-06 11:41 ` Trilok Soni
2010-10-06 11:58 ` Sundar R IYER
2010-10-06 15:43 ` Dmitry Torokhov
2010-10-06 16:19 ` [linux-pm] " Alan Stern
2010-10-06 17:18 ` Dmitry Torokhov
2010-10-06 18:19 ` Alan Stern
2010-10-06 18:26 ` Dmitry Torokhov
2010-10-06 18:51 ` Alan Stern
2010-10-06 19:08 ` Rafael J. Wysocki
2010-10-06 20:08 ` Alan Stern
2010-10-09 10:52 ` Rafael J. Wysocki
2010-10-09 22:46 ` Alan Stern
2010-10-09 23:02 ` Rafael J. Wysocki
2010-10-10 20:34 ` Alan Stern
2010-10-10 20:51 ` Dmitry Torokhov
2010-10-10 21:09 ` Alan Stern
2010-10-10 22:24 ` Rafael J. Wysocki
2010-10-11 15:56 ` Alan Stern
2010-10-11 22:33 ` Rafael J. Wysocki
2010-10-12 0:08 ` Alan Stern
2010-10-12 18:46 ` Rafael J. Wysocki [this message]
2010-10-11 3:16 ` Dmitry Torokhov
2010-10-11 16:06 ` Alan Stern
2010-10-11 16:15 ` Dmitry Torokhov
2010-10-11 16:53 ` Alan Stern
2010-10-11 17:07 ` Dmitry Torokhov
2010-10-11 21:54 ` Alan Stern
2010-10-11 22:08 ` Dmitry Torokhov
2010-10-12 7:25 ` Sundar R IYER
2010-10-12 15:34 ` Alan Stern
2010-10-12 15:53 ` Dmitry Torokhov
2010-10-12 17:45 ` Alan Stern
2010-10-12 16:32 ` Sundar R IYER
2010-10-12 17:49 ` Mark Brown
2010-10-12 18:27 ` Alan Stern
2010-10-12 18:30 ` Mark Brown
2010-10-13 6:16 ` Sundar R IYER
2010-10-13 9:57 ` Mark Brown
2010-10-13 14:10 ` Alan Stern
2010-10-13 17:25 ` Sundar
2010-10-13 17:37 ` Alan Stern
2010-10-13 17:42 ` Sundar
2010-10-13 18:00 ` Sundar
2010-10-13 20:26 ` Rafael J. Wysocki
2010-10-14 13:50 ` Alan Stern
2010-10-14 19:00 ` Rafael J. Wysocki
2010-10-15 16:04 ` Sundar
2010-10-13 7:11 ` Pavel Machek
2010-10-13 17:35 ` Ferenc Wagner
2010-10-13 19:20 ` [linux-pm] " Pavel Machek
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=201010122046.46562.rjw@sisk.pl \
--to=rjw@sisk.pl \
--cc=dmitry.torokhov@gmail.com \
--cc=linux-input@vger.kernel.org \
--cc=linux-pm@lists.linux-foundation.org \
--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).