linux-pm.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: dbasehore@chromium.org
To: linux-kernel@vger.kernel.org
Cc: dbasehore@chromium.org, linux-pm@vger.kernel.org,
	rjw@rjwysocki.net, pavel@ucw.cz, len.brown@intel.com,
	tglx@linutronix.de
Subject: [PATCH 0/5] Add suspend-to-idle validation for Intel SoCs
Date: Wed,  1 Jun 2016 21:33:24 -0700	[thread overview]
Message-ID: <1464842009-21789-1-git-send-email-dbasehore@chromium.org> (raw)

From: Derek Basehore <dbasehore@chromium.org>

This patch set adds support for catching errors when entering freeze
on Intel Skylake SoCs. Support for this can be added to newer SoCs in
later patches.

Verification is done by waking up the CPU once every X (default 10)
seconds to check the residency of S0ix. This can't be verified before
attempting to enter S0ix through mwait, so we have to repeatedly
verify entry into that state. Successfully entering S0ix is no
guarantee that it will be entered on the next attempt, so we have to
schedule another check. This has a minimal power impact of <1% of the
total system power on our systems.

This relies on the recently added patch "platform/x86: Add PMC Driver
for Intel Core SoC"

Derek Basehore (5):
  x86: stub out pmc function
  clockevents: Add timed freeze
  x86, apic: Add timed freeze support
  freeze: Add error reporting
  intel_idle: Add S0ix validation

 arch/x86/include/asm/pmc_core.h |   6 +-
 arch/x86/kernel/apic/apic.c     |  25 +++++-
 drivers/acpi/processor_idle.c   |  10 ++-
 drivers/cpuidle/cpuidle.c       |  31 +++++--
 drivers/idle/intel_idle.c       | 185 +++++++++++++++++++++++++++++++++++++---
 include/linux/clockchips.h      |  10 +++
 include/linux/cpuidle.h         |  10 ++-
 include/linux/suspend.h         |  10 +++
 kernel/power/suspend.c          |  11 ++-
 kernel/time/clockevents.c       | 117 +++++++++++++++++++++++++
 10 files changed, 385 insertions(+), 30 deletions(-)

-- 
2.8.0.rc3.226.g39d4020

             reply	other threads:[~2016-06-02  4:33 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-02  4:33 dbasehore [this message]
2016-06-02  4:33 ` [PATCH 1/5] x86: stub out pmc function dbasehore
2016-06-02  4:33 ` [PATCH 2/5] clockevents: Add timed freeze dbasehore
2016-06-02  4:33 ` [PATCH 3/5] x86, apic: Add timed freeze support dbasehore
2016-06-02  4:33 ` [PATCH 4/5] freeze: Add error reporting dbasehore
2016-06-02  4:33 ` [PATCH 5/5] intel_idle: Add S0ix validation dbasehore
2016-06-02  9:25   ` Peter Zijlstra
2016-06-02 13:23     ` One Thousand Gnomes
2016-06-02 18:31       ` dbasehore .
2016-06-02 18:55       ` dbasehore .
2016-06-02 19:53         ` One Thousand Gnomes
2016-06-02 20:35           ` dbasehore .
2016-06-04 12:22             ` Alan
2016-06-06 21:39               ` dbasehore .
2016-06-07  7:46 ` [PATCH 0/5] Add suspend-to-idle validation for Intel SoCs Pavel Machek
2016-06-08  0:07   ` dbasehore .
2016-06-11 20:31     ` Pavel Machek

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=1464842009-21789-1-git-send-email-dbasehore@chromium.org \
    --to=dbasehore@chromium.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 \
    --cc=tglx@linutronix.de \
    /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).