From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: Patrick Mochel <mochel@digitalimplant.org>
Cc: David Brownell <david-b@pacbell.net>,
Alan Stern <stern@rowland.harvard.edu>,
Kernel development list <linux-kernel@vger.kernel.org>
Subject: Re: klists and struct device semaphores
Date: Thu, 31 Mar 2005 14:08:36 -0500 [thread overview]
Message-ID: <d120d50005033111084a8a6f37@mail.gmail.com> (raw)
In-Reply-To: <Pine.LNX.4.50.0503311021040.7249-100000@monsoon.he.net>
On Thu, 31 Mar 2005 10:26:36 -0800 (PST), Patrick Mochel
<mochel@digitalimplant.org> wrote:
> I don't understand what you mean. Even if a device is suspended, be it
> automatically after some amount of inactivity or as directed explicitly by
> a user, we want to be able to open the device and have it work.
>
> Conversely, we only want to automatically suspend the device, or allow the
> device to be explicitly put to sleep, if the device is not being used.
Well, the disagreement in definition of "being used". Quite often you
have a device "open" for extended period of time (inactive ext2
partition is mounted on a disk) but device is not really active. You
could power it down and only wake up when there is a read or write
request.
It looks like "open" and "close" are terms better suited for class
devices while power management is applied to the "real" devices.
--
Dmitry
next prev parent reply other threads:[~2005-03-31 19:08 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-26 16:53 klists and struct device semaphores Alan Stern
2005-03-28 16:56 ` Patrick Mochel
2005-03-28 19:48 ` Alan Stern
2005-03-29 16:38 ` Patrick Mochel
2005-03-28 17:44 ` Patrick Mochel
2005-03-28 18:16 ` David Brownell
2005-03-28 18:43 ` Patrick Mochel
2005-03-28 21:58 ` Alan Stern
2005-03-31 2:12 ` Patrick Mochel
2005-03-31 16:18 ` Alan Stern
2005-03-31 17:59 ` Patrick Mochel
2005-03-31 18:18 ` David Brownell
2005-03-31 18:26 ` Patrick Mochel
2005-03-31 18:46 ` David Brownell
2005-03-31 19:08 ` Patrick Mochel
2005-03-31 19:08 ` Dmitry Torokhov [this message]
2005-03-29 16:18 ` Alan Stern
2005-03-29 16:26 ` Dmitry Torokhov
2005-03-31 2:16 ` Patrick Mochel
2005-03-31 3:01 ` Dmitry Torokhov
2005-03-31 5:47 ` Patrick Mochel
2005-03-31 16:24 ` Alan Stern
2005-03-31 18:04 ` Patrick Mochel
2005-03-31 19:49 ` Alan Stern
2005-04-02 18:06 ` Alan Stern
2005-04-06 7:39 ` Patrick Mochel
2005-04-06 19:45 ` Alan Stern
2005-04-07 20:08 ` Patrick Mochel
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=d120d50005033111084a8a6f37@mail.gmail.com \
--to=dmitry.torokhov@gmail.com \
--cc=david-b@pacbell.net \
--cc=dtor_core@ameritech.net \
--cc=linux-kernel@vger.kernel.org \
--cc=mochel@digitalimplant.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 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.