On Mon, 16 Mar 2015, Pavel Machek wrote: > On Mon 2015-03-16 13:55:39, Jiri Kosina wrote: > > On Sat, 14 Mar 2015, Pavel Machek wrote: > > > > > Hi! > > > > > > After oopsing kernel with ps/3 peripherals, I decided to play some > > > more. > > > > > > First "sony motion controller" (part of ps/3 move without the > > > led). Good news is that it no longer oopses. After pressing the PS > > > button, it seems to work, but it produces endless stream of events in > > > evtest: > > > > > > Event: time 1426360519.967818, type 3 (EV_ABS), code 0 (ABS_X), value 131 > > > Event: time 1426360519.967818, type 3 (EV_ABS), code 1 (ABS_Y), value 129 > > > Event: time 1426360519.967818, type 3 (EV_ABS), code 59 (ABS_MT_DISTANCE), value 513 > > > Event: time 1426360519.967818, type 3 (EV_ABS), code 60 (ABS_MT_TOOL_X), value 513 > > > > > > Should it really produce multitouch events? > > > > Some sony devices are producing multitouch events. You unfortunately > > didn't send us the VID/PID of the device you are playing with. > > Umm. I thought multitouch events are for touchscreen. This is joystick > with accelerometer...? Ok, that's USB_DEVICE_ID_SONY_NAVIGATION_CONTROLLER, which should get SIXAXIS_CONTROLLER_USB. That one shouldn't really be producing multitouch events. Could you please add printk()s to hid-sony.c to see how it's possible that it's generating those? I am sure Frank will comment on this as well. -- Jiri Kosina SUSE Labs -- To unsubscribe from this list: send the line "unsubscribe linux-input" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
