Re: [PATCH 2/2] Input: atmel_mxt_ts - Add keycodes array example
From: Javier Martinez Canillas <hidden>
Date: 2014-08-18 13:20:14
Also in:
linux-devicetree, linux-samsung-soc, lkml
From: Javier Martinez Canillas <hidden>
Date: 2014-08-18 13:20:14
Also in:
linux-devicetree, linux-samsung-soc, lkml
Hello Nick, On 08/15/2014 06:08 PM, Nick Dyer wrote:
quoted
Any comments on this? I would really appreciate if you can expand on how this DT property is supposed to be used so I can re-spin the atmel support patch for Peach boards.The below patch improves the documentation for the gpio-property. Stephen Warren has a good example here: https://github.com/swarren/linux-tegra/commit/09789801 trackpad@4b { compatible = "atmel,maxtouch"; reg = <0x4b>; interrupt-parent = <&gpio>; interrupts = <TEGRA_GPIO(W, 3) IRQ_TYPE_LEVEL_LOW>; linux,gpio-keymap = <0 0 0 BTN_LEFT>; }; This maps BTN_LEFT to the 4th bit of the T19 message. I haven't looked up what GPIO number that corresponds to on the mXT224SL that he has, it varies with the particular maXTouch device you have. Hope this helps.
Thanks a lot for the patch and the pointer to Stephen's DTS. I'll do some experimentation then to figure out the right values since I don't have proper documentation. Fortunately the Chrome OS 3.8 downstream driver works on -next so I can use evdev to compare if both drivers behave the same.
Signed-off-by: Nick Dyer <redacted>
Best regards, Javier