On Tue, 17 Feb 2015, Benjamin Tissoires wrote:
On Tue, Feb 17, 2015 at 5:36 PM, Ping Cheng pingli...@gmail.com wrote:
On Tue, Feb 17, 2015 at 11:19 AM, Benjamin Tissoires
benjamin.tissoi...@redhat.com wrote:
input_mt_sync_frame() calls input_mt_report_pointer_emulation() and do
some
On Tue, Feb 17, 2015 at 5:36 PM, Ping Cheng pingli...@gmail.com wrote:
On Tue, Feb 17, 2015 at 11:19 AM, Benjamin Tissoires
benjamin.tissoi...@redhat.com wrote:
input_mt_sync_frame() calls input_mt_report_pointer_emulation() and do
some internal steps required to keep in sync the state of the
input_mt_sync_frame() calls input_mt_report_pointer_emulation() and do
some internal steps required to keep in sync the state of the touch within
the various reports.
Given that we use input_mt_assign_slot() in this driver, it is better to
use input_mt_sync_frame().
Signed-off-by: Benjamin
On Tue, Feb 17, 2015 at 11:19 AM, Benjamin Tissoires
benjamin.tissoi...@redhat.com wrote:
input_mt_sync_frame() calls input_mt_report_pointer_emulation() and do
some internal steps required to keep in sync the state of the touch within
the various reports.
Given that we use
