From: Kevin Hilman <khilman@baylibre.com>
To: "shunzhou.jiang@amlogic.com" <shunzhou.jiang@amlogic.com>,
linux-arm-kernel <linux-arm-kernel@lists.infradead.org>,
linux-amlogic <linux-amlogic@lists.infradead.org>,
linux-kernel <linux-kernel@vger.kernel.org>
Cc: Neil Armstrong <narmstrong@baylibre.com>,
jbrunet <jbrunet@baylibre.com>,
Martin Blumenstingl <martin.blumenstingl@googlemail.com>,
"jianxin.pan" <jianxin.pan@amlogic.com>
Subject: Re: Re: [PATCH 2/2] soc: s4: Add support for power domains controller
Date: Fri, 11 Feb 2022 10:52:41 -0800 [thread overview]
Message-ID: <7hwni1me12.fsf@baylibre.com> (raw)
In-Reply-To: <2022021117375354230910@amlogic.com>
Hi Shunzhou,
"shunzhou.jiang@amlogic.com" <shunzhou.jiang@amlogic.com> writes:
> Hi Kevin:
> Thanks your kindly reply
You're welcome. For future reference, please avoid top-posting. See:
https://www.kernel.org/doc/html/latest/process/2.Process.html?highlight=top-posting#mailing-lists
> For those domains, default is active, we hope not close when in use or not in use, in our case,
> only runtime PM (include suspend) control this, so set always on flag to avoid domain shutdown,
my question remains: why do want to keep these powered on even when they
are not in use?
The goal of the power-domain framework + runtime PM is to be able to
save power by turnin off power domains when they are not in use.
> if you also have concern, we can control this not in kernel, but this not our expect.
My strong preference is that this is controlled by the kernel.
Kevin
next prev parent reply other threads:[~2022-02-11 18:52 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-26 6:10 [PATCH 0/2] Power: meson-s4: add s4 power domain driver Shunzhou Jiang
2022-01-26 6:10 ` [PATCH 1/2] dt-bindings: power: add Amlogic s4 power domains bindings Shunzhou Jiang
2022-01-26 6:10 ` [PATCH 2/2] soc: s4: Add support for power domains controller Shunzhou Jiang
2022-02-01 19:52 ` Kevin Hilman
[not found] ` <202202091001287547451@amlogic.com>
2022-02-09 20:30 ` Kevin Hilman
[not found] ` <2022021117375354230910@amlogic.com>
2022-02-11 18:52 ` Kevin Hilman [this message]
[not found] ` <2022021510112070486315@amlogic.com>
2022-02-19 0:32 ` Kevin Hilman
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=7hwni1me12.fsf@baylibre.com \
--to=khilman@baylibre.com \
--cc=jbrunet@baylibre.com \
--cc=jianxin.pan@amlogic.com \
--cc=linux-amlogic@lists.infradead.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=martin.blumenstingl@googlemail.com \
--cc=narmstrong@baylibre.com \
--cc=shunzhou.jiang@amlogic.com \
/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
Powered by JetHome