Linux IIO development
 help / color / mirror / Atom feed
From: Dmitry Osipenko <dmitry.osipenko@collabora.com>
To: Shreeya Patel <shreeya.patel@collabora.com>,
	jic23@kernel.org, lars@metafoo.de, robh+dt@kernel.org,
	Zhigang.Shi@liteon.com, krisman@collabora.com
Cc: linux-iio@vger.kernel.org, devicetree@vger.kernel.org,
	linux-kernel@vger.kernel.org, kernel@collabora.com,
	alvaro.soliverez@collabora.com, andy.shevchenko@gmail.com,
	digetx@gmail.com, kernel test robot <lkp@intel.com>
Subject: Re: [PATCH v6 2/2] iio: light: Add support for ltrf216a sensor
Date: Thu, 7 Jul 2022 00:00:21 +0300	[thread overview]
Message-ID: <37527ba7-ae54-86a0-b0af-fe20d3a1e484@collabora.com> (raw)
In-Reply-To: <20220615135130.227236-3-shreeya.patel@collabora.com>

On 6/15/22 16:51, Shreeya Patel wrote:
> +static int ltrf216a_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);
> +	ltrf216a_disable(indio_dev);
> +
> +	return 0;
> +}

As Jonathan said, there is no need to disable sensor in the remove()
since you're using devm_add_action_or_reset().

If you're going to use devm_pm_runtime_enable(), then let's also use
devm_iio_device_register() and in this case the ltrf216a_remove() is not
needed anymore at all since the removal will be handled by the driver
core entirely, i.e. you'll need to drop ltrf216a_remove().

-- 
Best regards,
Dmitry

  parent reply	other threads:[~2022-07-06 21:00 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-15 13:51 [PATCH v6 0/2] Add LTRF216A Driver Shreeya Patel
2022-06-15 13:51 ` [PATCH v6 1/2] dt-bindings: Document ltrf216a light sensor bindings Shreeya Patel
2022-06-15 17:20   ` Rob Herring
2022-06-19 12:34   ` Jonathan Cameron
2022-06-19 12:57     ` Shreeya Patel
2022-06-15 13:51 ` [PATCH v6 2/2] iio: light: Add support for ltrf216a sensor Shreeya Patel
2022-06-15 16:32   ` Andy Shevchenko
2022-06-19 12:44     ` Jonathan Cameron
2022-07-06 20:52   ` Dmitry Osipenko
2022-07-06 20:52   ` Dmitry Osipenko
2022-07-06 20:59   ` Dmitry Osipenko
2022-07-06 21:00   ` Dmitry Osipenko [this message]
2022-07-06 21:09   ` Dmitry Osipenko
2022-07-06 22:48     ` Shreeya Patel

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=37527ba7-ae54-86a0-b0af-fe20d3a1e484@collabora.com \
    --to=dmitry.osipenko@collabora.com \
    --cc=Zhigang.Shi@liteon.com \
    --cc=alvaro.soliverez@collabora.com \
    --cc=andy.shevchenko@gmail.com \
    --cc=devicetree@vger.kernel.org \
    --cc=digetx@gmail.com \
    --cc=jic23@kernel.org \
    --cc=kernel@collabora.com \
    --cc=krisman@collabora.com \
    --cc=lars@metafoo.de \
    --cc=linux-iio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lkp@intel.com \
    --cc=robh+dt@kernel.org \
    --cc=shreeya.patel@collabora.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