All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jonathan Cameron <jic23@kernel.org>
To: Chuhong Yuan <hslester96@gmail.com>
Cc: linux-iio@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] iio: mxc4005: Use device-managed APIs
Date: Sat, 27 Jul 2019 18:20:45 +0100	[thread overview]
Message-ID: <20190727182045.283fef07@archlinux> (raw)
In-Reply-To: <20190726063616.11045-1-hslester96@gmail.com>

On Fri, 26 Jul 2019 14:36:16 +0800
Chuhong Yuan <hslester96@gmail.com> wrote:

> Use device-managed APIs to simplify the code.
> The remove function is redundant now and can
> be deleted.
> 
> Signed-off-by: Chuhong Yuan <hslester96@gmail.com>
Applied, with a similar change to the other patches I modified earlier.

Applied to the togreg branch of iio.git and pushed out as testing for
the autobuilders to play with it.

Thanks,

Jonathan

> ---
>  drivers/iio/accel/mxc4005.c | 35 +++++++----------------------------
>  1 file changed, 7 insertions(+), 28 deletions(-)
> 
> diff --git a/drivers/iio/accel/mxc4005.c b/drivers/iio/accel/mxc4005.c
> index 637e6e676061..d8b999023ef2 100644
> --- a/drivers/iio/accel/mxc4005.c
> +++ b/drivers/iio/accel/mxc4005.c
> @@ -424,7 +424,7 @@ static int mxc4005_probe(struct i2c_client *client,
>  	indio_dev->modes = INDIO_DIRECT_MODE;
>  	indio_dev->info = &mxc4005_info;
>  
> -	ret = iio_triggered_buffer_setup(indio_dev,
> +	ret = devm_iio_triggered_buffer_setup(&client->dev, indio_dev,
>  					 iio_pollfunc_store_time,
>  					 mxc4005_trigger_handler,
>  					 NULL);
> @@ -452,7 +452,7 @@ static int mxc4005_probe(struct i2c_client *client,
>  		if (ret) {
>  			dev_err(&client->dev,
>  				"failed to init threaded irq\n");
> -			goto err_buffer_cleanup;
> +			return ret;
>  		}
>  
>  		data->dready_trig->dev.parent = &client->dev;
> @@ -460,43 +460,23 @@ static int mxc4005_probe(struct i2c_client *client,
>  		iio_trigger_set_drvdata(data->dready_trig, indio_dev);
>  		indio_dev->trig = data->dready_trig;
>  		iio_trigger_get(indio_dev->trig);
> -		ret = iio_trigger_register(data->dready_trig);
> +		ret = devm_iio_trigger_register(&client->dev,
> +						data->dready_trig);
>  		if (ret) {
>  			dev_err(&client->dev,
>  				"failed to register trigger\n");
> -			goto err_trigger_unregister;
> +			return ret;
>  		}
>  	}
>  
> -	ret = iio_device_register(indio_dev);
> +	ret = devm_iio_device_register(&client->dev, indio_dev);
>  	if (ret < 0) {
>  		dev_err(&client->dev,
>  			"unable to register iio device %d\n", ret);
> -		goto err_buffer_cleanup;
> +		return ret;
I dropped the print out and tidied this up as
return devm_iio_device_register();

>  	}
>  
>  	return 0;
> -
> -err_trigger_unregister:
> -	iio_trigger_unregister(data->dready_trig);
> -err_buffer_cleanup:
> -	iio_triggered_buffer_cleanup(indio_dev);
> -
> -	return ret;
> -}
> -
> -static int mxc4005_remove(struct i2c_client *client)
> -{
> -	struct iio_dev *indio_dev = i2c_get_clientdata(client);
> -	struct mxc4005_data *data = iio_priv(indio_dev);
> -
> -	iio_device_unregister(indio_dev);
> -
> -	iio_triggered_buffer_cleanup(indio_dev);
> -	if (data->dready_trig)
> -		iio_trigger_unregister(data->dready_trig);
> -
> -	return 0;
>  }
>  
>  static const struct acpi_device_id mxc4005_acpi_match[] = {
> @@ -517,7 +497,6 @@ static struct i2c_driver mxc4005_driver = {
>  		.acpi_match_table = ACPI_PTR(mxc4005_acpi_match),
>  	},
>  	.probe		= mxc4005_probe,
> -	.remove		= mxc4005_remove,
>  	.id_table	= mxc4005_id,
>  };
>  


      reply	other threads:[~2019-07-27 17:20 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-07-26  6:36 [PATCH] iio: mxc4005: Use device-managed APIs Chuhong Yuan
2019-07-27 17:20 ` 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=20190727182045.283fef07@archlinux \
    --to=jic23@kernel.org \
    --cc=hslester96@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.