2014-07-24 03:23:23 +08:00
|
|
|
Atmel maXTouch touchscreen/touchpad
|
|
|
|
|
|
|
|
|
|
Required properties:
|
|
|
|
|
- compatible:
|
|
|
|
|
atmel,maxtouch
|
|
|
|
|
|
2018-05-02 02:44:53 +08:00
|
|
|
The following compatibles have been used in various products but are
|
|
|
|
|
deprecated:
|
|
|
|
|
atmel,qt602240_ts
|
|
|
|
|
atmel,atmel_mxt_ts
|
|
|
|
|
atmel,atmel_mxt_tp
|
|
|
|
|
atmel,mXT224
|
|
|
|
|
|
2014-07-24 03:23:23 +08:00
|
|
|
- reg: The I2C address of the device
|
|
|
|
|
|
|
|
|
|
- interrupts: The sink for the touchpad's IRQ output
|
|
|
|
|
See ../interrupt-controller/interrupts.txt
|
|
|
|
|
|
|
|
|
|
Optional properties for main touchpad device:
|
|
|
|
|
|
2014-08-18 00:08:42 +08:00
|
|
|
- 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.
|
|
|
|
|
|
2017-07-26 05:11:34 +08:00
|
|
|
- reset-gpios: GPIO specifier for the touchscreen's reset pin (active low)
|
|
|
|
|
|
2014-07-24 03:23:23 +08:00
|
|
|
Example:
|
|
|
|
|
|
|
|
|
|
touch@4b {
|
|
|
|
|
compatible = "atmel,maxtouch";
|
|
|
|
|
reg = <0x4b>;
|
|
|
|
|
interrupt-parent = <&gpio>;
|
|
|
|
|
interrupts = <TEGRA_GPIO(W, 3) IRQ_TYPE_LEVEL_LOW>;
|
|
|
|
|
};
|
