From: Lukasz Luba <lukasz.luba@arm.com>
To: Jiawen Liu <1298662399@qq.com>
Cc: Alim Akhtar <alim.akhtar@samsung.com>,
linux-pm@vger.kernel.org,
Peter Griffin <peter.griffin@linaro.org>,
Krzysztof Kozlowski <krzk@kernel.org>,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, linux-samsung-soc@vger.kernel.org
Subject: Re: [PATCH] memory: exynos5422-dmc: handle clock enable failures
Date: Fri, 4 Sep 2026 09:14:15 +0100 [thread overview]
Message-ID: <92153d54-e7aa-4fe3-8317-0060b4078d6c@arm.com> (raw)
In-Reply-To: <tencent_405FF24AB67AAAA26BC85ADD092710C0BB07@qq.com>
On 8/18/26 14:19, Jiawen Liu wrote:
> Check clock-enable failures during probe.
>
> If a later clock cannot be enabled, unwind clocks already enabled on
> that path before returning the error.
>
> Signed-off-by: jiawen <1298662399@qq.com>
> ---
> diff --git a/drivers/memory/samsung/exynos5422-dmc.c b/drivers/memory/samsung/exynos5422-dmc.c
> --- a/drivers/memory/samsung/exynos5422-dmc.c
> +++ b/drivers/memory/samsung/exynos5422-dmc.c
> @@ -1297,8 +1297,15 @@
> if (ret)
> return ret;
>
> - clk_prepare_enable(dmc->fout_bpll);
> - clk_prepare_enable(dmc->mout_bpll);
> + ret = clk_prepare_enable(dmc->fout_bpll);
> + if (ret)
> + return ret;
> +
> + ret = clk_prepare_enable(dmc->mout_bpll);
> + if (ret) {
> + clk_disable_unprepare(dmc->fout_bpll);
> + return ret;
> + }
>
> /*
> * Some bootloaders do not set clock routes correctly.
>
As other folks mentioned, please align to the procedures for
sending the patches.
The change itself looks good, so looking forward for the proper
v2.
Regards,
Lukasz
prev parent reply other threads:[~2026-09-04 8:14 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-18 13:19 [PATCH] memory: exynos5422-dmc: handle clock enable failures Jiawen Liu
2026-08-20 10:55 ` Markus Elfring
2026-09-01 15:57 ` Krzysztof Kozlowski
2026-09-04 8:14 ` Lukasz Luba [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=92153d54-e7aa-4fe3-8317-0060b4078d6c@arm.com \
--to=lukasz.luba@arm.com \
--cc=1298662399@qq.com \
--cc=alim.akhtar@samsung.com \
--cc=krzk@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=peter.griffin@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