From: Dmitry Osipenko <digetx@gmail.com>
To: Ulf Hansson <ulf.hansson@linaro.org>
Cc: "Rafael J . Wysocki" <rafael@kernel.org>,
linux-pm@vger.kernel.org, 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] PM: domains: Prevent power off for parent unless child is in deepest state
Date: Sun, 13 Feb 2022 15:14:15 +0300 [thread overview]
Message-ID: <2656099c-76bc-33a5-3b98-c46858025955@gmail.com> (raw)
In-Reply-To: <CAPDyKFpLX0Jpz-tzYx3-g0YBZZNh6Bw731gQEFQub1SviLGoYg@mail.gmail.com>
07.02.2022 11:43, Ulf Hansson пишет:
>> In general, such changes usually are deferred from being upstreamed
>> until there is a real user, otherwise there is a risk of cluttering the
>> code with unused features. Do you have a time estimation in regards to
>> when STMicro may start to benefit from this change?
> The STMicro folkz are working on it right now, but I can't give you
> any estimates for their work.
>
> Moreover, I think the important point in this regard, is that the
> $subject patch doesn't really hurt anything else, so then what's the
> point of holding this back?
If that work will never pan out, will you remove the unused code?
next prev parent reply other threads:[~2022-02-13 12:14 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-31 11:37 Ulf Hansson
2022-01-31 18:29 ` Dmitry Osipenko
2022-02-04 9:43 ` Ulf Hansson
2022-02-04 19:10 ` Dmitry Osipenko
2022-02-07 8:43 ` Ulf Hansson
2022-02-13 12:14 ` Dmitry Osipenko [this message]
2022-02-14 9:22 ` Ulf Hansson
2022-02-15 21:49 ` Dmitry Osipenko
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=2656099c-76bc-33a5-3b98-c46858025955@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
all inboxes | Powered by JetHome®