From: Rajendra Nayak <rnayak@codeaurora.org>
To: Stephen Boyd <swboyd@chromium.org>,
Viresh Kumar <vireshk@kernel.org>, Nishanth Menon <nm@ti.com>,
Stephen Boyd <sboyd@kernel.org>
Cc: linux-kernel@vger.kernel.org, linux-pm@vger.kernel.org
Subject: Re: [PATCH] OPP: Put opp table in dev_pm_opp_set_rate() all the time
Date: Wed, 12 Aug 2020 11:40:16 +0530 [thread overview]
Message-ID: <006c62c2-e946-954b-6f11-2c5ab131d93d@codeaurora.org> (raw)
In-Reply-To: <20200811212836.2531613-1-swboyd@chromium.org>
On 8/12/2020 2:58 AM, Stephen Boyd wrote:
> We get the opp_table pointer at the top of the function and so we should
> put the pointer at the end of the function like all other exit paths
> from this function do.
>
> Cc: Rajendra Nayak <rnayak@codeaurora.org>
> Fixes: aca48b61f963 ("opp: Manage empty OPP tables with clk handle")
> Signed-off-by: Stephen Boyd <swboyd@chromium.org>
Thanks for the fix.
Reviewed-by: Rajendra Nayak <rnayak@codeaurora.org>
> ---
> drivers/opp/core.c | 8 +++++---
> 1 file changed, 5 insertions(+), 3 deletions(-)
>
> diff --git a/drivers/opp/core.c b/drivers/opp/core.c
> index 9d7fb45b1786..bdb028c7793d 100644
> --- a/drivers/opp/core.c
> +++ b/drivers/opp/core.c
> @@ -893,8 +893,10 @@ int dev_pm_opp_set_rate(struct device *dev, unsigned long target_freq)
> * have OPP table for the device, while others don't and
> * opp_set_rate() just needs to behave like clk_set_rate().
> */
> - if (!_get_opp_count(opp_table))
> - return 0;
> + if (!_get_opp_count(opp_table)) {
> + ret = 0;
> + goto put_opp_table;
> + }
>
> if (!opp_table->required_opp_tables && !opp_table->regulators &&
> !opp_table->paths) {
> @@ -905,7 +907,7 @@ int dev_pm_opp_set_rate(struct device *dev, unsigned long target_freq)
>
> ret = _set_opp_bw(opp_table, NULL, dev, true);
> if (ret)
> - return ret;
> + goto put_opp_table;
>
> if (opp_table->regulator_enabled) {
> regulator_disable(opp_table->regulators[0]);
>
--
QUALCOMM INDIA, on behalf of Qualcomm Innovation Center, Inc. is a member
of Code Aurora Forum, hosted by The Linux Foundation
next prev parent reply other threads:[~2020-08-12 6:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-11 21:28 Stephen Boyd
2020-08-12 6:10 ` Rajendra Nayak [this message]
2020-08-12 8:20 ` Viresh Kumar
2020-08-12 8:22 ` Stephen Boyd
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=006c62c2-e946-954b-6f11-2c5ab131d93d@codeaurora.org \
--to=rnayak@codeaurora.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=nm@ti.com \
--cc=sboyd@kernel.org \
--cc=swboyd@chromium.org \
--cc=vireshk@kernel.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®