On 06/12/2014 05:25 AM, Nick Dyer wrote: > Stephen Warren wrote: >>> I will test this on my setup and see if I can figure out what is causing >>> the problem. >> >> Nick, did you get anywhere reproducing my problem? Unfortunately with >> your recent patches merged, I can't get the touchpad working at all, >> whereas before I had a few simple patches that made it work:-( > > I haven't been able to reproduce your issue, I have a devicetree based > system that will successfully probe without a config file. > > Could you send me the dmesg output with all of the driver debug enabled? It > would be good to see how far it is getting. My apologies; I should have retested before asking about this again. I guess something must have changed in linux-next since the last time I tested this. With next-20140611 plus the following patches on top: d3168ccd7d57 ARM: tegra: enable Atmel touchpad in defconfig fc1d7c4aefe0 ARM: tegra: add touchpad to Venice2 DT da5f283a52ea Input: atmel_mxt_ts: implement device tree parsing 22911ed92e76 Input: atmel_mxt_ts: define a device tree binding 57f79f65a8f9 Input: atmel_mxt_ts - Set pointer emulation on touchpads ... the driver built into the kernel, and no firmware available in /lib/firmware, the touchpad now works. Are you still expecting to take my DT binding patches above and resend them? One bug I see is that the mouse doesn't seem to release when I drag it (either through double clicking and holding on the second click, or by a two-finger drag). Is that a known issue? -- 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
