Linux IIO development
 help / color / mirror / Atom feed
From: "Nuno Sá" <noname.nuno@gmail.com>
To: Christophe JAILLET <christophe.jaillet@wanadoo.fr>,
	Lars-Peter Clausen <lars@metafoo.de>,
	Michael Hennerich <Michael.Hennerich@analog.com>,
	Alexandru Tachici <alexandru.tachici@analog.com>,
	Jonathan Cameron <jic23@kernel.org>
Cc: linux-kernel@vger.kernel.org, kernel-janitors@vger.kernel.org,
	linux-iio@vger.kernel.org
Subject: Re: [PATCH] iio: adc: ad7192: Simplify using devm_clk_get_optional_enabled()
Date: Thu, 15 Jun 2023 14:12:57 +0200	[thread overview]
Message-ID: <55a46a8cffef60758f0136f389909e307fa1ade4.camel@gmail.com> (raw)
In-Reply-To: <7dbe973905f1fdae5d2f5ae5a3b01dd1d6a9925b.1686774340.git.christophe.jaillet@wanadoo.fr>

On Wed, 2023-06-14 at 22:26 +0200, Christophe JAILLET wrote:
> If st->mclk is not NULL, then st->clock_sel is either AD7192_CLK_EXT_MCLK2
> or AD7192_CLK_EXT_MCLK1_2.
> 
> So devm_clk_get_optional_enabled() can be used instead of hand writing it.
> This saves some line of code.
> 
> Signed-off-by: Christophe JAILLET <christophe.jaillet@wanadoo.fr>
> ---

Reviewed-by: Nuno Sa <nuno.sa@analog.com>

>  drivers/iio/adc/ad7192.c | 16 +---------------
>  1 file changed, 1 insertion(+), 15 deletions(-)
> 
> diff --git a/drivers/iio/adc/ad7192.c b/drivers/iio/adc/ad7192.c
> index 8685e0b58a83..5dcb257ad754 100644
> --- a/drivers/iio/adc/ad7192.c
> +++ b/drivers/iio/adc/ad7192.c
> @@ -972,11 +972,6 @@ static void ad7192_reg_disable(void *reg)
>         regulator_disable(reg);
>  }
>  
> -static void ad7192_clk_disable(void *clk)
> -{
> -       clk_disable_unprepare(clk);
> -}
> -
>  static int ad7192_probe(struct spi_device *spi)
>  {
>         struct ad7192_state *st;
> @@ -1044,7 +1039,7 @@ static int ad7192_probe(struct spi_device *spi)
>  
>         st->fclk = AD7192_INT_FREQ_MHZ;
>  
> -       st->mclk = devm_clk_get_optional(&spi->dev, "mclk");
> +       st->mclk = devm_clk_get_optional_enabled(&spi->dev, "mclk");
>         if (IS_ERR(st->mclk))
>                 return PTR_ERR(st->mclk);
>  
> @@ -1052,15 +1047,6 @@ static int ad7192_probe(struct spi_device *spi)
>  
>         if (st->clock_sel == AD7192_CLK_EXT_MCLK1_2 ||
>             st->clock_sel == AD7192_CLK_EXT_MCLK2) {
> -               ret = clk_prepare_enable(st->mclk);
> -               if (ret < 0)
> -                       return ret;
> -
> -               ret = devm_add_action_or_reset(&spi->dev, ad7192_clk_disable,
> -                                              st->mclk);
> -               if (ret)
> -                       return ret;
> -
>                 st->fclk = clk_get_rate(st->mclk);
>                 if (!ad7192_valid_external_frequency(st->fclk)) {
>                         dev_err(&spi->dev,


  reply	other threads:[~2023-06-15 12:10 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-14 20:26 [PATCH] iio: adc: ad7192: Simplify using devm_clk_get_optional_enabled() Christophe JAILLET
2023-06-15 12:12 ` Nuno Sá [this message]
2023-06-17 18:13   ` Jonathan Cameron

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=55a46a8cffef60758f0136f389909e307fa1ade4.camel@gmail.com \
    --to=noname.nuno@gmail.com \
    --cc=Michael.Hennerich@analog.com \
    --cc=alexandru.tachici@analog.com \
    --cc=christophe.jaillet@wanadoo.fr \
    --cc=jic23@kernel.org \
    --cc=kernel-janitors@vger.kernel.org \
    --cc=lars@metafoo.de \
    --cc=linux-iio@vger.kernel.org \
    --cc=linux-kernel@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