From: Hugo Villeneuve <hugo@hugovil.com>
To: Xiangwu Lai <laixiangwu@cmss.chinamobile.com>
Cc: gregkh@linuxfoundation.org, jirislaby@kernel.org,
linux-serial@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] serial: sc16is7xx: Fix clock leak on invalid clock frequency
Date: Fri, 13 Nov 2026 15:03:31 -0500 [thread overview]
Message-ID: <20261113150331.0133a3b8601bcb64b6536ef8@hugovil.com> (raw)
In-Reply-To: <20261113103855.2144-1-laixiangwu@cmss.chinamobile.com>
Hi,
On Fri, 13 Nov 2026 18:38:54 +0800
Xiangwu Lai <laixiangwu@cmss.chinamobile.com> wrote:
> sc16is7xx_probe() enables the clock with clk_prepare_enable() early
> in the probe path. If the resulting clock frequency cannot be
> determined (neither from the clock itself, nor from the
> "clock-frequency" property or platform data), the driver bails out
> with -EINVAL, but it does so with a plain return, leaving the clock
> prepared and enabled.
>
> Switch to devm_clk_get_optional_enabled(), which drops the clock
> reference and disables the clock automatically when the probe fails
> and when the device is removed. The manual clock management is no
> longer needed: drop clk_prepare_enable(), the out_clk label and the
> clk_disable_unprepare() call in sc16is7xx_remove().
>
> Fixes: cb1b206cff46 ("serial: sc16is7xx: Use devm_clk_get_optional()")
> Suggested-by: Hugo Villeneuve <hugo@hugovil.com>
> Signed-off-by: Xiangwu Lai <laixiangwu@cmss.chinamobile.com>
Reviewed-by: Hugo Villeneuve <hvilleneuve@dimonoff.com>
> ---
> Changes in v2:
>
> - Rework the patch following Hugo Villeneuve's suggestion: switch to
> devm_clk_get_optional_enabled() so the clock is disabled
> automatically on probe failure and on remove, and remove the now
> unneeded manual clock management (clk_prepare_enable(), the
> out_clk label and the clk_disable_unprepare() call in
> sc16is7xx_remove()). The -EINVAL path keeps its original plain
> return since devm handles the cleanup.
>
> Link: https://lore.kernel.org/all/20261030085508.1882-1-laixiangwu@cmss.chinamobile.com
> drivers/tty/serial/sc16is7xx.c | 18 ++++--------------
> 1 file changed, 4 insertions(+), 14 deletions(-)
>
> diff --git a/drivers/tty/serial/sc16is7xx.c b/drivers/tty/serial/sc16is7xx.c
> index fba588559..a69b71fb8 100644
> --- a/drivers/tty/serial/sc16is7xx.c
> +++ b/drivers/tty/serial/sc16is7xx.c
> @@ -1605,14 +1605,10 @@ int sc16is7xx_probe(struct device *dev, const struct sc16is7xx_devtype *devtype,
> dev_dbg(dev,
> "No interrupt pin definition, falling back to polling mode\n");
>
> - s->clk = devm_clk_get_optional(dev, NULL);
> + s->clk = devm_clk_get_optional_enabled(dev, NULL);
> if (IS_ERR(s->clk))
> return PTR_ERR(s->clk);
>
> - ret = clk_prepare_enable(s->clk);
> - if (ret)
> - return ret;
> -
> freq = clk_get_rate(s->clk);
> if (freq == 0) {
> if (uartclk)
> @@ -1631,10 +1627,9 @@ int sc16is7xx_probe(struct device *dev, const struct sc16is7xx_devtype *devtype,
> kthread_init_worker(&s->kworker);
> s->kworker_task = kthread_run(kthread_worker_fn, &s->kworker,
> "sc16is7xx");
> - if (IS_ERR(s->kworker_task)) {
> - ret = PTR_ERR(s->kworker_task);
> - goto out_clk;
> - }
> + if (IS_ERR(s->kworker_task))
> + return PTR_ERR(s->kworker_task);
> +
> sched_set_fifo(s->kworker_task);
>
> ret = sc16is7xx_reset(dev, regmaps[0]);
> @@ -1711,9 +1706,6 @@ int sc16is7xx_probe(struct device *dev, const struct sc16is7xx_devtype *devtype,
> out_kthread:
> kthread_stop(s->kworker_task);
>
> -out_clk:
> - clk_disable_unprepare(s->clk);
> -
> return ret;
> }
> EXPORT_SYMBOL_GPL(sc16is7xx_probe);
> @@ -1740,8 +1732,6 @@ void sc16is7xx_remove(struct device *dev)
>
> kthread_flush_worker(&s->kworker);
> kthread_stop(s->kworker_task);
> -
> - clk_disable_unprepare(s->clk);
> }
> EXPORT_SYMBOL_GPL(sc16is7xx_remove);
>
> --
> 2.50.1.windows.1
>
>
>
>
--
Hugo Villeneuve
prev parent reply other threads:[~2026-11-13 20:03 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-13 10:38 Xiangwu Lai
2026-11-13 20:03 ` Hugo Villeneuve [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=20261113150331.0133a3b8601bcb64b6536ef8@hugovil.com \
--to=hugo@hugovil.com \
--cc=gregkh@linuxfoundation.org \
--cc=jirislaby@kernel.org \
--cc=laixiangwu@cmss.chinamobile.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-serial@vger.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
all inboxes | Powered by JetHome®