linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Chen Yu <yu.c.chen@intel.com>
To: x86@kernel.org
Cc: Thomas Gleixner <tglx@linutronix.de>,
	"Rafael J. Wysocki" <rjw@rjwysocki.net>,
	Len Brown <lenb@kernel.org>, John Stultz <john.stultz@linaro.org>,
	Xunlei Pang <xlpang@redhat.com>,
	linux-pm@vger.kernel.org, rtc-linux@googlegroups.com,
	linux-kernel@vger.kernel.org, Chen Yu <yu.c.chen@intel.com>
Subject: [PATCH 0/2][RFC v6] Ignore bogus sleep time if pm_trace is enabled
Date: Tue,  8 Nov 2016 17:00:10 +0800	[thread overview]
Message-ID: <cover.1478589736.git.yu.c.chen@intel.com> (raw)

This patch set is based on Thomas's previous solution, to bypass
the bogus CMOS-RTC sleep time after resumed, thus to avoid damage
to timekeeping system. The bogus sleep time comes from pm_trace,
which might use CMOS-RTC for debugging purpose.

Meanwhile, a solution to save/restore of CMOS-RTC is also proposed to give
better user experience. 

Chen Yu (2):
  timekeeping: Ignore the bogus sleep time if pm_trace is enabled
  PM / sleep: save/restore RTC time after resumed if pm_trace enabled

 arch/x86/kernel/rtc.c       |  9 +++++++++
 drivers/base/power/trace.c  | 31 +++++++++++++++++++++++++++++++
 drivers/rtc/rtc-cmos.c      |  7 +++++++
 include/linux/mc146818rtc.h |  1 +
 include/linux/pm-trace.h    |  9 ++++++++-
 5 files changed, 56 insertions(+), 1 deletion(-)

-- 
2.7.4

             reply	other threads:[~2016-11-08  8:51 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-08  9:00 Chen Yu [this message]
2016-11-08  9:01 ` [PATCH 1/2][RFC v6] timekeeping: Ignore the bogus sleep time if pm_trace is enabled Chen Yu
2016-11-08 12:50   ` Chen Yu
2016-11-08  9:02 ` [PATCH 2/2][RFC v6] PM / sleep: save/restore RTC time after resumed if pm_trace enabled Chen Yu
2016-11-08 12:43   ` Chen Yu

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=cover.1478589736.git.yu.c.chen@intel.com \
    --to=yu.c.chen@intel.com \
    --cc=john.stultz@linaro.org \
    --cc=lenb@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=rjw@rjwysocki.net \
    --cc=rtc-linux@googlegroups.com \
    --cc=tglx@linutronix.de \
    --cc=x86@kernel.org \
    --cc=xlpang@redhat.com \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).