From: Dmitry Osipenko <digetx@gmail.com>
To: Ulf Hansson <ulf.hansson@linaro.org>,
"Rafael J . Wysocki" <rafael@kernel.org>,
linux-pm@vger.kernel.org
Cc: Kevin Hilman <khilman@kernel.org>,
Alexandre Torgue <alexandre.torgue@foss.st.com>,
Geert Uytterhoeven <geert+renesas@glider.be>,
Rajendra Nayak <rnayak@codeaurora.org>,
Dong Aisheng <aisheng.dong@nxp.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] PM: domains: Prevent power off for parent unless child is in deepest state
Date: Wed, 16 Feb 2022 00:49:50 +0300 [thread overview]
Message-ID: <dd7d0ebd-7bd8-9f2e-e212-5b597ec729d5@gmail.com> (raw)
In-Reply-To: <20220204101657.233723-1-ulf.hansson@linaro.org>
04.02.2022 13:16, Ulf Hansson пишет:
> A PM domain managed by genpd may support multiple idlestates. During
> genpd_power_off() a genpd governor may be asked to select one of the
> idlestates based upon the dev PM QoS constraints, for example.
>
> However, there is a problem with the behaviour around this in genpd. More
> precisely, a parent-domain is allowed to be powered off, no matter of what
> idlestate that has been selected for the child-domain.
>
> So far, we have not received any reports about errors from the current
> behaviour. However, there is an STMicro platform that is being worked on,
> which can't cope with this.
Could you please provide some technical info about why STMicro platform
can't cope with that?
next prev parent reply other threads:[~2022-02-15 21:49 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-04 10:16 [PATCH v2] PM: domains: Prevent power off for parent unless child is in deepest state Ulf Hansson
2022-02-15 21:49 ` Dmitry Osipenko [this message]
2022-02-16 9:45 ` Ulf Hansson
2022-02-17 10:02 ` Dmitry Osipenko
-- strict thread matches above, loose matches on Subject: below --
2022-02-17 12:49 Ulf Hansson
2022-02-17 23:11 ` Dmitry Osipenko
2022-02-28 8:56 ` Ulf Hansson
2022-03-01 14:56 ` Rafael J. Wysocki
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=dd7d0ebd-7bd8-9f2e-e212-5b597ec729d5@gmail.com \
--to=digetx@gmail.com \
--cc=aisheng.dong@nxp.com \
--cc=alexandre.torgue@foss.st.com \
--cc=geert+renesas@glider.be \
--cc=khilman@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=rafael@kernel.org \
--cc=rnayak@codeaurora.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