On Wed, 29 May 2013, Srinivas Pandruvada wrote:
Daniel has tested and confirmed that this patch fixes issue.
Thanks for confirmation. I have now applied the patch.
--
Jiri Kosina
SUSE Labs
--
To unsubscribe from this list: send the line unsubscribe linux-input in
the body of a message to
On Wed, 10 Apr 2013, Srinivas Pandruvada wrote:
I don't know if this should be fixed in client drivers since other drivers may
have this issue.
Agreed.
Srinivas, how about the patch below, could you please test it in your
scenario to see whether it actually fixes the issue?
Thanks.
diff
Jiri, ping?
Daniel
On Wed, 10 Apr 2013 08:44:34 -0700
Srinivas Pandruvada srinivas.pandruv...@linux.intel.com wrote:
Thanks Daniel.
I don't know if this should be fixed in client drivers since other
drivers may have this issue.
I interpret the return value of hdrv-raw_event as :
0
On Mon, 25 Mar 2013, Srinivas Pandruvada wrote:
Daniel,
I am looking at 3.9.rc1.
The only place I see the raw_event callback is called from
hid/hid_input_report(). hid_input_report is called with type
HID_INPUT_REPORT
in all cases, except hid_ctrl(), where it can be different depending on
On Mon, 25 Mar 2013, Srinivas Pandruvada wrote:
Daniel,
I am looking at 3.9.rc1.
The only place I see the raw_event callback is called from
hid/hid_input_report(). hid_input_report is called with type
HID_INPUT_REPORT
in all cases, except hid_ctrl(), where it can be different depending on
On Mon, 25 Mar 2013, Srinivas Pandruvada wrote:
Daniel,
I am looking at 3.9.rc1.
The only place I see the raw_event callback is called from
hid/hid_input_report(). hid_input_report is called with type HID_INPUT_REPORT
in all cases, except hid_ctrl(), where it can be different depending on
From: Daniel Leung daniel.le...@linux.intel.com
In sensor_hub_raw_event(), HID feature reports are ignored but are
still marked as processed. This causes the in-kernel struct not to be
updated. Any non-updated fields in the feature reports are zero, and
they are being sent to the device. This
