From: Jon Hunter <jonathanh@nvidia.com>
To: Christophe JAILLET <christophe.jaillet@wanadoo.fr>,
<thierry.reding@gmail.com>, <digetx@gmail.com>,
<ulf.hansson@linaro.org>, <maz@kernel.org>,
<gustavoars@kernel.org>, <jckuo@nvidia.com>
Cc: <linux-tegra@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<kernel-janitors@vger.kernel.org>
Subject: Re: [PATCH] soc/tegra: Fix an error handling path in 'tegra_powergate_power_up()'
Date: Mon, 28 Jun 2021 09:28:27 +0100 [thread overview]
Message-ID: <52f72ce4-a630-af2f-858e-488e4dd7d9cf@nvidia.com> (raw)
In-Reply-To: <46d3af4a83e2e7b680c857e8969167f0d2d94841.1624809134.git.christophe.jaillet@wanadoo.fr>
On 27/06/2021 16:54, Christophe JAILLET wrote:
> If an error occurs after a successful 'tegra_powergate_enable_clocks()'
> call, it must be undone by a 'tegra_powergate_disable_clocks()' call, as
> already done in the below and above error handling paths of this function.
>
> Update the 'goto' to branch at the correct place of the error handling
> path.
>
> Fixes: a38045121bf4 ("soc/tegra: pmc: Add generic PM domain support")
> Signed-off-by: Christophe JAILLET <christophe.jaillet@wanadoo.fr>
> ---
> /!\ This patch is speculative /!\
> Review with care.
> ---
> drivers/soc/tegra/pmc.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/soc/tegra/pmc.c b/drivers/soc/tegra/pmc.c
> index ea62f84d1c8b..b8ef9506f3de 100644
> --- a/drivers/soc/tegra/pmc.c
> +++ b/drivers/soc/tegra/pmc.c
> @@ -782,7 +782,7 @@ static int tegra_powergate_power_up(struct tegra_powergate *pg,
>
> err = reset_control_deassert(pg->reset);
> if (err)
> - goto powergate_off;
> + goto disable_clks;
>
> usleep_range(10, 20);
Thanks for the fix.
Reviewed-by: Jon Hunter <jonathanh@nvidia.com>
Cheers
Jon
--
nvpublic
next prev parent reply other threads:[~2021-06-28 8:28 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-27 15:54 [PATCH] soc/tegra: Fix an error handling path in 'tegra_powergate_power_up()' Christophe JAILLET
2021-06-28 8:28 ` Jon Hunter [this message]
2021-10-07 18:02 ` Thierry Reding
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=52f72ce4-a630-af2f-858e-488e4dd7d9cf@nvidia.com \
--to=jonathanh@nvidia.com \
--cc=christophe.jaillet@wanadoo.fr \
--cc=digetx@gmail.com \
--cc=gustavoars@kernel.org \
--cc=jckuo@nvidia.com \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=maz@kernel.org \
--cc=thierry.reding@gmail.com \
--cc=ulf.hansson@linaro.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