From: Matthew Garrett <mjg59@srcf.ucam.org>
To: Robert Hancock <hancockr@shaw.ca>
Cc: Alan Stern <stern@rowland.harvard.edu>,
linux-kernel@vger.kernel.org,
linux-pm@lists.linux-foundation.org
Subject: Re: [linux-pm] [PATCH] Remove process freezer from suspend to RAM pathway
Date: Wed, 4 Jul 2007 01:34:24 +0100 [thread overview]
Message-ID: <20070704003424.GA30958@srcf.ucam.org> (raw)
In-Reply-To: <468AE700.7080102@shaw.ca>
On Tue, Jul 03, 2007 at 06:17:04PM -0600, Robert Hancock wrote:
> Matthew Garrett wrote:
> >Leave the process blocked and defer any i/o until after resume. Why does
> >it need to be any more complicated than that?
>
> It gets complicated when this has to be added and TESTED in EVERY
> driver. The implied contract for drivers previously was that their
> device would not get accessed after it was suspended until it had been
> resumed first. This proposed change violates that.
No, that's only ever been true for ACPI systems. It's never been true
elsewhere, and it won't be true for anything implementing any sort of
runtime power management.
> I don't think this sort of handling is something that individual drivers
> should have to deal with (at least not ones that are part of a framework
> like USB, libata, etc.)
I'd agree there. Driver midlayers (where they exist) are the appropriate
place to handle this.
--
Matthew Garrett | mjg59@srcf.ucam.org
next prev parent reply other threads:[~2007-07-04 0:35 UTC|newest]
Thread overview: 62+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <fa.ftLWBLCc+XqdYjiuxoPg+qyuUOE@ifi.uio.no>
[not found] ` <fa.Oxrm8HYXTOF4jv5LrTjEe16lCE0@ifi.uio.no>
[not found] ` <fa.d3GOse+YbAb42uYwLymWkJiH9Fw@ifi.uio.no>
2007-07-04 0:17 ` [linux-pm] [PATCH] Remove process freezer from suspend to RAM pathway Robert Hancock
2007-07-04 0:34 ` Matthew Garrett [this message]
2007-07-04 10:21 ` Rafael J. Wysocki
2007-07-03 4:29 Matthew Garrett
2007-07-03 5:49 ` [linux-pm] " Benjamin Herrenschmidt
2007-07-03 13:07 ` Rafael J. Wysocki
2007-07-03 16:03 ` Alan Stern
2007-07-03 16:05 ` Matthew Garrett
2007-07-03 16:57 ` Alan Stern
2007-07-03 17:02 ` Matthew Garrett
2007-07-03 19:33 ` Alan Stern
2007-07-03 19:42 ` Matthew Garrett
2007-07-03 19:54 ` Alan Stern
2007-07-03 20:23 ` Matthew Garrett
2007-07-03 21:10 ` Alan Stern
2007-07-03 21:12 ` Matthew Garrett
2007-07-03 21:16 ` Alan Stern
2007-07-03 21:20 ` Matthew Garrett
2007-07-03 21:37 ` Rafael J. Wysocki
2007-07-03 21:36 ` Matthew Garrett
2007-07-03 21:47 ` Oliver Neukum
2007-07-03 22:46 ` Rafael J. Wysocki
2007-07-04 3:38 ` Paul Mackerras
2007-07-04 10:42 ` Rafael J. Wysocki
2007-07-04 10:58 ` Paul Mackerras
2007-07-04 11:25 ` Rafael J. Wysocki
2007-07-04 11:34 ` Paul Mackerras
2007-07-04 14:12 ` Dmitry Torokhov
2007-07-04 15:38 ` Alan Stern
2007-07-04 19:07 ` Alan Stern
2007-07-04 11:51 ` Miklos Szeredi
2007-07-04 14:41 ` Rafael J. Wysocki
2007-07-04 14:45 ` Miklos Szeredi
2007-07-04 15:03 ` Oliver Neukum
2007-07-04 15:17 ` Rafael J. Wysocki
2007-07-05 0:29 ` Paul Mackerras
2007-07-05 12:29 ` Rafael J. Wysocki
2007-07-12 15:13 ` Pavel Machek
2007-07-04 15:42 ` Alan Stern
2007-07-04 19:25 ` Miklos Szeredi
2007-07-04 21:36 ` Rafael J. Wysocki
2007-07-05 8:37 ` Miklos Szeredi
2007-07-05 12:39 ` Rafael J. Wysocki
2007-07-05 12:39 ` Miklos Szeredi
2007-07-05 16:10 ` Jeremy Fitzhardinge
2007-07-05 17:45 ` Miklos Szeredi
2007-07-05 0:43 ` Paul Mackerras
2007-07-05 12:49 ` Rafael J. Wysocki
2007-07-05 0:36 ` Paul Mackerras
2007-07-05 12:51 ` Rafael J. Wysocki
2007-07-05 12:50 ` Johannes Berg
2007-07-05 13:47 ` Rafael J. Wysocki
2007-07-05 14:25 ` Alan Stern
2007-07-05 17:42 ` Miklos Szeredi
2007-07-05 20:43 ` Alan Stern
2007-07-04 12:41 ` Theodore Tso
2007-07-04 14:40 ` Rafael J. Wysocki
2007-07-03 22:21 ` Alan Stern
2007-07-03 22:42 ` Matthew Garrett
2007-07-04 14:38 ` Alan Stern
2007-07-04 14:58 ` Matthew Garrett
2007-07-04 15:02 ` Oliver Neukum
2007-07-04 15:57 ` Alan Stern
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=20070704003424.GA30958@srcf.ucam.org \
--to=mjg59@srcf.ucam.org \
--cc=hancockr@shaw.ca \
--cc=linux-kernel@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