[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <4BE37DDD.8000402@cox.net>
Date: Thu, 06 May 2010 22:41:33 -0400
From: James Kosin <james.kosin.04@....edu>
To: linux-kernel@...r.kernel.org
Subject: Re: [linux-pm] [PATCH 1/8] PM: Add suspend block api.
On 5/5/2010 8:10 PM, Tony Lindgren wrote:
> * Brian Swetland <swetland@...gle.com> [100505 16:51]:
>> On Wed, May 5, 2010 at 4:47 PM, Tony Lindgren <tony@...mide.com> wrote:
>>> * Brian Swetland <swetland@...gle.com> [100505 14:34]:
>>>> On Wed, May 5, 2010 at 2:12 PM, Alan Stern <stern@...land.harvard.edu> wrote:
<<-- snip -->>
>>>>> At no point does the user program have to communicate anything to the
>>>>> modem driver, and at no point does it have to do anything out of the
>>>>> ordinary except to enable and disable a suspend blocker.
>>>>
>>>> Exactly -- and you can use the same style of overlapping suspend
>>>> blockers with other drivers than input, if the input interface is not
>>>> suitable for the particular interaction.
>>>
>>> Would the suspend blockers still be needed somewhere in the example
>>> above?
>>
>> How often would we retry suspending?
>
> Well based on some timer, the same way the screen blanks? Or five
> seconds of no audio play? So if the suspend fails, then reset whatever
> userspace suspend policy timers.
>
Tony,
Wouldn't this be handled by the idle task, or task manager?
When all tasks are suspended and not doing anything that should be the
first clue that a real suspend cycle could be attempted.
James
--
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