Re: Change behaviour when tracing ... nasty trap (was Re: [PATCH] PM/Trace: get rid of synchronous resume limit during PM trace)

2015-01-29 Thread Rafael J. Wysocki
On Monday, January 26, 2015 02:43:04 PM Pavel Machek wrote: > Document pm_tracing actually affecting suspend in non-trivial way. > > > Signed-off-by: Pavel Machek > > --- > > On Mon 2015-01-26 14:41:02, Rafael J. Wysocki wrote: > > On Monday, January 26, 2015 12:05:16 PM Pavel Machek wrote: >

Re: Change behaviour when tracing ... nasty trap (was Re: [PATCH] PM/Trace: get rid of synchronous resume limit during PM trace)

2015-01-26 Thread Pavel Machek
Document pm_tracing actually affecting suspend in non-trivial way. Signed-off-by: Pavel Machek --- On Mon 2015-01-26 14:41:02, Rafael J. Wysocki wrote: > On Monday, January 26, 2015 12:05:16 PM Pavel Machek wrote: > > On Mon 2015-01-26 10:39:04, Liu, Chuansheng wrote: > > > > > @@ -517,8 +517

Re: [PATCH] PM/Trace: get rid of synchronous resume limit during PM trace

2015-01-26 Thread Rafael J. Wysocki
On Monday, January 26, 2015 03:59:59 PM Fu, Zhonghui wrote: > > This is a incorrect patch , please ignore it. Of course it is incorrect. If it "fixes" anything for you, this means you need to reorder devices in dpm_list on the given system. > On 2015/1/26 13:07, Fu, Zhonghui wrote: > > From f9

Re: Change behaviour when tracing ... nasty trap (was Re: [PATCH] PM/Trace: get rid of synchronous resume limit during PM trace)

2015-01-26 Thread Rafael J. Wysocki
On Monday, January 26, 2015 12:05:16 PM Pavel Machek wrote: > On Mon 2015-01-26 10:39:04, Liu, Chuansheng wrote: > > Hello Pavel, > > > > > > There are some kind of dependency between devices in some > > > > hardware platforms. So, asynchronous resuming devices may > > > > hang system due to wrong

Re: Change behaviour when tracing ... nasty trap (was Re: [PATCH] PM/Trace: get rid of synchronous resume limit during PM trace)

2015-01-26 Thread Pavel Machek
On Mon 2015-01-26 10:39:04, Liu, Chuansheng wrote: > Hello Pavel, > > > > There are some kind of dependency between devices in some > > > hardware platforms. So, asynchronous resuming devices may > > > hang system due to wrong resume order. As a result, should > > > not fore synchronously resuming

RE: Change behaviour when tracing ... nasty trap (was Re: [PATCH] PM/Trace: get rid of synchronous resume limit during PM trace)

2015-01-26 Thread Liu, Chuansheng
> Subject: Change behaviour when tracing ... nasty trap (was Re: [PATCH] > PM/Trace: get rid of synchronous resume limit during PM trace) > > On Mon 2015-01-26 13:07:03, Fu, Zhonghui wrote: > > >From f9c841d1f943d81b5ab0aac7483e794a7f966296 Mon Sep 17 00:00:00 > 2001 > >

Change behaviour when tracing ... nasty trap (was Re: [PATCH] PM/Trace: get rid of synchronous resume limit during PM trace)

2015-01-26 Thread Pavel Machek
On Mon 2015-01-26 13:07:03, Fu, Zhonghui wrote: > >From f9c841d1f943d81b5ab0aac7483e794a7f966296 Mon Sep 17 00:00:00 2001 > From: Zhonghui Fu > Date: Mon, 26 Jan 2015 11:27:08 +0800 > Subject: [PATCH] PM/Trace: get rid of synchronous resume limit during PM trace > > There are some kind of depende

Re: [PATCH] PM/Trace: get rid of synchronous resume limit during PM trace

2015-01-26 Thread Fu, Zhonghui
This is a incorrect patch , please ignore it. Thanks, Zhonghui On 2015/1/26 13:07, Fu, Zhonghui wrote: > From f9c841d1f943d81b5ab0aac7483e794a7f966296 Mon Sep 17 00:00:00 2001 > From: Zhonghui Fu > Date: Mon, 26 Jan 2015 11:27:08 +0800 > Subject: [PATCH] PM/Trace: get rid of synchronous resume