path: root/dts/Bindings/input
diff options
authorSascha Hauer <>2014-09-16 07:37:58 +0200
committerSascha Hauer <>2014-09-16 07:37:58 +0200
commit550b05766e2768638463ff2a52612d65fa6cd6a4 (patch)
tree1348d24d287d86275fba040045c1d1b4a80e36b5 /dts/Bindings/input
parent48199fd57c38e6acd63213334ef86119e16496c7 (diff)
dts: update to v3.17-rc5
Signed-off-by: Sascha Hauer <>
Diffstat (limited to 'dts/Bindings/input')
1 files changed, 11 insertions, 0 deletions
diff --git a/dts/Bindings/input/atmel,maxtouch.txt b/dts/Bindings/input/atmel,maxtouch.txt
index baef432e83..0ac23f2ed1 100644
--- a/dts/Bindings/input/atmel,maxtouch.txt
+++ b/dts/Bindings/input/atmel,maxtouch.txt
@@ -15,6 +15,17 @@ Optional properties for main touchpad device:
keycode generated by each GPIO. Linux keycodes are defined in
+- linux,gpio-keymap: When enabled, the SPT_GPIOPWN_T19 object sends messages
+ on GPIO bit changes. An array of up to 8 entries can be provided
+ indicating the Linux keycode mapped to each bit of the status byte,
+ starting at the LSB. Linux keycodes are defined in
+ <dt-bindings/input/input.h>.
+ Note: the numbering of the GPIOs and the bit they start at varies between
+ maXTouch devices. You must either refer to the documentation, or
+ experiment to determine which bit corresponds to which input. Use
+ KEY_RESERVED for unused padding values.
touch@4b {