On 15 November 2013 23:03, Kevin Hilman wrote:
> Tony Lindgren writes:
>
>> * Nishanth Menon [131115 05:30]:
>>> On 11/15/2013 02:07 AM, Paul Walmsley wrote:
>>> > On Thu, 14 Nov 2013, Nishanth Menon wrote:
>>> >
>>> >> OMAP device hooks around suspend|resume_noirq ensures that hwmod
>>> >>
On 15 November 2013 23:03, Kevin Hilman khil...@linaro.org wrote:
Tony Lindgren t...@atomide.com writes:
* Nishanth Menon n...@ti.com [131115 05:30]:
On 11/15/2013 02:07 AM, Paul Walmsley wrote:
On Thu, 14 Nov 2013, Nishanth Menon wrote:
OMAP device hooks around suspend|resume_noirq
Tony Lindgren writes:
> * Nishanth Menon [131115 05:30]:
>> On 11/15/2013 02:07 AM, Paul Walmsley wrote:
>> > On Thu, 14 Nov 2013, Nishanth Menon wrote:
>> >
>> >> OMAP device hooks around suspend|resume_noirq ensures that hwmod
>> >> devices are forced to idle using omap_device_idle/enable as
On Fri, 15 Nov 2013, Tony Lindgren wrote:
> I can take it unless you have other fixes pending right now.
Ran a quick test with the patch applied on v3.12, results here:
http://www.pwsan.com/omap/testlogs/test_nm_omap_device_fix_v3.12-rc/20131115123132/
No other fixes queued here right now, so:
* Nishanth Menon [131115 05:30]:
> On 11/15/2013 02:07 AM, Paul Walmsley wrote:
> > On Thu, 14 Nov 2013, Nishanth Menon wrote:
> >
> >> OMAP device hooks around suspend|resume_noirq ensures that hwmod
> >> devices are forced to idle using omap_device_idle/enable as part of
> >> the last stage of
On 11/15/2013 02:07 AM, Paul Walmsley wrote:
> On Thu, 14 Nov 2013, Nishanth Menon wrote:
>
>> OMAP device hooks around suspend|resume_noirq ensures that hwmod
>> devices are forced to idle using omap_device_idle/enable as part of
>> the last stage of suspend activity.
>>
>> For a device such as
On Thu, 14 Nov 2013, Nishanth Menon wrote:
> OMAP device hooks around suspend|resume_noirq ensures that hwmod
> devices are forced to idle using omap_device_idle/enable as part of
> the last stage of suspend activity.
>
> For a device such as i2c who uses autosuspend, it is possible to enter
>
On Thu, 14 Nov 2013, Nishanth Menon wrote:
OMAP device hooks around suspend|resume_noirq ensures that hwmod
devices are forced to idle using omap_device_idle/enable as part of
the last stage of suspend activity.
For a device such as i2c who uses autosuspend, it is possible to enter
the
On 11/15/2013 02:07 AM, Paul Walmsley wrote:
On Thu, 14 Nov 2013, Nishanth Menon wrote:
OMAP device hooks around suspend|resume_noirq ensures that hwmod
devices are forced to idle using omap_device_idle/enable as part of
the last stage of suspend activity.
For a device such as i2c who uses
* Nishanth Menon n...@ti.com [131115 05:30]:
On 11/15/2013 02:07 AM, Paul Walmsley wrote:
On Thu, 14 Nov 2013, Nishanth Menon wrote:
OMAP device hooks around suspend|resume_noirq ensures that hwmod
devices are forced to idle using omap_device_idle/enable as part of
the last stage of
On Fri, 15 Nov 2013, Tony Lindgren wrote:
I can take it unless you have other fixes pending right now.
Ran a quick test with the patch applied on v3.12, results here:
http://www.pwsan.com/omap/testlogs/test_nm_omap_device_fix_v3.12-rc/20131115123132/
No other fixes queued here right now, so:
Tony Lindgren t...@atomide.com writes:
* Nishanth Menon n...@ti.com [131115 05:30]:
On 11/15/2013 02:07 AM, Paul Walmsley wrote:
On Thu, 14 Nov 2013, Nishanth Menon wrote:
OMAP device hooks around suspend|resume_noirq ensures that hwmod
devices are forced to idle using
On 11/14/2013 12:55 PM, Felipe Balbi wrote:
> Hi,
>
> On Thu, Nov 14, 2013 at 11:05:16AM -0600, Nishanth Menon wrote:
>> OMAP device hooks around suspend|resume_noirq ensures that hwmod
>> devices are forced to idle using omap_device_idle/enable as part of
>> the last stage of suspend activity.
Hi,
On Thu, Nov 14, 2013 at 11:05:16AM -0600, Nishanth Menon wrote:
> OMAP device hooks around suspend|resume_noirq ensures that hwmod
> devices are forced to idle using omap_device_idle/enable as part of
> the last stage of suspend activity.
>
> For a device such as i2c who uses autosuspend, it
OMAP device hooks around suspend|resume_noirq ensures that hwmod
devices are forced to idle using omap_device_idle/enable as part of
the last stage of suspend activity.
For a device such as i2c who uses autosuspend, it is possible to enter
the suspend path with dev->power.runtime_status =
OMAP device hooks around suspend|resume_noirq ensures that hwmod
devices are forced to idle using omap_device_idle/enable as part of
the last stage of suspend activity.
For a device such as i2c who uses autosuspend, it is possible to enter
the suspend path with dev-power.runtime_status =
Hi,
On Thu, Nov 14, 2013 at 11:05:16AM -0600, Nishanth Menon wrote:
OMAP device hooks around suspend|resume_noirq ensures that hwmod
devices are forced to idle using omap_device_idle/enable as part of
the last stage of suspend activity.
For a device such as i2c who uses autosuspend, it is
On 11/14/2013 12:55 PM, Felipe Balbi wrote:
Hi,
On Thu, Nov 14, 2013 at 11:05:16AM -0600, Nishanth Menon wrote:
OMAP device hooks around suspend|resume_noirq ensures that hwmod
devices are forced to idle using omap_device_idle/enable as part of
the last stage of suspend activity.
For a
18 matches
Mail list logo