public inbox for linux-iio@vger.kernel.org
help / color / mirror / Atom feed
From: Jonathan Cameron <jic23@kernel.org>
To: Alexandru Ardelean <aardelean@deviqon.com>
Cc: linux-kernel@vger.kernel.org, linux-iio@vger.kernel.org
Subject: Re: [PATCH] iio: light: max44000: use device-managed functions in probe
Date: Sat, 18 Sep 2021 19:08:34 +0100	[thread overview]
Message-ID: <20210918190834.66d6fbce@jic23-huawei> (raw)
In-Reply-To: <20210913120002.306280-1-aardelean@deviqon.com>

On Mon, 13 Sep 2021 15:00:02 +0300
Alexandru Ardelean <aardelean@deviqon.com> wrote:

> This is a simple conversion. Both iio_device_register() and
> iio_triggered_buffer_setup() functions have device-managed variants.
> 
> Signed-off-by: Alexandru Ardelean <aardelean@deviqon.com>
Applied to the togreg branch of iio.git and pushed out as testing
as per normal.

Thanks,

Jonathan

> ---
>  drivers/iio/light/max44000.c | 17 +++--------------
>  1 file changed, 3 insertions(+), 14 deletions(-)
> 
> diff --git a/drivers/iio/light/max44000.c b/drivers/iio/light/max44000.c
> index b8e721bced5b..85689dffbcbf 100644
> --- a/drivers/iio/light/max44000.c
> +++ b/drivers/iio/light/max44000.c
> @@ -540,7 +540,6 @@ static int max44000_probe(struct i2c_client *client,
>  		return PTR_ERR(data->regmap);
>  	}
>  
> -	i2c_set_clientdata(client, indio_dev);
>  	mutex_init(&data->lock);
>  	indio_dev->info = &max44000_info;
>  	indio_dev->name = MAX44000_DRV_NAME;
> @@ -589,23 +588,14 @@ static int max44000_probe(struct i2c_client *client,
>  		return ret;
>  	}
>  
> -	ret = iio_triggered_buffer_setup(indio_dev, NULL, max44000_trigger_handler, NULL);
> +	ret = devm_iio_triggered_buffer_setup(&client->dev, indio_dev, NULL,
> +					      max44000_trigger_handler, NULL);
>  	if (ret < 0) {
>  		dev_err(&client->dev, "iio triggered buffer setup failed\n");
>  		return ret;
>  	}
>  
> -	return iio_device_register(indio_dev);
> -}
> -
> -static int max44000_remove(struct i2c_client *client)
> -{
> -	struct iio_dev *indio_dev = i2c_get_clientdata(client);
> -
> -	iio_device_unregister(indio_dev);
> -	iio_triggered_buffer_cleanup(indio_dev);
> -
> -	return 0;
> +	return devm_iio_device_register(&client->dev, indio_dev);
>  }
>  
>  static const struct i2c_device_id max44000_id[] = {
> @@ -628,7 +618,6 @@ static struct i2c_driver max44000_driver = {
>  		.acpi_match_table = ACPI_PTR(max44000_acpi_match),
>  	},
>  	.probe		= max44000_probe,
> -	.remove		= max44000_remove,
>  	.id_table	= max44000_id,
>  };
>  


      reply	other threads:[~2021-09-18 18:04 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-13 12:00 [PATCH] iio: light: max44000: use device-managed functions in probe Alexandru Ardelean
2021-09-18 18:08 ` 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=20210918190834.66d6fbce@jic23-huawei \
    --to=jic23@kernel.org \
    --cc=aardelean@deviqon.com \
    --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