summaryrefslogtreecommitdiff
path: root/fs
diff options
context:
space:
mode:
authorSong Hongyan <hongyan.song@intel.com>2017-02-22 17:17:38 +0800
committerGreg Kroah-Hartman <gregkh@linuxfoundation.org>2017-03-30 09:35:17 +0200
commit7413d1f8991e7d5c240d89a3feb35e2a54d27baf (patch)
tree89bce21b61b616b90f83f30d121c77dfeef3719d /fs
parent8f189e1d0ecac38ac69b44b89f2561c3bcffacbd (diff)
iio: hid-sensor-trigger: Change get poll value function order to avoid sensor properties losing after resume from S3
commit 3bec247474469f769af41e8c80d3a100dd97dd76 upstream. In function _hid_sensor_power_state(), when hid_sensor_read_poll_value() is called, sensor's all properties will be updated by the value from sensor hardware/firmware. In some implementation, sensor hardware/firmware will do a power cycle during S3. In this case, after resume, once hid_sensor_read_poll_value() is called, sensor's all properties which are kept by driver during S3 will be changed to default value. But instead, if a set feature function is called first, sensor hardware/firmware will be recovered to the last status. So change the sensor_hub_set_feature() calling order to behind of set feature function to avoid sensor properties lose. Signed-off-by: Song Hongyan <hongyan.song@intel.com> Acked-by: Srinivas Pandruvada <srinivas.pandruvada@linux.intel.com> Signed-off-by: Jonathan Cameron <jic23@kernel.org> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Diffstat (limited to 'fs')
0 files changed, 0 insertions, 0 deletions