From: Thierry Reding <thierry.reding@gmail.com>
To: Stephen Boyd <sboyd@kernel.org>
Cc: Yang Yingliang <yangyingliang@huawei.com>,
linux-clk@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-tegra@vger.kernel.org, jonathanh@nvidia.com
Subject: Re: [PATCH -next] clk: tegra: tegra124-emc: fix missing clk_disable_unprepare() on error in emc_set_timing()
Date: Wed, 2 Jun 2021 11:06:42 +0200 [thread overview]
Message-ID: <YLdKIqyqaOwlXw9v@orome.fritz.box> (raw)
In-Reply-To: <162262068754.4130789.12258910664512101759@swboyd.mtv.corp.google.com>
[-- Attachment #1: Type: text/plain, Size: 1982 bytes --]
On Wed, Jun 02, 2021 at 12:58:07AM -0700, Stephen Boyd wrote:
> Why does the subject have -next in it?
>
> Quoting Yang Yingliang (2021-05-17 21:42:47)
> > After calling clk_prepare_enable(), clk_disable_unprepare() need
> > be called when prepare_timing_change() failed.
> >
> > Fixes: 2db04f16b589 ("clk: tegra: Add EMC clock driver")
>
> And then the Fixes tag is for a patch that was merged in v4.10?
To be honest, I'm not sure it's worth backporting this. The probability
of this happening is very small and the worst that will happen is that
the parent clock may stay enabled even if it doesn't have to. However,
the parent clock for these is one of pll_p, pll_c or pll_m, all of which
are usually sourced from other peripherals.
Yes, it's nice to fix this, but I don't think it warrants a backport, so
I think I'll just drop the Fixes tag.
> > Reported-by: Hulk Robot <hulkci@huawei.com>
> > Signed-off-by: Yang Yingliang <yangyingliang@huawei.com>
> > ---
> > drivers/clk/tegra/clk-tegra124-emc.c | 4 +++-
> > 1 file changed, 3 insertions(+), 1 deletion(-)
> >
> > diff --git a/drivers/clk/tegra/clk-tegra124-emc.c b/drivers/clk/tegra/clk-tegra124-emc.c
> > index bdf6f4a51617..74c1d894cca8 100644
> > --- a/drivers/clk/tegra/clk-tegra124-emc.c
> > +++ b/drivers/clk/tegra/clk-tegra124-emc.c
> > @@ -249,8 +249,10 @@ static int emc_set_timing(struct tegra_clk_emc *tegra,
> > div = timing->parent_rate / (timing->rate / 2) - 2;
> >
> > err = tegra->prepare_timing_change(emc, timing->rate);
> > - if (err)
> > + if (err) {
> > + clk_disable_unprepare(timing->parent);
> > return err;
> > + }
> >
> > spin_lock_irqsave(tegra->lock, flags);
> >
>
> Looks correct to me. I assume Thierry will pick it up for the next merge
> window.
Yes, I can do that. I've got a couple of minor fixes queued already, so
this will fit right in.
Thierry
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
prev parent reply other threads:[~2021-06-02 9:05 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-18 4:42 [PATCH -next] clk: tegra: tegra124-emc: fix missing clk_disable_unprepare() on error in emc_set_timing() Yang Yingliang
2021-06-02 7:58 ` Stephen Boyd
2021-06-02 9:06 ` Thierry Reding [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=YLdKIqyqaOwlXw9v@orome.fritz.box \
--to=thierry.reding@gmail.com \
--cc=jonathanh@nvidia.com \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=sboyd@kernel.org \
--cc=yangyingliang@huawei.com \
/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).