From: zhang.lyra@gmail.com
To: "Rafael J . Wysocki" <rjw@rjwysocki.net>,
Daniel Lezcano <daniel.lezcano@linaro.org>,
Rob Herring <robh+dt@kernel.org>,
Mark Rutland <mark.rutland@arm.com>
Cc: linux-pm@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org,
Chunyan Zhang <zhang.lyra@gmail.com>,
Chunyan Zhang <chunyan.zhang@unisoc.com>
Subject: [RFC PATCH v1 0/2] allow idle state to be found as deepest state for s2idle only
Date: Mon, 13 Apr 2020 15:00:12 +0800 [thread overview]
Message-ID: <20200413070014.12960-1-zhang.lyra@gmail.com> (raw)
From: Chunyan Zhang <chunyan.zhang@unisoc.com>
We can add a new c-state to let system suspend enter into the same deep
state as s2ram when using s2idle, but we don't want other cases to use
that c-state, such as play_idle() which would find the deepest state by
invoking find_deepest_state() as well. This patch-set provides users
an option which can restrict c-state to be found as deepest state for
s2idle only.
Chunyan Zhang (2):
cpuidle: allow idle state to be found as deepest state for s2idle only
dt-bindings: arm: Add description to the new property for-s2idle-only
Documentation/devicetree/bindings/arm/idle-states.yaml | 10 +++++++++-
drivers/cpuidle/cpuidle.c | 3 ++-
drivers/cpuidle/dt_idle_states.c | 3 +++
include/linux/cpuidle.h | 1 +
4 files changed, 15 insertions(+), 2 deletions(-)
--
2.20.1
next reply other threads:[~2020-04-13 7:00 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-13 7:00 zhang.lyra [this message]
2020-04-13 7:00 ` [RFC PATCH v1 1/2] cpuidle: allow idle state to be found as deepest state for s2idle only zhang.lyra
2020-04-20 9:36 ` Chunyan Zhang
2020-04-20 11:42 ` Mark Rutland
2020-04-21 7:31 ` Chunyan Zhang
2020-04-13 7:00 ` [RFC PATCH v1 2/2] dt-bindings: arm: Add description to the new property for-s2idle-only zhang.lyra
2020-04-20 11:44 ` Mark Rutland
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=20200413070014.12960-1-zhang.lyra@gmail.com \
--to=zhang.lyra@gmail.com \
--cc=chunyan.zhang@unisoc.com \
--cc=daniel.lezcano@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=rjw@rjwysocki.net \
--cc=robh+dt@kernel.org \
/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).