From: Jonathan Cameron <jic23@kernel.org>
To: Srinivas Pandruvada <srinivas.pandruvada@linux.intel.com>
Cc: hadess@hadess.net, linux-iio@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] iio: hid-sensor-trigger: Fix the race with user space powering up sensors
Date: Sun, 13 Aug 2017 13:12:46 +0100 [thread overview]
Message-ID: <20170813131246.5d97a020@archlinux> (raw)
In-Reply-To: <1502554161-9300-1-git-send-email-srinivas.pandruvada@linux.intel.com>
On Sat, 12 Aug 2017 09:09:21 -0700
Srinivas Pandruvada <srinivas.pandruvada@linux.intel.com> wrote:
> It has been reported for a while that with iio-sensor-proxy service the
> rotation only works after one suspend/resume cycle. This required a wait
> in the systemd unit file to avoid race. I found a Yoga 900 where I could
> reproduce this.
>
> The problem scenerio is:
> - During sensor driver init, enable run time PM and also set a
> auto-suspend for 3 seconds.
> This result in one runtime resume. But there is a check to avoid
> a powerup in this sequence, but rpm is active
> - User space iio-sensor-proxy tries to power up the sensor. Since rpm is
> active it will simply return. But sensors were not actually
> powered up in the prior sequence, so actaully the sensors will not work
> - After 3 seconds the auto suspend kicks
>
> If we add a wait in systemd service file to fire iio-sensor-proxy after
> 3 seconds, then now everything will work as the runtime resume will
> actually powerup the sensor as this is a user request.
>
> To avoid this:
> - Remove the check to match user requested state, this will cause a
> brief powerup, but if the iio-sensor-proxy starts immediately it will
> still work as the sensors are ON.
> - Also move the autosuspend delay to place when user requested turn off
> of sensors, like after user finished raw read or buffer disable
>
> Signed-off-by: Srinivas Pandruvada <srinivas.pandruvada@linux.intel.com>
> Tested-by: Bastien Nocera <hadess@hadess.net>
>
Applied to the fixes-togreg branch of iio.git and marked for stable.
Thanks,
Jonathan
> ---
> Changes:
> Removed RFT and added Tested-by tag.
>
> drivers/iio/common/hid-sensors/hid-sensor-trigger.c | 8 ++++----
> 1 file changed, 4 insertions(+), 4 deletions(-)
>
> diff --git a/drivers/iio/common/hid-sensors/hid-sensor-trigger.c b/drivers/iio/common/hid-sensors/hid-sensor-trigger.c
> index 16ade0a..0e4b379 100644
> --- a/drivers/iio/common/hid-sensors/hid-sensor-trigger.c
> +++ b/drivers/iio/common/hid-sensors/hid-sensor-trigger.c
> @@ -111,8 +111,6 @@ static int _hid_sensor_power_state(struct hid_sensor_common *st, bool state)
> s32 poll_value = 0;
>
> if (state) {
> - if (!atomic_read(&st->user_requested_state))
> - return 0;
> if (sensor_hub_device_open(st->hsdev))
> return -EIO;
>
> @@ -161,6 +159,9 @@ static int _hid_sensor_power_state(struct hid_sensor_common *st, bool state)
> &report_val);
> }
>
> + pr_debug("HID_SENSOR %s set power_state %d report_state %d\n",
> + st->pdev->name, state_val, report_val);
> +
> sensor_hub_get_feature(st->hsdev, st->power_state.report_id,
> st->power_state.index,
> sizeof(state_val), &state_val);
> @@ -182,6 +183,7 @@ int hid_sensor_power_state(struct hid_sensor_common *st, bool state)
> ret = pm_runtime_get_sync(&st->pdev->dev);
> else {
> pm_runtime_mark_last_busy(&st->pdev->dev);
> + pm_runtime_use_autosuspend(&st->pdev->dev);
> ret = pm_runtime_put_autosuspend(&st->pdev->dev);
> }
> if (ret < 0) {
> @@ -285,8 +287,6 @@ int hid_sensor_setup_trigger(struct iio_dev *indio_dev, const char *name,
> /* Default to 3 seconds, but can be changed from sysfs */
> pm_runtime_set_autosuspend_delay(&attrb->pdev->dev,
> 3000);
> - pm_runtime_use_autosuspend(&attrb->pdev->dev);
> -
> return ret;
> error_unreg_trigger:
> iio_trigger_unregister(trig);
prev parent reply other threads:[~2017-08-13 12:12 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-12 16:09 [PATCH] iio: hid-sensor-trigger: Fix the race with user space powering up sensors Srinivas Pandruvada
2017-08-13 12:12 ` 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=20170813131246.5d97a020@archlinux \
--to=jic23@kernel.org \
--cc=hadess@hadess.net \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=srinivas.pandruvada@linux.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).