From: Tushar Nimkar <quic_tnimkar@quicinc.com>
To: "Rafael J . Wysocki" <rafael@kernel.org>,
Daniel Lezcano <daniel.lezcano@linaro.org>,
Ulf Hansson <ulf.hansson@linaro.org>
Cc: <linux-pm@vger.kernel.org>, <linux-arm-msm@vger.kernel.org>,
<linux-kernel@vger.kernel.org>, <quic_lsrao@quicinc.com>,
<quic_mkshah@quicinc.com>,
Tushar Nimkar <quic_tnimkar@quicinc.com>,
<devicetree@vger.kernel.org>
Subject: [PATCH 1/2] dt-bindings: cpu: idle-states: Add idle-state-disabled property
Date: Thu, 8 Jun 2023 14:25:43 +0530 [thread overview]
Message-ID: <20230608085544.16211-3-quic_tnimkar@quicinc.com> (raw)
In-Reply-To: <20230608085544.16211-1-quic_tnimkar@quicinc.com>
This change adds idle-state-disabled property using which certain or all
idle-states can be kept disabled during boot-up. Once boot-up is completed
same can be enabled using below command.
echo N > /sys/devices/system/cpu/cpuX/cpuidle/stateX/disable
Cc: devicetree@vger.kernel.org
Signed-off-by: Tushar Nimkar <quic_tnimkar@quicinc.com>
---
Documentation/devicetree/bindings/cpu/idle-states.yaml | 8 ++++++++
1 file changed, 8 insertions(+)
diff --git a/Documentation/devicetree/bindings/cpu/idle-states.yaml b/Documentation/devicetree/bindings/cpu/idle-states.yaml
index b8cc826c9501..f999bc666bbd 100644
--- a/Documentation/devicetree/bindings/cpu/idle-states.yaml
+++ b/Documentation/devicetree/bindings/cpu/idle-states.yaml
@@ -358,6 +358,13 @@ patternProperties:
systems entry-latency-us + exit-latency-us will exceed
wakeup-latency-us by this duration.
+ idle-state-disabled:
+ description: |
+ If present the idle state stays disabled. It can be enabled back from
+ shell using below command.
+ echo N > /sys/devices/system/cpu/cpuX/cpuidle/stateX/disable
+ type: boolean
+
idle-state-name:
$ref: /schemas/types.yaml#/definitions/string
description:
@@ -548,6 +555,7 @@ examples:
CPU_SLEEP_0_0: cpu-sleep-0-0 {
compatible = "arm,idle-state";
local-timer-stop;
+ idle-state-disabled;
arm,psci-suspend-param = <0x0010000>;
entry-latency-us = <250>;
exit-latency-us = <500>;
--
2.17.1
next prev parent reply other threads:[~2023-06-08 8:56 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-08 8:55 [PATCH 0/2] Add provision to keep idle state disabled Tushar Nimkar
2023-06-08 8:55 ` [PATCH 1/2] dt-bindings: arm: idle-states: Add idle-state-disabled property Tushar Nimkar
2023-06-08 9:19 ` Conor Dooley
2023-06-09 4:39 ` Tushar Nimkar
2023-06-09 13:14 ` Krzysztof Kozlowski
2023-06-14 6:45 ` Tushar Nimkar
2023-06-15 8:56 ` Sudeep Holla
2023-06-16 5:56 ` Tushar Nimkar
2023-06-16 15:39 ` Sudeep Holla
2023-06-21 6:27 ` Tushar Nimkar
2023-06-08 8:55 ` Tushar Nimkar [this message]
2023-06-09 13:15 ` [PATCH 1/2] dt-bindings: cpu: " Krzysztof Kozlowski
2023-06-08 8:55 ` [PATCH 2/2] cpuidle: dt: Add support to keep idle state disabled Tushar Nimkar
2023-06-12 10:26 ` [PATCH 0/2] Add provision " Ulf Hansson
2023-06-14 6:43 ` Tushar Nimkar
2023-06-16 10:55 ` Ulf Hansson
2023-06-21 6:21 ` Tushar Nimkar
2023-06-22 13:01 ` Ulf Hansson
2023-06-26 6:44 ` Tushar Nimkar
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=20230608085544.16211-3-quic_tnimkar@quicinc.com \
--to=quic_tnimkar@quicinc.com \
--cc=daniel.lezcano@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=quic_lsrao@quicinc.com \
--cc=quic_mkshah@quicinc.com \
--cc=rafael@kernel.org \
--cc=ulf.hansson@linaro.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).