summaryrefslogtreecommitdiffstats
path: root/drivers/iio/trigger
diff options
context:
space:
mode:
authorSrinivas Pandruvada2017-04-08 02:13:17 +0200
committerJonathan Cameron2017-04-08 16:13:36 +0200
commit5d9854eaea776441b38a9a45b4e6879524c4f48c (patch)
tree305609e2526bcb3432b5b0abc98efe074c822d48 /drivers/iio/trigger
parentMerge tag 'iio-fixes-for-4.11d' of git://git.kernel.org/pub/scm/linux/kernel/... (diff)
downloadkernel-qcow2-linux-5d9854eaea776441b38a9a45b4e6879524c4f48c.tar.gz
kernel-qcow2-linux-5d9854eaea776441b38a9a45b4e6879524c4f48c.tar.xz
kernel-qcow2-linux-5d9854eaea776441b38a9a45b4e6879524c4f48c.zip
iio: hid-sensor: Store restore poll and hysteresis on S3
This change undo the change done by 'commit 3bec24747446 ("iio: hid-sensor-trigger: Change get poll value function order to avoid sensor properties losing after resume from S3")' as this breaks some USB/i2c sensor hubs. Instead of relying on HW for restoring poll and hysteresis, driver stores and restores on resume (S3). In this way user space modified settings are not lost for any kind of sensor hub behavior. In this change, whenever user space modifies sampling frequency or hysteresis driver will get the feature value from the hub and store in the per device hid_sensor_common data structure. On resume callback from S3, system will set the feature to sensor hub, if user space ever modified the feature value. Fixes: 3bec24747446 ("iio: hid-sensor-trigger: Change get poll value function order to avoid sensor properties losing after resume from S3") Reported-by: Ritesh Raj Sarraf <rrs@researchut.com> Tested-by: Ritesh Raj Sarraf <rrs@researchut.com> Tested-by: Song, Hongyan <hongyan.song@intel.com> Cc: stable@vger.kernel.org Signed-off-by: Srinivas Pandruvada <srinivas.pandruvada@linux.intel.com> Signed-off-by: Jonathan Cameron <jic23@kernel.org>
Diffstat (limited to 'drivers/iio/trigger')
0 files changed, 0 insertions, 0 deletions