Driver for AUO In-Cell touchscreens using pixcir ICs
Subsystems (2)
PATCH v3 1/1 Driver for AUO In-Cell touchscreens using pixcir ICs
Some displays from AUO have a so called in-cell touchscreen, meaning it is built directly into the display unit.
Touchdata is gathered through PIXCIR Tango-ICs and processed in an Atmel ATmega168P with custom firmware. Communication between the host system and ATmega is done via I2C.
Devices using this touch solution include the Dell Streak5 and the family of Qisda ebook readers.
The driver reports single- and multi-touch events including touch area values.
---
changes since v2: address comments from Dmitry Torokhov especially suspend/resume handling
changes since v1: address comments from Christoph Fritz (wrong type for error checks, wrong call to input_free_device)
drivers/input/touchscreen/Kconfig | 13 + drivers/input/touchscreen/Makefile | 1 + drivers/input/touchscreen/auo-pixcir-ts.c | 654 +++++++++++++++++++++++++++++ include/linux/input/auo-pixcir-ts.h | 56 +++ 4 files changed, 724 insertions(+), 0 deletions(-) create mode 100644 drivers/input/touchscreen/auo-pixcir-ts.c create mode 100644 include/linux/input/auo-pixcir-ts.h
drivers/input/touchscreen/Kconfig +13 -0
@@ -98,6 +98,19 @@ config TOUCHSCREEN_ATMEL_MXT To compile this driver as a module, choose M here: the module will be called atmel_mxt_ts. +config TOUCHSCREEN_AUO_PIXCIR + tristate "AUO in-cell touchscreen using Pixcir ICs" + depends on I2C + depends on GPIOLIB + help + Say Y here if you have a AUO display with in-cell touchscreen + using Pixcir ICs. + + If unsure, say N. + + To compile this driver as a module, choose M here: the + module will be called auo-pixcir-ts. + config TOUCHSCREEN_BITSY tristate "Compaq iPAQ H3600 (Bitsy) touchscreen" depends on SA1100_BITSY
drivers/input/touchscreen/Makefile +1 -0
@@ -14,6 +14,7 @@ obj-$(CONFIG_TOUCHSCREEN_AD7879_SPI) += ad7879-spi.o obj-$(CONFIG_TOUCHSCREEN_ADS7846) += ads7846.o obj-$(CONFIG_TOUCHSCREEN_ATMEL_MXT) += atmel_mxt_ts.o obj-$(CONFIG_TOUCHSCREEN_ATMEL_TSADCC) += atmel_tsadcc.o +obj-$(CONFIG_TOUCHSCREEN_AUO_PIXCIR) += auo-pixcir-ts.o obj-$(CONFIG_TOUCHSCREEN_BITSY) += h3600_ts_input.o obj-$(CONFIG_TOUCHSCREEN_BU21013) += bu21013_ts.o obj-$(CONFIG_TOUCHSCREEN_CY8CTMG110) += cy8ctmg110_ts.o
drivers/input/touchscreen/auo-pixcir-ts.c new file +654 -0
654 lines not on this page · raw message
include/linux/input/auo-pixcir-ts.h new file +56 -0
56 lines not on this page · raw message
Signature · 1 line
1.7.2.3
Hi Dmitry,
Am Mittwoch, 7. Dezember 2011, 23:48:04 schrieb Heiko Stübner:
Quoted 13 lines
Some displays from AUO have a so called in-cell touchscreen, meaning it is built directly into the display unit.
Touchdata is gathered through PIXCIR Tango-ICs and processed in an Atmel ATmega168P with custom firmware. Communication between the host system and ATmega is done via I2C.
Devices using this touch solution include the Dell Streak5 and the family of Qisda ebook readers.
The driver reports single- and multi-touch events including touch area values.
Quoted 7 lines
Signed-off-by Heiko Stuebner <[email protected]>---
changes since v2: address comments from Dmitry Torokhov especially suspend/resume handlingchanges since v1: address comments from Christoph Fritz (wrong type for error checks, wrong call to
input_free_device)
ping for this?
As I wrote in the other thread, the device is not capable of tracking the individual fingers, so this v3 should hopefully address all your comments.
Heiko
--
To unsubscribe from this list: send the line "unsubscribe linux-input" in the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Am Dienstag, 13. Dezember 2011, 11:03:19 schrieb Heiko Stübner:
Quoted 21 lines
Hi Dmitry,
Am Mittwoch, 7. Dezember 2011, 23:48:04 schrieb Heiko Stübner:
Quoted 18 lines
Some displays from AUO have a so called in-cell touchscreen, meaning it is built directly into the display unit.
Touchdata is gathered through PIXCIR Tango-ICs and processed in an Atmel ATmega168P with custom firmware. Communication between the host system and ATmega is done via I2C.
Devices using this touch solution include the Dell Streak5 and the family of Qisda ebook readers.
The driver reports single- and multi-touch events including touch area values.
Signed-off-by Heiko Stuebner <[email protected]>---
changes since v2: address comments from Dmitry Torokhov especially suspend/resume handling
Quoted 7 lines
Quoted 2 lines
changes since v1: address comments from Christoph Fritz (wrong type for error checks, wrong call to
input_free_device)ping for this?
As I wrote in the other thread, the device is not capable of tracking the individual fingers, so this v3 should hopefully address all your comments.
another ping :-)
Heiko
--
To unsubscribe from this list: send the line "unsubscribe linux-input" in the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Quoted 7 lines · Heiko Stübner
Some displays from AUO have a so called in-cell touchscreen, meaning it is built directly into the display unit.
Touchdata is gathered through PIXCIR Tango-ICs and processed in an Atmel ATmega168P with custom firmware. Communication between the host system and ATmega is done via I2C.
Quoted 6 lines
Devices using this touch solution include the Dell Streak5 and the family of Qisda ebook readers.
The driver reports single- and multi-touch events including touch area values.
Applied, thank you Heiko.
Signature · 5 lines
Dmitry -- To unsubscribe from this list: send the line "unsubscribe linux-input" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html