From: sashiko-bot@kernel.org
To: "Hongling Zeng" <zenghongling@kylinos.cn>
Cc: olteanv@gmail.com, vkoul@kernel.org,
linux-phy@lists.infradead.org, neil.armstrong@linaro.org
Subject: Re: [PATCH v7 4/4] phy: ti-pipe3: Fix clock leak in init error path
Date: Wed, 09 Sep 2026 11:43:58 +0000 [thread overview]
Message-ID: <20260909114358.8F9BE1F00A3E@smtp.kernel.org> (raw)
In-Reply-To: <20260909113433.1287454-5-zenghongling@kylinos.cn>
Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Medium] The patch includes an undocumented fix for a clock leak in the SATA normal exit path.
--
commit ca88937817d44eb924ea2b35541539f033e6efa9
Author: Hongling Zeng <zenghongling@kylinos.cn>
phy: ti-pipe3: Fix clock leak in init error path
When regmap_update_bits() fails in ti_pipe3_init() for PCIe mode,
the function returns the error without calling ti_pipe3_disable_clocks().
This leaves the clocks permanently enabled since the PHY framework won't
invoke the .exit callback on init failure.
Link: https://lore.kernel.org/all/20260518023657.41852C2BCB0@smtp.kernel.org/
> diff --git a/drivers/phy/ti/phy-ti-pipe3.c b/drivers/phy/ti/phy-ti-pipe3.c
> index a67f5da43c83b..fea64db93da54 100644
> --- a/drivers/phy/ti/phy-ti-pipe3.c
> +++ b/drivers/phy/ti/phy-ti-pipe3.c
[ ... ]
> @@ -555,8 +557,10 @@ static int ti_pipe3_exit(struct phy *x)
> /* If dpll_reset_syscon is not present we wont power down SATA DPLL
> * due to Errata i783
> */
> - if (phy->mode == PIPE3_MODE_SATA && !phy->dpll_reset_syscon)
> + if (phy->mode == PIPE3_MODE_SATA && !phy->dpll_reset_syscon) {
> + ti_pipe3_disable_clocks(phy);
> return 0;
> + }
>
> /* PCIe doesn't have internal DPLL */
> if (phy->mode != PIPE3_MODE_PCIE) {
[Severity: Medium]
Does the commit message need to document this fix in the SATA exit path?
The commit message only mentions fixing the clock leak in the ti_pipe3_init()
error path for PCIe mode.
This addition of ti_pipe3_disable_clocks() in ti_pipe3_exit() for the SATA
mode seems like a meaningful functional change that isn't documented in the
commit log, which could cause confusion during review and hinder stable
backports.
--
Sashiko AI review · https://sashiko.dev/#/patchset/20260909113433.1287454-1-zenghongling@kylinos.cn?part=4
--
linux-phy mailing list
linux-phy@lists.infradead.org
https://lists.infradead.org/mailman/listinfo/linux-phy
prev parent reply other threads:[~2026-09-09 11:44 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-09 11:34 [PATCH v7 0/4] phy: ti-pipe3: Fix clock resource handling issues Hongling Zeng
2026-09-09 11:34 ` [PATCH v7 1/4] phy: ti-pipe3: Fix ignored clock enable return value in init Hongling Zeng
2026-09-09 11:46 ` sashiko-bot
2026-09-09 11:34 ` [PATCH v7 2/4] phy: ti: pipe3: Fix clock resource leak on probe errors Hongling Zeng
2026-09-09 11:34 ` [PATCH v7 3/4] phy: ti-pipe3: Fix EPROBE_DEFER handling for clock resources Hongling Zeng
2026-09-09 11:42 ` sashiko-bot
2026-09-09 11:34 ` [PATCH v7 4/4] phy: ti-pipe3: Fix clock leak in init error path Hongling Zeng
2026-09-09 11:43 ` sashiko-bot [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=20260909114358.8F9BE1F00A3E@smtp.kernel.org \
--to=sashiko-bot@kernel.org \
--cc=linux-phy@lists.infradead.org \
--cc=neil.armstrong@linaro.org \
--cc=olteanv@gmail.com \
--cc=sashiko-reviews@lists.linux.dev \
--cc=vkoul@kernel.org \
--cc=zenghongling@kylinos.cn \
/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