linux-pm.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Chanwoo Choi <cwchoi00@gmail.com>
To: Dmitry Osipenko <digetx@gmail.com>,
	Thierry Reding <thierry.reding@gmail.com>,
	Jonathan Hunter <jonathanh@nvidia.com>,
	Viresh Kumar <vireshk@kernel.org>, Nishanth Menon <nm@ti.com>,
	MyungJoo Ham <myungjoo.ham@samsung.com>,
	Stephen Boyd <sboyd@kernel.org>,
	Kyungmin Park <kyungmin.park@samsung.com>,
	Chanwoo Choi <cw00.choi@samsung.com>
Cc: linux-tegra@vger.kernel.org, linux-kernel@vger.kernel.org,
	linux-pm@vger.kernel.org
Subject: Re: [PATCH v1 4/4] PM / devfreq: tegra30: Check whether clk_round_rate() returns zero rate
Date: Wed, 15 Sep 2021 12:51:11 +0900	[thread overview]
Message-ID: <9fa66405-883a-3653-eb5d-3cd7eee07a0a@gmail.com> (raw)
In-Reply-To: <20210912184458.17995-5-digetx@gmail.com>

Hi,

On 21. 9. 13. 오전 3:44, Dmitry Osipenko wrote:
> EMC clock is always-on and can't be zero. Check whether clk_round_rate()
> returns zero rate and error out if it does. It can return zero if clock
> tree isn't initialized properly.
> 
> Signed-off-by: Dmitry Osipenko <digetx@gmail.com>
> ---
>   drivers/devfreq/tegra30-devfreq.c | 4 ++--
>   1 file changed, 2 insertions(+), 2 deletions(-)
> 
> diff --git a/drivers/devfreq/tegra30-devfreq.c b/drivers/devfreq/tegra30-devfreq.c
> index d83fdc2713ed..65ecf17a36f4 100644
> --- a/drivers/devfreq/tegra30-devfreq.c
> +++ b/drivers/devfreq/tegra30-devfreq.c
> @@ -891,9 +891,9 @@ static int tegra_devfreq_probe(struct platform_device *pdev)
>   		return err;
>   
>   	rate = clk_round_rate(tegra->emc_clock, ULONG_MAX);
> -	if (rate < 0) {
> +	if (rate <= 0) {
>   		dev_err(&pdev->dev, "Failed to round clock rate: %ld\n", rate);
> -		return rate;
> +		return rate ?: -EINVAL;
>   	}
>   
>   	tegra->max_freq = rate / KHZ;
> 

Acked-by: Chanwoo Choi <cw00.choi@samsung.com>

-- 
Best Regards,
Samsung Electronics
Chanwoo Choi

  reply	other threads:[~2021-09-15  3:51 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-12 18:44 [PATCH v1 0/4] Make probe() of Tegra devfreq driver completely resource-managed Dmitry Osipenko
2021-09-12 18:44 ` [PATCH v1 1/4] opp: Add more resource-managed variants of dev_pm_opp_of_add_table() Dmitry Osipenko
2021-09-12 18:44 ` [PATCH v1 2/4] PM / devfreq: Add devm_devfreq_add_governor() Dmitry Osipenko
2021-09-15 18:23   ` Chanwoo Choi
2021-09-16  1:30     ` Dmitry Osipenko
2021-09-15 18:37   ` Chanwoo Choi
2021-09-16  1:29     ` Dmitry Osipenko
2021-09-12 18:44 ` [PATCH v1 3/4] PM / devfreq: tegra30: Use resource-managed helpers Dmitry Osipenko
2021-09-12 18:44 ` [PATCH v1 4/4] PM / devfreq: tegra30: Check whether clk_round_rate() returns zero rate Dmitry Osipenko
2021-09-15  3:51   ` Chanwoo Choi [this message]
2021-09-15 18:31     ` Chanwoo Choi
2021-09-16  1:28       ` Dmitry Osipenko
2021-09-19  9:43         ` Chanwoo Choi

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=9fa66405-883a-3653-eb5d-3cd7eee07a0a@gmail.com \
    --to=cwchoi00@gmail.com \
    --cc=cw00.choi@samsung.com \
    --cc=digetx@gmail.com \
    --cc=jonathanh@nvidia.com \
    --cc=kyungmin.park@samsung.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=linux-tegra@vger.kernel.org \
    --cc=myungjoo.ham@samsung.com \
    --cc=nm@ti.com \
    --cc=sboyd@kernel.org \
    --cc=thierry.reding@gmail.com \
    --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;
as well as URLs for NNTP newsgroup(s).