From: Jonathan Cameron <jic23@kernel.org>
To: Mikko Koivunen <mikko.koivunen@fi.rohmeurope.com>
Cc: pmeerw@pmeerw.net, knaack.h@gmx.de, lars@metafoo.de,
Daniel Baluta <daniel.baluta@nxp.com>,
linux-iio@vger.kernel.org
Subject: Re: [PATCH v6 10/10] iio: light: rpr0521 iio_device_register to devm_
Date: Tue, 20 Jun 2017 18:10:42 +0100 [thread overview]
Message-ID: <20170620181042.26bfd59c@kernel.org> (raw)
In-Reply-To: <1497516947-21482-1-git-send-email-mikko.koivunen@fi.rohmeurope.com>
On Thu, 15 Jun 2017 11:55:47 +0300
Mikko Koivunen <mikko.koivunen@fi.rohmeurope.com> wrote:
> Change iio_device_register to devm_
>
> Signed-off-by: Mikko Koivunen <mikko.koivunen@fi.rohmeurope.com>
This leads to a race I think.
Power is turned off in remove. Userspace interface is only removed
after the remove call ends.
Basic rule of thumb is that if you have anything in .remove then
you can't use the devm_iio_device_register call.
Jonathan
> ---
>
> drivers/iio/light/rpr0521.c | 4 +---
> 1 file changed, 1 insertion(+), 3 deletions(-)
>
> diff --git a/drivers/iio/light/rpr0521.c b/drivers/iio/light/rpr0521.c
> index ce576be..e00f427 100644
> --- a/drivers/iio/light/rpr0521.c
> +++ b/drivers/iio/light/rpr0521.c
> @@ -1025,7 +1025,7 @@ static int rpr0521_probe(struct i2c_client *client,
> }
> }
>
> - ret = iio_device_register(indio_dev);
> + ret = devm_iio_device_register(indio_dev->dev.parent, indio_dev);
> if (ret)
> goto err_pm_disable;
>
> @@ -1045,8 +1045,6 @@ static int rpr0521_remove(struct i2c_client *client)
> {
> struct iio_dev *indio_dev = i2c_get_clientdata(client);
>
> - iio_device_unregister(indio_dev);
> -
> pm_runtime_disable(&client->dev);
> pm_runtime_set_suspended(&client->dev);
> pm_runtime_put_noidle(&client->dev);
prev parent reply other threads:[~2017-06-20 17:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-15 8:55 [PATCH v6 10/10] iio: light: rpr0521 iio_device_register to devm_ Mikko Koivunen
2017-06-20 17:10 ` 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=20170620181042.26bfd59c@kernel.org \
--to=jic23@kernel.org \
--cc=daniel.baluta@nxp.com \
--cc=knaack.h@gmx.de \
--cc=lars@metafoo.de \
--cc=linux-iio@vger.kernel.org \
--cc=mikko.koivunen@fi.rohmeurope.com \
--cc=pmeerw@pmeerw.net \
/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;
as well as URLs for NNTP newsgroup(s).