From: Sudeep Holla <sudeep.holla@arm.com>
To: Tushar Nimkar <quic_tnimkar@quicinc.com>
Cc: "Rafael J . Wysocki" <rafael@kernel.org>,
Sudeep Holla <sudeep.holla@arm.com>,
Daniel Lezcano <daniel.lezcano@linaro.org>,
Ulf Hansson <ulf.hansson@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, devicetree@vger.kernel.org
Subject: Re: [PATCH 1/2] dt-bindings: arm: idle-states: Add idle-state-disabled property
Date: Fri, 16 Jun 2023 16:39:24 +0100 [thread overview]
Message-ID: <20230616153924.2wtvgr7lvjcul6to@bogus> (raw)
In-Reply-To: <5820345a-4207-3b12-87eb-098bac4ef4e8@quicinc.com>
On Fri, Jun 16, 2023 at 11:26:18AM +0530, Tushar Nimkar wrote:
>
> Thanks for review Sundeep,
>
> On 6/15/2023 2:26 PM, Sudeep Holla wrote:
> > On Thu, Jun 08, 2023 at 02:25:42PM +0530, Tushar Nimkar wrote:
> > > + 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
> > > +
> >
> > This is clearly a policy and not a hardware or firmware feature to expose
> > in the device tree. So NACK, why can't you load it modules if you don't want
> > idle states in the boot.
> >
> Attempt of making cpuidle governors to modular was rejected in past [2]
>
OK try command line approach to disable all states(you can't get partial
on/off in that case). I don't think the build config is of any use as we
end up enabling it which will affect other platforms.
> [2] https://lore.kernel.org/lkml/1637830481-21709-1-git-send-email-quic_mkshah@quicinc.com/#t
>
> > It is same as choosing any default governor or performance states, will you
> > add those next ? It is simply policy not a feature/property to be exposed
> > in the device tree.
> >
The above still holds, so still NACK. It is a policy and not a
hardware/firmware property or feature.
--
Regards,
Sudeep
next prev parent reply other threads:[~2023-06-16 15:39 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 [this message]
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
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=20230616153924.2wtvgr7lvjcul6to@bogus \
--to=sudeep.holla@arm.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=quic_tnimkar@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