[<prev] [next>] [day] [month] [year] [list]
Message-ID: <59qes3i0orxy6yfyqhf7q34x.1264348598355@email.android.com>
Date: Sun, 24 Jan 2010 07:56:38 -0800
From: Jesse Barnes <jbarnes@...tuousgeek.org>
To: "Rafael J. Wysocki" <rjw@...k.pl>,
Alan Stern <stern@...land.harvard.edu>
Cc: pm list <linux-pm@...ts.linux-foundation.org>,
LKML <linux-kernel@...r.kernel.org>,
Matthew Garrett <mjg59@...f.ucam.org>, Greg KH <greg@...ah.com>
Subject: Re: [PATCH 1/2] PM / Runtime: Add sysfs switch for disabling device
run-time PM (rev. 2)
"Rafael J. Wysocki" <rjw@...k.pl> wrote:
>On Saturday 23 January 2010, Alan Stern wrote:
>> On Sat, 23 Jan 2010, Rafael J. Wysocki wrote:
>>
>> > Hmm, OK.
>> >
>> > Of course, if the driver decides to leave disable_depth > 0, the user still
>> > won't be able to do anything about that, but if I understand correctly, you
>> > want drivers to have the option to use pm_runtime_forbid() initially, right
>> > after pm_runtime_enable(), so that the user space can turn the runtime PM
>> > on if desired via sysfs.
>> >
>> > That makes sense. I have a usage case for that myself. :-)
>> >
>> > Updated patch is appended.
>>
>> It looks good.
>>
>> Acked-by: Alan Stern <stern@...land.harvard.edu>
>
>Thanks!
>
>Rafael
>
Powered by blists - more mailing lists