summaryrefslogtreecommitdiffstats
path: root/drivers/md
diff options
context:
space:
mode:
authorSong Hongyan <hongyan.song@intel.com>2017-02-22 17:17:38 +0800
committerJonathan Cameron <jic23@kernel.org>2017-03-05 10:26:47 +0000
commit3bec247474469f769af41e8c80d3a100dd97dd76 (patch)
tree46aa75b1a3470ece108e23a51b77f95ce9fea9af /drivers/md
parent2d62e0768d3c28536d4cfe4c40ba1e5e8e442a93 (diff)
downloadlinux-3bec247474469f769af41e8c80d3a100dd97dd76.tar.bz2
iio: hid-sensor-trigger: Change get poll value function order to avoid sensor properties losing after resume from S3
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> Cc: <Stable@vger.kernel.org> Signed-off-by: Jonathan Cameron <jic23@kernel.org>
Diffstat (limited to 'drivers/md')
0 files changed, 0 insertions, 0 deletions