On 22 March 2013 23:04, Kevin Hilman wrote:
> Hi Rajagopal,
>
> Rajagopal Venkat writes:
>
>> Allow device devfreq to be suspend/resume automatically with
>> runtime pm suspend/resume. The devfreq drivers should be least
>> cared when to suspend/resume the devfreq.
>
> That is the "what", but the
Hi Rajagopal,
Rajagopal Venkat writes:
> Allow device devfreq to be suspend/resume automatically with
> runtime pm suspend/resume. The devfreq drivers should be least
> cared when to suspend/resume the devfreq.
That is the "what", but the changelog should also answer the question
"why?".
> pm_
On 21 March 2013 20:32, Alan Stern wrote:
> On Thu, 21 Mar 2013, Rajagopal Venkat wrote:
>
>> Allow device devfreq to be suspend/resume automatically with
>> runtime pm suspend/resume. The devfreq drivers should be least
>> cared when to suspend/resume the devfreq.
>>
>> pm_runtime_suspend(dev) wi
On Thu, 21 Mar 2013, Rajagopal Venkat wrote:
> Allow device devfreq to be suspend/resume automatically with
> runtime pm suspend/resume. The devfreq drivers should be least
> cared when to suspend/resume the devfreq.
>
> pm_runtime_suspend(dev) will first suspend device devfreq(if available)
> be
Allow device devfreq to be suspend/resume automatically with
runtime pm suspend/resume. The devfreq drivers should be least
cared when to suspend/resume the devfreq.
pm_runtime_suspend(dev) will first suspend device devfreq(if available)
before device is suspended from runtime pm core.
pm_runtime
5 matches
Mail list logo