From: Tushar Nimkar <quic_tnimkar@quicinc.com>
To: Ulf Hansson <ulf.hansson@linaro.org>
Cc: "Rafael J . Wysocki" <rafael@kernel.org>,
Daniel Lezcano <daniel.lezcano@linaro.org>,
<linux-pm@vger.kernel.org>, <linux-arm-msm@vger.kernel.org>,
<linux-kernel@vger.kernel.org>, <quic_lsrao@quicinc.com>,
<quic_mkshah@quicinc.com>
Subject: Re: [PATCH 0/2] Add provision to keep idle state disabled
Date: Wed, 14 Jun 2023 12:13:19 +0530 [thread overview]
Message-ID: <443b00b1-76b8-c31d-53d3-42e3592d26e8@quicinc.com> (raw)
In-Reply-To: <CAPDyKFqhVkMH42Vz0+a62j5kFh+R_CvGrcSU7hxoW__tjOhfLw@mail.gmail.com>
Thanks for response Ulf.
On 6/12/2023 3:56 PM, Ulf Hansson wrote:
> On Thu, 8 Jun 2023 at 10:56, Tushar Nimkar <quic_tnimkar@quicinc.com> wrote:
>>
>> CPUidle already has CPUIDLE_FLAG_OFF to keep idle state disabled,
>> Lets extend the support to set this flag using device tree.
>>
>> This allows to keep an idle state disabled and they can be enabled back using
>> sysfs after certain point using below command.
>>
>> echo N > /sys/devices/system/cpu/cpuX/cpuidle/stateX/disable
>>
>> This helps in cases where vendors want to keep cpuidle off until home
>> screen comes up. In the past attempt was done at [1] but it was not considered
>> safe option to export cpu_idle_poll_ctrl().
>>
>> [1] https://patchwork.kernel.org/project/linux-arm-msm/patch/1637831676-32737-1-git-send-email-quic_mkshah@quicinc.com/
>
> Before considering this, I don't recall if I ever received a reply to
> my earlier suggestion to the above thread. So, let me repeat my
> question.
>
> I am wondering if a similar improvement can be achieved by
> modularizing the cpuidle-psci driver. If insmodding it after the
> homescreen, we allow only ARM WFI during boot. This should achieve the
> similar results as we get with $subject series, right?
>
> [...]
>
This will not work for targets which does not have DLKM support.
>>
>> Thanks,
>> Tushar Nimkar.
>>
>> Tushar Nimkar (2):
>> dt-bindings: cpu: idle-states: Add idle-state-disabled property
>> cpuidle: dt: Add support to keep idle state disabled
>>
>> Documentation/devicetree/bindings/cpu/idle-states.yaml | 8 ++++++++
>> drivers/cpuidle/dt_idle_states.c | 3 +++
>> 2 files changed, 11 insertions(+)
>>
>
> Kind regards
> Uffe
Thanks,
Tushar
next prev parent reply other threads:[~2023-06-14 6:43 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-08 8:55 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 ` [PATCH 1/2] dt-bindings: cpu: " Tushar Nimkar
2023-06-09 13:15 ` 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 [this message]
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=443b00b1-76b8-c31d-53d3-42e3592d26e8@quicinc.com \
--to=quic_tnimkar@quicinc.com \
--cc=daniel.lezcano@linaro.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
all inboxes | Powered by JetHome®