On Sat, Aug 17, 2013 at 7:53 AM, Rafael J. Wysocki wrote:
> On Friday, August 16, 2013 05:13:42 PM Li Yang-R58472 wrote:
>>
>> 在 2013-8-16,下午7:22,"Rafael J. Wysocki" 写道:
>>
>> > On Friday, August 16, 2013 04:06:26 PM Li Yang wrote:
>> >> Hi Guys,
>> >>
>> >> Is there a standard way for the device
On Friday, August 16, 2013 05:13:42 PM Li Yang-R58472 wrote:
>
> 在 2013-8-16,下午7:22,"Rafael J. Wysocki" 写道:
>
> > On Friday, August 16, 2013 04:06:26 PM Li Yang wrote:
> >> Hi Guys,
> >>
> >> Is there a standard way for the device drivers to know if the system
> >> is going to “standby” mode or
在 2013-8-16,下午7:22,"Rafael J. Wysocki" 写道:
> On Friday, August 16, 2013 04:06:26 PM Li Yang wrote:
>> Hi Guys,
>>
>> Is there a standard way for the device drivers to know if the system
>> is going to “standby” mode or “mem” mode when the suspend() callbacks
>> are called?
>
> No, there's non
On Friday, August 16, 2013 04:06:26 PM Li Yang wrote:
> Hi Guys,
>
> Is there a standard way for the device drivers to know if the system
> is going to “standby” mode or “mem” mode when the suspend() callbacks
> are called?
No, there's none.
What do you need that for?
Rafael
--
To unsubscribe
On 08/16/2013 10:06 AM, Li Yang wrote:
Hi Guys,
Is there a standard way for the device drivers to know if the system
is going to “standby” mode or “mem” mode when the suspend() callbacks
are called?
what about implementing struct device_driver::suspend?
This is for driver level suspend operat
5 matches
Mail list logo