[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20111124195703.GA6735@google.com>
Date: Thu, 24 Nov 2011 11:57:03 -0800
From: Tejun Heo <tj@...nel.org>
To: Alan Stern <stern@...land.harvard.edu>
Cc: Lin Ming <ming.m.lin@...el.com>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"linux-ide@...r.kernel.org" <linux-ide@...r.kernel.org>,
"linux-scsi@...r.kernel.org" <linux-scsi@...r.kernel.org>,
"linux-pm@...r.kernel.org" <linux-pm@...r.kernel.org>,
Jeff Garzik <jgarzik@...ox.com>,
"Rafael J. Wysocki" <rjw@...k.pl>,
James Bottomley <JBottomley@...allels.com>,
"Huang, Ying" <ying.huang@...el.com>,
"Zhang, Rui" <rui.zhang@...el.com>
Subject: Re: [PATCH v3 3/6] [SCSI] runtime resume device before system
suspend
Hello,
On Thu, Nov 24, 2011 at 11:36:20AM -0500, Alan Stern wrote:
> I think this email discussion has answered his objection: The only SCSI
> top-level driver implementing runtime suspend is sd, and sd treats
> runtime suspend the same as system sleep. It might be a good idea to
> add a comment with this explanation along with the new code, however.
Hmmm... I see. This shouldn't affect host controller states - we'll
be skipping only the drive PM transitions, right? As long as it's
well documented, I guess it's okay but at the same time I don't think
it's such a big deal to spin up drives when the system is entering
hibernation from runtime powersave. On most systems, they'll need to
be spun up for image dump pretty soon anyway.
Thanks.
--
tejun
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists