From: Marcelo Schmitt <marcelo.schmitt1@gmail.com>
To: "Maíra Canal" <maira.canal@usp.br>
Cc: michael.hennerich@analog.com, lars@metafoo.de, jic23@kernel.org,
linux-iio@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] iio: ad7266: convert probe to full device-managed
Date: Thu, 7 Apr 2022 00:18:46 -0300 [thread overview]
Message-ID: <Yk5YFrp3etcJBF6A@marsc.168.1.7> (raw)
In-Reply-To: <Yk2t5D2x2+YorkTd@fedora>
Hi Maíra,
On 04/06, Maíra Canal wrote:
> Convert probe functions to device-managed variants, with exception of
> the regulator, which required a devm_add_action_or_reset() hook
> registration.
>
> Signed-off-by: Maíra Canal <maira.canal@usp.br>
Nice patch!
Minor nit inline.
Reviewed-by: Marcelo Schmitt <marcelo.schmitt1@gmail.com>
> ---
> I apologize if you received this email more than once. For some reason, the
> patch is not showing up on the linux-iio mailing list. I believe that the
> problem was that Michael's Hennerich email on the MAINTAINERS list was
> Michael.Hennerich@analog.com instead of michael.hennerich@analog.com. Anyway,
> I am truly sorry with you received this email more than once.
> ---
> drivers/iio/adc/ad7266.c | 43 +++++++++++++---------------------------
> 1 file changed, 14 insertions(+), 29 deletions(-)
>
> diff --git a/drivers/iio/adc/ad7266.c b/drivers/iio/adc/ad7266.c
> index c17d9b5fbaf6..4f8f07d5c1a3 100644
> --- a/drivers/iio/adc/ad7266.c
> +++ b/drivers/iio/adc/ad7266.c
> @@ -378,6 +378,11 @@ static const char * const ad7266_gpio_labels[] = {
> "ad0", "ad1", "ad2",
> };
>
> +static void ad7266_reg_disable(void *reg)
> +{
> + regulator_disable(reg);
> +}
> +
> static int ad7266_probe(struct spi_device *spi)
> {
> struct ad7266_platform_data *pdata = spi->dev.platform_data;
> @@ -398,9 +403,13 @@ static int ad7266_probe(struct spi_device *spi)
> if (ret)
> return ret;
>
> + ret = devm_add_action_or_reset(&spi->dev, ad7266_reg_disable, st->reg);
> + if (ret)
> + return ret;
> +
> ret = regulator_get_voltage(st->reg);
> if (ret < 0)
> - goto error_disable_reg;
> + return ret;
>
> st->vref_mv = ret / 1000;
> } else {
> @@ -423,7 +432,7 @@ static int ad7266_probe(struct spi_device *spi)
> GPIOD_OUT_LOW);
> if (IS_ERR(st->gpios[i])) {
> ret = PTR_ERR(st->gpios[i]);
> - goto error_disable_reg;
> + return ret;
> }
> }
> }
> @@ -459,35 +468,12 @@ static int ad7266_probe(struct spi_device *spi)
> spi_message_add_tail(&st->single_xfer[1], &st->single_msg);
> spi_message_add_tail(&st->single_xfer[2], &st->single_msg);
>
> - ret = iio_triggered_buffer_setup(indio_dev, &iio_pollfunc_store_time,
> + ret = devm_iio_triggered_buffer_setup(&spi->dev, indio_dev, &iio_pollfunc_store_time,
> &ad7266_trigger_handler, &iio_triggered_buffer_setup_ops);
> if (ret)
> - goto error_disable_reg;
> -
> - ret = iio_device_register(indio_dev);
> - if (ret)
> - goto error_buffer_cleanup;
> -
> - return 0;
> -
> -error_buffer_cleanup:
> - iio_triggered_buffer_cleanup(indio_dev);
> -error_disable_reg:
> - if (!IS_ERR(st->reg))
> - regulator_disable(st->reg);
> -
> - return ret;
> -}
> -
> -static void ad7266_remove(struct spi_device *spi)
> -{
> - struct iio_dev *indio_dev = spi_get_drvdata(spi);
With this removal, there is no other usage of driver_data so you may also remove
spi_set_drvdata(spi, indio_dev);
> - struct ad7266_state *st = iio_priv(indio_dev);
> + return ret;
>
> - iio_device_unregister(indio_dev);
> - iio_triggered_buffer_cleanup(indio_dev);
> - if (!IS_ERR(st->reg))
> - regulator_disable(st->reg);
> + return devm_iio_device_register(&spi->dev, indio_dev);
> }
>
> static const struct spi_device_id ad7266_id[] = {
> @@ -502,7 +488,6 @@ static struct spi_driver ad7266_driver = {
> .name = "ad7266",
> },
> .probe = ad7266_probe,
> - .remove = ad7266_remove,
> .id_table = ad7266_id,
> };
> module_spi_driver(ad7266_driver);
> --
> 2.35.1
>
next prev parent reply other threads:[~2022-04-07 3:21 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-06 15:12 [PATCH] iio: ad7266: convert probe to full device-managed Maíra Canal
2022-04-07 3:18 ` Marcelo Schmitt [this message]
2022-04-07 9:00 ` Sa, Nuno
-- strict thread matches above, loose matches on Subject: below --
2022-04-06 12:29 Maíra Canal
2022-04-06 12:16 Maíra Canal
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=Yk5YFrp3etcJBF6A@marsc.168.1.7 \
--to=marcelo.schmitt1@gmail.com \
--cc=jic23@kernel.org \
--cc=lars@metafoo.de \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maira.canal@usp.br \
--cc=michael.hennerich@analog.com \
/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