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:
>
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 pa...@ucw.cz
---
On Mon 2015-01-26 14:41:02, Rafael J. Wysocki wrote:
On Monday, January 26, 2015 12:05:16 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:
> > On Mon 2015-01-26 10:39:04, Liu, Chuansheng wrote:
> > > > > @@ -517,8
hui 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
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
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
> 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
> >
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
>
>
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
Document pm_tracing actually affecting suspend in non-trivial way.
Signed-off-by: Pavel Machek pa...@ucw.cz
---
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
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 resume order.
f9c841d1f943d81b5ab0aac7483e794a7f966296 Mon Sep 17 00:00:00 2001
From: Zhonghui Fu zhonghui...@linux.intel.com
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 dependency between devices in some
On Mon 2015-01-26 13:07:03, Fu, Zhonghui wrote:
From f9c841d1f943d81b5ab0aac7483e794a7f966296 Mon Sep 17 00:00:00 2001
From: Zhonghui Fu zhonghui...@linux.intel.com
Date: Mon, 26 Jan 2015 11:27:08 +0800
Subject: [PATCH] PM/Trace: get rid of synchronous resume limit during PM trace
rid of synchronous resume limit during PM trace
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 devices during tracing
PM events
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
From: Zhonghui Fu zhonghui...@linux.intel.com
Date: Mon, 26
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 devices
>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 dependency between devices in some
hardware platforms.
From f9c841d1f943d81b5ab0aac7483e794a7f966296 Mon Sep 17 00:00:00 2001
From: Zhonghui Fu zhonghui...@linux.intel.com
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 dependency between devices in some
18 matches
Mail list logo