From: Jonathan Cameron <jic23@kernel.org>
To: Andrey Smirnov <andrew.smirnov@gmail.com>
Cc: linux-iio@vger.kernel.org, linux-kernel@vger.kernel.org,
Chris Healy <cphealy@gmail.com>,
Vladimir Barinov <vladimir.barinov@cogentembedded.com>,
Nikita Yushchenko <nikita.yoush@cogentembedded.com>
Subject: Re: [PATCH] iio: hi8435: Drop hi8435_remove()
Date: Sun, 11 Aug 2019 10:00:22 +0100 [thread overview]
Message-ID: <20190811100022.4fe91756@archlinux> (raw)
In-Reply-To: <20190811054545.6922-1-andrew.smirnov@gmail.com>
On Sat, 10 Aug 2019 22:45:45 -0700
Andrey Smirnov <andrew.smirnov@gmail.com> wrote:
> Convert the remainder of hi8435_probe() to use devres and get rid of
> hi8435_remove().
>
> Signed-off-by: Andrey Smirnov <andrew.smirnov@gmail.com>
> Cc: linux-kernel@vger.kernel.org
> Cc: linux-iio@vger.kernel.org
> Cc: Jonathan Cameron <jic23@kernel.org>
> Cc: Chris Healy <cphealy@gmail.com>
+CC as before.
I've tweaked things a little bit (see below)
Applied to the togreg branch of iio.git and pushed out as testing
for the autobuilders to play with it.
Still time for others to comment btw!
Thanks,
Jonathan
> ---
> drivers/iio/adc/hi8435.c | 30 +++++++++++++-----------------
> 1 file changed, 13 insertions(+), 17 deletions(-)
>
> diff --git a/drivers/iio/adc/hi8435.c b/drivers/iio/adc/hi8435.c
> index c15f0e154e4d..fe1341383d30 100644
> --- a/drivers/iio/adc/hi8435.c
> +++ b/drivers/iio/adc/hi8435.c
> @@ -456,6 +456,11 @@ static irqreturn_t hi8435_trigger_handler(int irq, void *private)
> return IRQ_HANDLED;
> }
>
> +static void hi8435_triggered_event_cleanup(void *data)
> +{
> + iio_triggered_event_cleanup(data);
> +}
Hmm. I wonder if we should do a full devm_iio_triggered_event_setup()
but given we have very few callers that can be a job for another day.
> +
> static int hi8435_probe(struct spi_device *spi)
> {
> struct iio_dev *idev;
> @@ -513,26 +518,18 @@ static int hi8435_probe(struct spi_device *spi)
> if (ret)
> return ret;
>
> - ret = iio_device_register(idev);
> + ret = devm_add_action_or_reset(&spi->dev,
> + hi8435_triggered_event_cleanup,
> + idev);
> + if (ret)
> + return ret;
> +
> + ret = devm_iio_device_register(&spi->dev, idev);
> if (ret < 0) {
> dev_err(&spi->dev, "unable to register device\n");
> - goto unregister_triggered_event;
> + return ret;
We could tidy up a little more and do
if (ret)
dev_err...
return ret;
Or, given all the likely paths in iio_device_register() have
error prints anyway, can just do
return devm_iio_device_register();
I'll change it to this last one whilst applying.
> }
>
> - return 0;
> -
> -unregister_triggered_event:
> - iio_triggered_event_cleanup(idev);
> - return ret;
> -}
> -
> -static int hi8435_remove(struct spi_device *spi)
> -{
> - struct iio_dev *idev = spi_get_drvdata(spi);
> -
> - iio_device_unregister(idev);
> - iio_triggered_event_cleanup(idev);
> -
> return 0;
> }
>
> @@ -554,7 +551,6 @@ static struct spi_driver hi8435_driver = {
> .of_match_table = of_match_ptr(hi8435_dt_ids),
> },
> .probe = hi8435_probe,
> - .remove = hi8435_remove,
> .id_table = hi8435_id,
> };
> module_spi_driver(hi8435_driver);
prev parent reply other threads:[~2019-08-11 9:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-11 5:45 [PATCH] iio: hi8435: Drop hi8435_remove() Andrey Smirnov
2019-08-11 9:00 ` Jonathan Cameron [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=20190811100022.4fe91756@archlinux \
--to=jic23@kernel.org \
--cc=andrew.smirnov@gmail.com \
--cc=cphealy@gmail.com \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nikita.yoush@cogentembedded.com \
--cc=vladimir.barinov@cogentembedded.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