On 09/24/13 10:32, Jiri Kosina wrote:
On Wed, 18 Sep 2013, Srinivas Pandruvada wrote:
Don't call hid_open_device till there is actually an user. This saves
power by not opening underlying transport for HID. Also close device
if there are no active mfd client using HID sensor hub.
On Wed, 18 Sep 2013, Srinivas Pandruvada wrote:
Don't call hid_open_device till there is actually an user. This saves
power by not opening underlying transport for HID. Also close device
if there are no active mfd client using HID sensor hub.
Signed-off-by: Srinivas Pandruvada
On 09/15/2013 03:15 AM, Jonathan Cameron wrote:
On 09/10/13 21:03, Srinivas Pandruvada wrote:
Don't call hid_open_device till there is actually an user. This saves
power by not opening underlying transport for HID. Also close device
if there are no active mfd client using HID sensor hub.
Don't call hid_open_device till there is actually an user. This saves
power by not opening underlying transport for HID. Also close device
if there are no active mfd client using HID sensor hub.
Signed-off-by: Srinivas Pandruvada srinivas.pandruv...@linux.intel.com
---
On 09/18/13 18:13, Srinivas Pandruvada wrote:
Don't call hid_open_device till there is actually an user. This saves
power by not opening underlying transport for HID. Also close device
if there are no active mfd client using HID sensor hub.
Signed-off-by: Srinivas Pandruvada
On 09/10/13 21:03, Srinivas Pandruvada wrote:
Don't call hid_open_device till there is actually an user. This saves
power by not opening underlying transport for HID. Also close device
if there are no active mfd client using HID sensor hub.
Signed-off-by: Srinivas Pandruvada
Don't call hid_open_device till there is actually an user. This saves
power by not opening underlying transport for HID. Also close device
if there are no active mfd client using HID sensor hub.
Signed-off-by: Srinivas Pandruvada srinivas.pandruv...@linux.intel.com
---