[PATCH] make ektf3k driver report non-MT events too

Seth Forshee seth.forshee at canonical.com
Fri Aug 9 13:59:07 UTC 2013


On Fri, Aug 09, 2013 at 01:46:14AM -0400, Matt Whitlock wrote:
> On Thursday, 8 August 2013, at 1:49 pm, Seth Forshee wrote:
> > On Wed, Aug 07, 2013 at 01:51:12PM -0400, Matt Whitlock wrote:
> > > Joseph Salisbury requested that I submit this patch to the Ubuntu Kernel Team mailing list for review.
> > > 
> > > > This patch resolves a shortcoming of the ektf3k driver. Previously, the
> > > > driver was reporting only multi-touch events. xf86-input-evdev 2.7.3
> > > > crashes upon receiving input events from [that] driver, and 2.8.1 simply
> > > > ignores the input device altogether as a workaround for the crash.
> > > > 
> > > > This patch adds single-touch ABS_X, ABS_Y, and ABS_PRESSURE axes, as well as
> > > > the BTN_TOUCH key. Only the first finger touching reports on these
> > > > single-touch axes (while continuing to report on the multi-touch axes);
> > > > additional fingers report only on the multi-touch axes.
> > > > 
> > > > I have tested this patch on a Nexus 7 running X.org server 1.13.4 and
> > > > xf86-input-evdev 2.8.1. Without the patch, evdev ignores all input from the
> > > > touchscreen. With the patch, evdev generates mouse events in response to
> > > > touches, as one would expect.
> > > 
> > > https://bugs.launchpad.net/ubuntu/+source/linux-grouper/+bug/1209049
> > 
> > input_mt_report_pointer_emulation() exists for exactly this purpose, so
> > it would be preferable to use that instead.
> 
> Thanks for the pointer, Seth.  I am not too familiar with the kernel input layer.  I've adjusted my patch and confirmed that it still works as intended.  See the Launchpad bug or the attached.

Great, thanks! A few more things though.

First, I realize the indentation of that driver is already a mess, but
it would improve readability if you'd make your indentation match that
of the surrounding lines.

Second, there are two other places in the file with report MT data.
Shouldn't those places also be making this call?

And as Tim indicated, we require sign-offs to establish who authored the
patch. Our general patch submission process is documented at
https://wiki.ubuntu.com/Kernel/Dev/KernelPatches (in this case upstream
submission doesn't make sense, but we use the same format and sign-off
policy as upstream). Here's a recent example of a correctly formatted
patch for grouper that you can refer to:
https://lists.ubuntu.com/archives/kernel-team/2013-August/031399.html




More information about the kernel-team mailing list