From: Chanwoo Choi <cwchoi00@gmail.com>
To: Christian Marangi <ansuelsmth@gmail.com>,
MyungJoo Ham <myungjoo.ham@samsung.com>,
Kyungmin Park <kyungmin.park@samsung.com>,
Chanwoo Choi <cw00.choi@samsung.com>,
Sibi Sankar <sibis@codeaurora.org>,
Saravana Kannan <skannan@codeaurora.org>,
linux-pm@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] PM / devfreq: Fix kernel warning with cpufreq passive register fail
Date: Thu, 30 Jun 2022 06:33:04 +0900 [thread overview]
Message-ID: <6256a27e-58fc-1c72-be93-f203feb79b0a@gmail.com> (raw)
In-Reply-To: <20220619222939.32029-1-ansuelsmth@gmail.com>
On 22. 6. 20. 07:29, Christian Marangi wrote:
> Remove cpufreq_passive_unregister_notifier from
> cpufreq_passive_register_notifier in case of error as devfreq core
> already call unregister on GOV_START fail.
>
> This fix the kernel always printing a WARN on governor PROBE_DEFER as
> cpufreq_passive_unregister_notifier is called two times and return
> error on the second call as the cpufreq is already unregistered.
>
> Fixes: a03dacb0316f ("PM / devfreq: Add cpu based scaling support to passive governor")
> Signed-off-by: Christian Marangi <ansuelsmth@gmail.com>
> ---
> drivers/devfreq/governor_passive.c | 1 -
> 1 file changed, 1 deletion(-)
>
> diff --git a/drivers/devfreq/governor_passive.c b/drivers/devfreq/governor_passive.c
> index 72c67979ebe1..8055801cf182 100644
> --- a/drivers/devfreq/governor_passive.c
> +++ b/drivers/devfreq/governor_passive.c
> @@ -336,7 +336,6 @@ static int cpufreq_passive_register_notifier(struct devfreq *devfreq)
> err_put_policy:
> cpufreq_cpu_put(policy);
> err:
> - WARN_ON(cpufreq_passive_unregister_notifier(devfreq));
>
> return ret;
> }
Applied. Thanks.
--
Best Regards,
Samsung Electronics
Chanwoo Choi
prev parent reply other threads:[~2022-06-29 21:33 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-19 22:29 Christian Marangi
2022-06-29 21:33 ` Chanwoo Choi [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=6256a27e-58fc-1c72-be93-f203feb79b0a@gmail.com \
--to=cwchoi00@gmail.com \
--cc=ansuelsmth@gmail.com \
--cc=cw00.choi@samsung.com \
--cc=kyungmin.park@samsung.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=myungjoo.ham@samsung.com \
--cc=sibis@codeaurora.org \
--cc=skannan@codeaurora.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®