From: Jonathan Cameron <jic23@kernel.org>
To: Ye Xiang <xiang.ye@intel.com>
Cc: jikos@kernel.org, srinivas.pandruvada@linux.intel.com,
linux-input@vger.kernel.org, linux-iio@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 2/4] iio: hid-sensor-trigger: Decrement runtime pm enable count on driver removal
Date: Sat, 21 Nov 2020 17:22:57 +0000 [thread overview]
Message-ID: <20201121172257.59fa05d5@archlinux> (raw)
In-Reply-To: <20201119100331.2594-3-xiang.ye@intel.com>
On Thu, 19 Nov 2020 18:03:29 +0800
Ye Xiang <xiang.ye@intel.com> wrote:
> To avoid pm_runtime_disable called repeatedly by hid sensor drivers,
> decrease runtime pm enable count after call it.
>
> Signed-off-by: Ye Xiang <xiang.ye@intel.com>
This sounds like a fix. If so please make that clear and add a fixes tag.
If it couldn't have been triggered before, then please explain why in this
patch description.
Thanks,
Jonathan
> ---
> drivers/iio/common/hid-sensors/hid-sensor-trigger.c | 4 +++-
> 1 file changed, 3 insertions(+), 1 deletion(-)
>
> diff --git a/drivers/iio/common/hid-sensors/hid-sensor-trigger.c b/drivers/iio/common/hid-sensors/hid-sensor-trigger.c
> index ff375790b7e8..30340abcbc8d 100644
> --- a/drivers/iio/common/hid-sensors/hid-sensor-trigger.c
> +++ b/drivers/iio/common/hid-sensors/hid-sensor-trigger.c
> @@ -227,8 +227,10 @@ static int hid_sensor_data_rdy_trigger_set_state(struct iio_trigger *trig,
> void hid_sensor_remove_trigger(struct iio_dev *indio_dev,
> struct hid_sensor_common *attrb)
> {
> - if (atomic_read(&attrb->runtime_pm_enable))
> + if (atomic_read(&attrb->runtime_pm_enable)) {
> pm_runtime_disable(&attrb->pdev->dev);
> + atomic_dec(&attrb->runtime_pm_enable);
> + }
>
> pm_runtime_set_suspended(&attrb->pdev->dev);
> pm_runtime_put_noidle(&attrb->pdev->dev);
next prev parent reply other threads:[~2020-11-21 17:23 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-19 10:03 [PATCH v2 0/4] add custom hinge sensor support Ye Xiang
2020-11-19 10:03 ` [PATCH v2 1/4] HID: hid-sensor-custom: Add custom sensor iio support Ye Xiang
2020-11-21 17:21 ` Jonathan Cameron
2020-11-24 10:29 ` Ye, Xiang
2020-11-24 11:32 ` Jonathan Cameron
2020-11-25 2:27 ` Ye, Xiang
2020-11-28 13:29 ` Jonathan Cameron
2020-11-19 10:03 ` [PATCH v2 2/4] iio: hid-sensor-trigger: Decrement runtime pm enable count on driver removal Ye Xiang
2020-11-21 17:22 ` Jonathan Cameron [this message]
2020-11-22 1:54 ` Pandruvada, Srinivas
2020-11-19 10:03 ` [PATCH v2 3/4] iio: hid-sensor-trigger: Use iio->trig instead trig field internal structure Ye Xiang
2020-11-21 17:33 ` Jonathan Cameron
2020-11-19 10:03 ` [PATCH v2 4/4] iio: hid-sensors: Add hinge sensor driver Ye Xiang
2020-11-21 17:56 ` Jonathan Cameron
2020-11-22 1:46 ` Pandruvada, Srinivas
2020-11-22 2:14 ` Pandruvada, Srinivas
2020-11-22 14:14 ` Jonathan Cameron
2020-11-22 15:51 ` Pandruvada, Srinivas
2020-11-22 16:50 ` Jonathan Cameron
2020-11-24 3:30 ` Ye, Xiang
2020-11-24 11:36 ` Jonathan Cameron
2020-11-25 3:24 ` Ye, Xiang
2020-11-24 6:43 ` Ye, Xiang
2020-11-24 11:39 ` Jonathan Cameron
2020-11-25 2:39 ` Ye, Xiang
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=20201121172257.59fa05d5@archlinux \
--to=jic23@kernel.org \
--cc=jikos@kernel.org \
--cc=linux-iio@vger.kernel.org \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=srinivas.pandruvada@linux.intel.com \
--cc=xiang.ye@intel.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;
as well as URLs for NNTP newsgroup(s).