From: Bastien Nocera <hadess@hadess.net>
To: Srinivas Pandruvada <srinivas.pandruvada@linux.intel.com>,
jic23@kernel.org, Hans de Goede <hdegoede@redhat.com>
Cc: linux-iio@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [RFT][PATCH] iio: hid-sensor-trigger: Fix the race with user space powering up sensors
Date: Fri, 11 Aug 2017 16:04:30 +0200 [thread overview]
Message-ID: <1502460270.2588.8.camel@hadess.net> (raw)
In-Reply-To: <1502407444-1078-1-git-send-email-srinivas.pandruvada@linux.intel.com>
Woot!
On Thu, 2017-08-10 at 16:24 -0700, Srinivas Pandruvada 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>
I'm still chasing a couple of bugs in the user-space side of things
caused by the removal of the timeout.
Thanks!
next prev parent reply other threads:[~2017-08-11 14:04 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-10 23:24 [RFT][PATCH] iio: hid-sensor-trigger: Fix the race with user space powering up sensors Srinivas Pandruvada
2017-08-11 14:04 ` Bastien Nocera [this message]
2017-08-12 12:16 ` Jonathan Cameron
2017-08-12 12:58 ` Bastien Nocera
2017-08-12 16:04 ` Srinivas Pandruvada
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=1502460270.2588.8.camel@hadess.net \
--to=hadess@hadess.net \
--cc=hdegoede@redhat.com \
--cc=jic23@kernel.org \
--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