From: Johnson Wang <johnson.wang@mediatek.com>
To: Chanwoo Choi <cwchoi00@gmail.com>, <linux-pm@vger.kernel.org>,
<linux-kernel@vger.kernel.org>
Cc: <mka@chromium.org>, <wenst@chromium.org>,
<jia-wei.chang@mediatek.com>, <andrew-sh.cheng@mediatek.com>,
<hsinyi@chromium.org>, <saravanak@google.com>,
<cw00.choi@samsung.com>, <myungjoo.ham@samsung.com>,
<kyungmin.park@samsung.com>
Subject: Re: [PATCH v3 0/4] PM / devfreq: Add cpu based scaling support to passive governor
Date: Wed, 11 May 2022 13:29:38 +0800 [thread overview]
Message-ID: <3dc832f47406c835ccdb0076edad58c180881134.camel@mediatek.com> (raw)
In-Reply-To: <20220509120337.92472-1-cw00.choi@samsung.com>
On Mon, 2022-05-09 at 21:03 +0900, Chanwoo Choi wrote:
> The devfreq passive governor has already supported the devfreq parent
> device
> for coupling the frequency change if some hardware have the
> constraints
> such as power sharing and so on.
>
> Add cpu based scaling support to passive governor with required-opp
> property.
> It uses the cpufreq notifier to catch the frequency change timing of
> cpufreq
> and get the next frequency according to new cpu frequency by using
> required-opp
> property. It is based on patch[1] and then just code clean-up by
> myself.
>
> Make the common code for both passive_devfreq and passive_cpufreq
> parent type to remove the duplicate code.
>
> [1] [RFC,v2] PM / devfreq: Add cpu based scaling support to
> passive_governor
> - https://lore.kernel.org/patchwork/patch/1101049/
>
> Changes from v2:
> :
> https://urldefense.com/v3/__https://patchwork.kernel.org/project/linux-pm/cover/20220507150145.531864-1-cw00.choi@samsung.com/__;!!CTRNKA9wMg0ARbw!x-hPdV1M41ovWuBCw3cVvayFBaqFZRCtLLqDHeX_iNnzvwmOKQYOVQeD9mBfi7n8okEj$
>
> - Drop the following patch ("PM / devfreq: passive: Update frequency
> when start governor")
> - Move p_data->this initialization into
> cpufreq_passive_regiser_notifier()
>
> Changes from v1:
> :
> https://urldefense.com/v3/__https://patchwork.kernel.org/project/linux-pm/cover/20210617060546.26933-1-cw00.choi@samsung.com/__;!!CTRNKA9wMg0ARbw!x-hPdV1M41ovWuBCw3cVvayFBaqFZRCtLLqDHeX_iNnzvwmOKQYOVQeD9mBfiw3rUNcX$
>
> - Rename cpu_data variable to parent_cpu_data to avoid build fail
> - Use for_each_possible_cpu macro when register cpufreq transition
> notifier
> - Add missing exception handling when
> cpufreq_passive_register_notifier is failed
> - Keep cpufreq_policy for posible cpus instead of NR_CPU in order to
> avoid
> the memory waste when NR_CPU is too high.
> - Add reviewed-by tag of Matthias Kaehlcke for patch1
>
>
> Chanwoo Choi (3):
> PM / devfreq: Export devfreq_get_freq_range symbol within devfreq
> PM / devfreq: passive: Reduce duplicate code when passive_devfreq
> case
> PM / devfreq: passive: Keep cpufreq_policy for possible cpus
>
> Saravana Kannan (1):
> PM / devfreq: Add cpu based scaling support to passive governor
>
> drivers/devfreq/devfreq.c | 20 +-
> drivers/devfreq/governor.h | 27 ++
> drivers/devfreq/governor_passive.c | 400 ++++++++++++++++++++++++---
> --
> include/linux/devfreq.h | 17 +-
> 4 files changed, 387 insertions(+), 77 deletions(-)
>
For this serie:
Tested-by: Johnson Wang <johnson.wang@mediatek.com>
BRs,
Johnson Wang
prev parent reply other threads:[~2022-05-11 5:31 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-09 12:03 Chanwoo Choi
2022-05-09 12:03 ` [PATCH v3 1/4] PM / devfreq: Export devfreq_get_freq_range symbol within devfreq Chanwoo Choi
2022-05-09 12:03 ` [PATCH v3 2/4] PM / devfreq: Add cpu based scaling support to passive governor Chanwoo Choi
2022-05-09 18:01 ` Chanwoo Choi
2022-05-09 12:03 ` [PATCH v3 3/4] PM / devfreq: passive: Reduce duplicate code when passive_devfreq case Chanwoo Choi
2022-05-09 12:03 ` [PATCH v3 4/4] PM / devfreq: passive: Keep cpufreq_policy for possible cpus Chanwoo Choi
2022-05-10 9:00 ` [PATCH v3 0/4] PM / devfreq: Add cpu based scaling support to passive governor Chen-Yu Tsai
2022-05-10 9:08 ` Chanwoo Choi
2022-05-11 5:29 ` Johnson Wang [this message]
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=3dc832f47406c835ccdb0076edad58c180881134.camel@mediatek.com \
--to=johnson.wang@mediatek.com \
--cc=andrew-sh.cheng@mediatek.com \
--cc=cw00.choi@samsung.com \
--cc=cwchoi00@gmail.com \
--cc=hsinyi@chromium.org \
--cc=jia-wei.chang@mediatek.com \
--cc=kyungmin.park@samsung.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=mka@chromium.org \
--cc=myungjoo.ham@samsung.com \
--cc=saravanak@google.com \
--cc=wenst@chromium.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®