From: Lina Iyer <ilina@codeaurora.org>
To: Ulf Hansson <ulf.hansson@linaro.org>
Cc: "Rafael J. Wysocki" <rjw@rjwysocki.net>,
Linux PM <linux-pm@vger.kernel.org>,
linux-arm-msm <linux-arm-msm@vger.kernel.org>
Subject: Re: [PATCH] PM / Domains: allow domain idle states to be disabled
Date: Sun, 27 Dec 2020 19:30:39 -0700 [thread overview]
Message-ID: <X+lDTxDqTS9ik9TR@codeaurora.org> (raw)
In-Reply-To: <CAPDyKFrAV5Af8WVTy==u1-Ak7zrwC+X7bWSRCc_RrwHoTKfVGw@mail.gmail.com>
On Sat, Dec 26 2020 at 05:33 -0700, Ulf Hansson wrote:
>On Fri, 25 Dec 2020 at 02:31, Lina Iyer <ilina@codeaurora.org> wrote:
>>
>> On Tue, Dec 22 2020 at 03:16 -0700, Ulf Hansson wrote:
>> >On Wed, 16 Dec 2020 at 18:51, Lina Iyer <ilina@codeaurora.org> wrote:
>> >>
>> >> In order to debug critical domain and device power issues, it may be
>> >> necessary to disallow certain idle states at runtime. Let the device
>> >> disallow a domain idle state before suspending.The domain governor shall
>> >> check for the 'disabled' flag while determining the domain idle state.
>> >
>> >For debug purposes, you might as well just set a dev PM Qos latency
>> >request that corresponds to the state you want to disable. This will
>> >then prevent the genpd governor from selecting the state.
>> >
>> True, but it will also disable idle states deeper as well. Would like to
>> avoid that.
>
>I see. In any case, I am not so excited about adding an exported genpd
>interface for this that drivers can call, for example.
>
>Then I would rather see a proper debugfs interface, where userspace
>can both see the available states and choose which one to
>disable/enable. Would that work?
>
Sure, that would work. Any recommendations for existing debugfs node
that we can add this to or something new?
--Lina
next prev parent reply other threads:[~2020-12-28 2:31 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-16 17:50 [PATCH] PM / Domains: allow domain idle states to be disabled Lina Iyer
2020-12-22 10:15 ` Ulf Hansson
2020-12-25 1:31 ` Lina Iyer
2020-12-26 12:33 ` Ulf Hansson
2020-12-28 2:30 ` Lina Iyer [this message]
2021-01-08 10:22 ` Ulf Hansson
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=X+lDTxDqTS9ik9TR@codeaurora.org \
--to=ilina@codeaurora.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=rjw@rjwysocki.net \
--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).