From: "Fu, Zhonghui" <zhonghui.fu@linux.intel.com>
To: "Rafael J. Wysocki" <rjw@rjwysocki.net>,
len.brown@intel.com, pavel@ucw.cz,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
linux-pm@vger.kernel.org,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] PM/Trace: get rid of synchronous resume limit during PM trace
Date: Mon, 26 Jan 2015 15:59:59 +0800 [thread overview]
Message-ID: <54C5F3FF.6030600@linux.intel.com> (raw)
In-Reply-To: <54C5CB77.4000109@linux.intel.com>
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 <zhonghui.fu@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
> 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.
>
> Signed-off-by: Zhonghui Fu <zhonghui.fu@linux.intel.com>
> ---
> drivers/base/power/main.c | 3 +--
> include/linux/resume-trace.h | 7 -------
> 2 files changed, 1 insertions(+), 9 deletions(-)
>
> diff --git a/drivers/base/power/main.c b/drivers/base/power/main.c
> index 9717d5f..5df148b 100644
> --- a/drivers/base/power/main.c
> +++ b/drivers/base/power/main.c
> @@ -517,8 +517,7 @@ static int device_resume_noirq(struct device *dev, pm_message_t state, bool asyn
>
> static bool is_async(struct device *dev)
> {
> - return dev->power.async_suspend && pm_async_enabled
> - && !pm_trace_is_enabled();
> + return dev->power.async_suspend && pm_async_enabled;
> }
>
> static void async_resume_noirq(void *data, async_cookie_t cookie)
> diff --git a/include/linux/resume-trace.h b/include/linux/resume-trace.h
> index f31db23..fd0866e 100644
> --- a/include/linux/resume-trace.h
> +++ b/include/linux/resume-trace.h
> @@ -7,11 +7,6 @@
>
> extern int pm_trace_enabled;
>
> -static inline int pm_trace_is_enabled(void)
> -{
> - return pm_trace_enabled;
> -}
> -
> struct device;
> extern void set_trace_device(struct device *);
> extern void generate_resume_trace(const void *tracedata, unsigned int user);
> @@ -24,8 +19,6 @@ extern int show_trace_dev_match(char *buf, size_t size);
>
> #else
>
> -static inline int pm_trace_is_enabled(void) { return 0; }
> -
> #define TRACE_DEVICE(dev) do { } while (0)
> #define TRACE_RESUME(dev) do { } while (0)
>
> -- 1.7.1
>
next prev parent reply other threads:[~2015-01-26 7:59 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-26 5:07 [PATCH] PM/Trace: get rid of synchronous resume limit during PM trace Fu, Zhonghui
2015-01-26 7:59 ` Fu, Zhonghui [this message]
2015-01-26 13:44 ` Rafael J. Wysocki
2015-01-26 10:23 ` Change behaviour when tracing ... nasty trap (was Re: [PATCH] PM/Trace: get rid of synchronous resume limit during PM trace) Pavel Machek
2015-01-26 10:39 ` Liu, Chuansheng
2015-01-26 11:05 ` Pavel Machek
2015-01-26 13:41 ` Rafael J. Wysocki
2015-01-26 13:43 ` Pavel Machek
2015-01-30 0:53 ` Rafael J. Wysocki
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=54C5F3FF.6030600@linux.intel.com \
--to=zhonghui.fu@linux.intel.com \
--cc=gregkh@linuxfoundation.org \
--cc=len.brown@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=pavel@ucw.cz \
--cc=rjw@rjwysocki.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.