From: Christophe JAILLET <christophe.jaillet@wanadoo.fr>
To: Huan Yang <link@vivo.com>, Pavel Machek <pavel@ucw.cz>,
Lee Jones <lee@kernel.org>,
linux-leds@vger.kernel.org, linux-kernel@vger.kernel.org
Cc: opensource.kernel@vivo.com
Subject: Re: [PATCH] leds: lp55xx: Use devm_clk_get_enabled() helpers
Date: Tue, 20 Aug 2024 15:13:53 +0200 [thread overview]
Message-ID: <d8ae467b-de1b-4c65-a2b0-877ef887f9ae@wanadoo.fr> (raw)
In-Reply-To: <20240820102006.128840-1-link@vivo.com>
Le 20/08/2024 à 12:20, Huan Yang a écrit :
> lp55xx lp55xx_is_extclk_used get, enable clk and
> deinit_device disable and unprepare it.
>
> This can use a simplifies helper to cover.
>
> Signed-off-by: Huan Yang <link@vivo.com>
> ---
Hi,
if you want to go 1 step further, I think that 'vlk' can now also be
removed from struct lp55xx_chip.
Just my 2c.
CJ
> drivers/leds/leds-lp55xx-common.c | 14 ++------------
> 1 file changed, 2 insertions(+), 12 deletions(-)
>
> diff --git a/drivers/leds/leds-lp55xx-common.c b/drivers/leds/leds-lp55xx-common.c
> index 29e7142dca72..76dc62a3bd45 100644
> --- a/drivers/leds/leds-lp55xx-common.c
> +++ b/drivers/leds/leds-lp55xx-common.c
> @@ -965,21 +965,14 @@ EXPORT_SYMBOL_GPL(lp55xx_update_bits);
> bool lp55xx_is_extclk_used(struct lp55xx_chip *chip)
> {
> struct clk *clk;
> - int err;
>
> - clk = devm_clk_get(&chip->cl->dev, "32k_clk");
> + clk = devm_clk_get_enabled(&chip->cl->dev, "32k_clk");
> if (IS_ERR(clk))
> goto use_internal_clk;
>
> - err = clk_prepare_enable(clk);
> - if (err)
> + if (clk_get_rate(clk) != LP55XX_CLK_32K)
> goto use_internal_clk;
>
> - if (clk_get_rate(clk) != LP55XX_CLK_32K) {
> - clk_disable_unprepare(clk);
> - goto use_internal_clk;
> - }
> -
> dev_info(&chip->cl->dev, "%dHz external clock used\n", LP55XX_CLK_32K);
>
> chip->clk = clk;
> @@ -995,9 +988,6 @@ static void lp55xx_deinit_device(struct lp55xx_chip *chip)
> {
> struct lp55xx_platform_data *pdata = chip->pdata;
>
> - if (chip->clk)
> - clk_disable_unprepare(chip->clk);
> -
> if (pdata->enable_gpiod)
> gpiod_set_value(pdata->enable_gpiod, 0);
> }
next prev parent reply other threads:[~2024-08-20 13:15 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-20 10:20 Huan Yang
2024-08-20 13:13 ` Christophe JAILLET [this message]
2024-08-22 13:27 ` (subset) " Lee Jones
2024-08-22 13:28 ` Lee Jones
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=d8ae467b-de1b-4c65-a2b0-877ef887f9ae@wanadoo.fr \
--to=christophe.jaillet@wanadoo.fr \
--cc=lee@kernel.org \
--cc=link@vivo.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-leds@vger.kernel.org \
--cc=opensource.kernel@vivo.com \
--cc=pavel@ucw.cz \
/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®