1*4882a593SmuzhiyunAtmel maXTouch touchscreen/touchpad 2*4882a593Smuzhiyun 3*4882a593SmuzhiyunRequired properties: 4*4882a593Smuzhiyun- compatible: 5*4882a593Smuzhiyun atmel,maxtouch 6*4882a593Smuzhiyun 7*4882a593Smuzhiyun The following compatibles have been used in various products but are 8*4882a593Smuzhiyun deprecated: 9*4882a593Smuzhiyun atmel,qt602240_ts 10*4882a593Smuzhiyun atmel,atmel_mxt_ts 11*4882a593Smuzhiyun atmel,atmel_mxt_tp 12*4882a593Smuzhiyun atmel,mXT224 13*4882a593Smuzhiyun 14*4882a593Smuzhiyun- reg: The I2C address of the device 15*4882a593Smuzhiyun 16*4882a593Smuzhiyun- interrupts: The sink for the touchpad's IRQ output 17*4882a593Smuzhiyun See ../interrupt-controller/interrupts.txt 18*4882a593Smuzhiyun 19*4882a593SmuzhiyunOptional properties for main touchpad device: 20*4882a593Smuzhiyun 21*4882a593Smuzhiyun- linux,gpio-keymap: When enabled, the SPT_GPIOPWN_T19 object sends messages 22*4882a593Smuzhiyun on GPIO bit changes. An array of up to 8 entries can be provided 23*4882a593Smuzhiyun indicating the Linux keycode mapped to each bit of the status byte, 24*4882a593Smuzhiyun starting at the LSB. Linux keycodes are defined in 25*4882a593Smuzhiyun <dt-bindings/input/input.h>. 26*4882a593Smuzhiyun 27*4882a593Smuzhiyun Note: the numbering of the GPIOs and the bit they start at varies between 28*4882a593Smuzhiyun maXTouch devices. You must either refer to the documentation, or 29*4882a593Smuzhiyun experiment to determine which bit corresponds to which input. Use 30*4882a593Smuzhiyun KEY_RESERVED for unused padding values. 31*4882a593Smuzhiyun 32*4882a593Smuzhiyun- reset-gpios: GPIO specifier for the touchscreen's reset pin (active low) 33*4882a593Smuzhiyun 34*4882a593SmuzhiyunExample: 35*4882a593Smuzhiyun 36*4882a593Smuzhiyun touch@4b { 37*4882a593Smuzhiyun compatible = "atmel,maxtouch"; 38*4882a593Smuzhiyun reg = <0x4b>; 39*4882a593Smuzhiyun interrupt-parent = <&gpio>; 40*4882a593Smuzhiyun interrupts = <TEGRA_GPIO(W, 3) IRQ_TYPE_LEVEL_LOW>; 41*4882a593Smuzhiyun }; 42