Device Drivers -> Input device support -> Touchscreens -> Goodix I2C touchscreen Most failures occur because the device tree doesn't pass the correct resolution. Here is a reliable device tree snippet for a GT911 on an i.MX6UL with a 1024x600 LVDS screen:
&i2c2 clock-frequency = <400000>; pinctrl-names = "default"; status = "okay"; goodix_ts@5d compatible = "goodix,gt911"; reg = <0x5d>; interrupt-parent = <&gpio1>; interrupts = <9 IRQ_TYPE_EDGE_FALLING>; reset-gpios = <&gpio1 8 GPIO_ACTIVE_HIGH>; irq-gpios = <&gpio1 9 GPIO_ACTIVE_HIGH>; touchscreen-size-x = <1024>; touchscreen-size-y = <600>; touchscreen-inverted-x = <0>; touchscreen-inverted-y = <0>; ; ; gt9xx-1024x600
Introduction: Decoding the GT9XX-1024x600 In the world of embedded systems and Human-Machine Interfaces (HMI), few components are as critical as the touchscreen controller. Among the myriad of part numbers and specifications, one string stands out for developers working on mid-to-large-scale LCD projects: gt9xx-1024x600 . Device Drivers -> Input device support -> Touchscreens
This alphanumeric code is not just a random label. It represents a marriage between a powerful touch controller family (GT9XX, typically from Goodix) and a specific display resolution (1024x600, also known as WSVGA). Whether you are building a smart home control panel, an industrial PLC interface, a car infotainment system, or a custom Raspberry Pi tablet, understanding the GT9XX-1024x600 combo is essential. This alphanumeric code is not just a random label