An error occurred fetching the project authors.
- 19 Sep, 2017 1 commit
-
-
Robert Jarzmik authored
This adds support for the new AC97 bus code, which discovers the devices rather than uses platform data. As part of this discovery, it enables a multi-function device wm97xx, which supports touchscreen, battery, ADC and an audio codec. This patch adds the code to bind the touchscreen "cell" as the touchscreen driver. This was tested on the pxa architecture with a pxa270 + wm9713 + the mioa701 touchscreen. Signed-off-by:
Robert Jarzmik <robert.jarzmik@free.fr> Acked-by:
Charles Keepax <ckeepax@opensource.wolfsonmicro.com> Acked-by:
Dmitry Torokhov <dmitry.torokhov@gmail.com> Signed-off-by:
Mark Brown <broonie@kernel.org>
-
- 05 Jun, 2017 1 commit
-
-
Andi Shyti authored
The stmfts (ST-Microelectronics FingerTip S) touchscreen device is a capacitive multi-touch controller mainly for mobile use. It's connected through i2c bus at the address 0x49 and it interfaces with userspace through input event interface. At the current state it provides a touchscreen multitouch functionality up to 10 fingers. Each finger is enumerated with a distinctive id (from 0 to 9). If enabled the device can support single "touch" hovering, by providing three coordinates, x, y and distance. It is possible to select the touchkey functionality which provides a basic two keys interface for "home" and "back" menu, typical in mobile phones. Signed-off-by:
Andi Shyti <andi.shyti@samsung.com> Reviewed-by:
Javier Martinez Canillas <javier@osg.samsung.com> Acked-by:
Rob Herring <robh@kernel.org> Signed-off-by:
Dmitry Torokhov <dmitry.torokhov@gmail.com>
-
- 14 Apr, 2017 1 commit
-
-
Martin Kepplinger authored
ar1021_i2c also supports the ar1020 device I'm using. This is tested. They also share the same datasheet: http://ww1.microchip.com/downloads/en/DeviceDoc/40001393C.pdf So let users see that they have a compatible in front of them by adding AR1020 to the driver's description. Signed-off-by:
Martin Kepplinger <martin.kepplinger@ginzinger.com> Signed-off-by:
Dmitry Torokhov <dmitry.torokhov@gmail.com>
-
- 23 Mar, 2017 1 commit
-
-
Ksenija Stanojevic authored
Add 4-wire/5-wire touchscreen controller. Signed-off-by:
Ksenija Stanojevic <ksenija.stanojevic@gmail.com> Acked-by:
Dmitry Torokhov <dmitry.torokhov@gmail.com> Reviewed-by:
Marek Vasut <marex@denx.de> Signed-off-by:
Lee Jones <lee.jones@linaro.org>
-
- 23 Feb, 2017 1 commit
-
-
Dmitry Torokhov authored
Instead of rolling our own infrastructure to provide uniform access to I2C and SPI buses, let's switch to using regmap. Reviewed-by:
Michael Hennerich <michael.hennerich@analog.com> Tested-by:
Michael Hennerich <michael.hennerich@analog.com> Signed-off-by:
Dmitry Torokhov <dmitry.torokhov@gmail.com>
-
- 17 Feb, 2017 1 commit
-
-
H. Nikolaus Schaller authored
The tsc2007 chip not only has a resistive touch screen controller but also an external AUX adc imput which can be used for an ambient light sensor, battery voltage monitoring or any general purpose. Additionally it can measure the chip temperature. This extension provides an iio interface for these adc channels. Since it is not wasting much resources and is very straightforward, we simply provide all other adc channels as optional iio interfaces as weel. This can be used for debugging or special applications. This patch also splits the tsc2007 driver in several source files: tsc2007.h -- constants, structs and stubs tsc2007_core.c -- functional parts of the original driver tsc2007_iio.c -- the optional iio stuff Makefile magic allows to conditionally link the iio stuff if CONFIG_IIO=y or =m in a way that it works with CONFIG_TOUCHSCREEN_TSC2007=m. Signed-off-by:
H. Nikolaus Schaller <hns@goldelico.com> Reviewed-by:
Jonathan Cameron <jic23@kernel.org> Signed-off-by:
Dmitry Torokhov <dmitry.torokhov@gmail.com>
-
- 09 Feb, 2017 1 commit
-
-
Jelle van der Waa authored
This is a basic driver for the Zeitec ZET6223 I2C touchscreen controllers. The driver does not support firmware loading, which is not required for all tablets which contain this chip. Signed-off-by:
Jelle van der Waa <jelle@vdwaa.nl> Acked-by:
Rob Herring <robh@kernel.org> Signed-off-by:
Dmitry Torokhov <dmitry.torokhov@gmail.com>
-
- 06 Jan, 2017 1 commit
-
-
Andy Shevchenko authored
The Moorestown support was removed by commit 1a8359e4 ("x86/mid: Remove Intel Moorestown"). Remove this leftover. Signed-off-by:
Andy Shevchenko <andriy.shevchenko@linux.intel.com> Signed-off-by:
Dmitry Torokhov <dmitry.torokhov@gmail.com>
-
- 27 Sep, 2016 1 commit
-
-
Siebren Vroegindeweij authored
This adds a driver for the Elan eKTF2127 touchscreen controller, which speaks an i2c protocol which is distinctly different from the already supported eKTH controllers. Signed-off-by:
Michel Verlaan <michel.verl@gmail.com> Signed-off-by:
Siebren Vroegindeweij <siebren.vroegindeweij@hotmail.com> Signed-off-by:
Hans de Goede <hdegoede@redhat.com> Acked-by:
Rob Herring <robh@kernel.org> Signed-off-by:
Dmitry Torokhov <dmitry.torokhov@gmail.com>
-
- 19 Sep, 2016 1 commit
-
-
Arnd Bergmann authored
The newnly added debug mode for the atmel_mxt_ts driver relies on the v4l2 interface and vb2_vmalloc, but those might be configured as loadable modules when the driver itself is built-in, resulting in a link failure: drivers/input/touchscreen/atmel_mxt_ts.o: In function `mxt_vidioc_querycap': atmel_mxt_ts.c:(.text.mxt_vidioc_querycap+0x10): undefined reference to `video_devdata' drivers/input/touchscreen/atmel_mxt_ts.o: In function `mxt_buffer_queue': atmel_mxt_ts.c:(.text.mxt_buffer_queue+0x20): undefined reference to `vb2_plane_vaddr' atmel_mxt_ts.c:(.text.mxt_buffer_queue+0x164): undefined reference to `vb2_buffer_done' drivers/input/touchscreen/atmel_mxt_ts.o: In function `mxt_free_object_table': atmel_mxt_ts.c:(.text.mxt_free_object_table+0x18): undefined reference to `video_unregister_device' atmel_mxt_ts.c:(.text.mxt_free_object_table+0x20): undefined reference to `v4l2_device_unregister' The best workaround I could come up with is to disallow the debug mode unless it's actually possible to call it. Fixes: ecfdd7e2 ("[media] Input: atmel_mxt_ts - output diagnostic debug via V4L2 device") Signed-off-by:
Arnd Bergmann <arnd@arndb.de> Acked-by:
Nick Dyer <nick@shmanahar.org> Signed-off-by:
Hans Verkuil <hans.verkuil@cisco.com> Signed-off-by:
Mauro Carvalho Chehab <mchehab@s-opensource.com>
-
- 23 Aug, 2016 2 commits
-
-
Nick Dyer authored
Register a video device to output T37 diagnostic data. Signed-off-by:
Nick Dyer <nick@shmanahar.org> Signed-off-by:
Hans Verkuil <hans.verkuil@cisco.com> Signed-off-by:
Mauro Carvalho Chehab <mchehab@s-opensource.com> Acked-by:
Dmitry Torokhov <dmitry.torokhov@gmail.com>
-
Nick Dyer authored
Atmel maXTouch devices have a T37 object which can be used to read raw touch deltas from the device. This consists of an array of 16-bit integers, one for each node on the touchscreen matrix. Signed-off-by:
Nick Dyer <nick@shmanahar.org> Signed-off-by:
Hans Verkuil <hans.verkuil@cisco.com> Signed-off-by:
Mauro Carvalho Chehab <mchehab@s-opensource.com> Acked-by:
Dmitry Torokhov <dmitry.torokhov@gmail.com>
-
- 22 Aug, 2016 1 commit
-
-
Hans de Goede authored
The new(ish) ft6236 simply re-implements the M09 protocol of the (much) older edt-ft5x06.c driver. This commit removes this duplicate driver and adds the i2c ids and dt compatible string to the edt-ft5x06.c driver to keep compatibility. This commit also adds the standard touchscreen properties as optional properties to the edt,ft5x06 binding, these were documented in the focaltech,ft6236 bindingi, but were missing from the edt,ft5x06 doc. Signed-off-by:
Hans de Goede <hdegoede@redhat.com> Acked-by:
Rob Herring <robh@kernel.org> Signed-off-by:
Dmitry Torokhov <dmitry.torokhov@gmail.com>
-
- 04 Aug, 2016 1 commit
-
-
Arnd Bergmann authored
The newly added sis_i2c driver fails to link without the CRC_ITU_T driver enabled: drivers/input/touchscreen/sis_i2c.o: In function `sis_ts_irq_handler': sis_i2c.c:(.text+0xc0): undefined reference to `crc_itu_t' This adds a Kconfig select statement. Signed-off-by:
Arnd Bergmann <arnd@arndb.de> Fixes: a485cb03 ("Input: add driver for SiS 9200 family I2C touchscreen controllers") Signed-off-by:
Dmitry Torokhov <dmitry.torokhov@gmail.com>
-
- 03 Aug, 2016 2 commits
-
-
Mika Penttilä authored
This is a driver for SiS 9200 family touchscreen controllers using I2C bus. Signed-off-by:
Mika Penttilä <mika.penttila@nextfour.com> Acked-by:
Tammy Tseng <tammy_tseng@sis.com> Acked-by:
Yuger Yu <yuger_yu@sis.com> Signed-off-by:
Dmitry Torokhov <dmitry.torokhov@gmail.com>
-
Robert Dolca authored
This driver adds support for Silead touchscreens. It has been tested with GSL1680 and GSL3680 touch panels. It supports ACPI and device tree enumeration. Screen resolution, the maximum number of fingers supported and firmware name are configurable. Signed-off-by:
Robert Dolca <robert.dolca@intel.com> Signed-off-by:
Daniel Jansen <djaniboe@gmail.com> Signed-off-by:
Hans de Goede <hdegoede@redhat.com> Signed-off-by:
Dmitry Torokhov <dmitry.torokhov@gmail.com>
-
- 28 May, 2016 1 commit
-
-
Jeffrey Lin authored
This adds support for Raydium I2C touch controllers compatible with RM32380. Signed-off-by:
Jeffrey Lin <jeffrey.lin@rad-ic.com> Acked-by:
Rob Herring <robh@kernel.org> Signed-off-by:
Dmitry Torokhov <dmitry.torokhov@gmail.com>
-
- 19 May, 2016 1 commit
-
-
Benjamin Tissoires authored
This is a basic driver for the Surface 3. I am not so sure it will work with any firmwares as most values are encoded, but given that I only have access to my current device with its firmware and I don't have the datasheet, it should be OK for now. The Surface Pen is not supported (if it is supposed to be). I'll work on this when I get one. Tested-by:
Bastien Nocera <hadess@hadess.net> Signed-off-by:
Benjamin Tissoires <benjamin.tissoires@redhat.com> Signed-off-by:
Dmitry Torokhov <dmitry.torokhov@gmail.com>
-
- 18 May, 2016 1 commit
-
-
Javier Martinez Canillas authored
The driver only has runtime but no build time dependency with SH_MIGOR, so it can be built for testing purposes if the COMPILE_TEST option is enabled. This is useful to have more build coverage and make sure that drivers are not affected by changes that could cause build regressions. Signed-off-by:
Javier Martinez Canillas <javier@osg.samsung.com> Signed-off-by:
Dmitry Torokhov <dmitry.torokhov@gmail.com>
-
- 04 Mar, 2016 1 commit
-
-
Jean Delvare authored
The Technologic Systems TS-4800 is an i.MX515 board, so its drivers are useless unless building a SOC_IMX51 kernel, except for build testing purposes. Signed-off-by:
Jean Delvare <jdelvare@suse.de> Signed-off-by:
Dmitry Torokhov <dmitry.torokhov@gmail.com>
-
- 17 Feb, 2016 1 commit
-
-
Sangwon Jee authored
This is an input driver for MELFAS MIP4 Touchscreen devices, such as MMS400, MMS500, MCS8000, MIT200, MIT300, MIT400, MFS10. All devices implementing MIP4 protocol (MELFAS Interface Protocol Version 4) should be supported by this driver. Signed-off-by:
Sangwon Jee <jeesw@melfas.com> Signed-off-by:
Dmitry Torokhov <dmitry.torokhov@gmail.com>
-
- 11 Feb, 2016 1 commit
-
-
Markus Pargmann authored
This is a driver for the imx25 ADC/TSC module. It controls the touchscreen conversion queue and creates a touchscreen input device. The driver currently only supports 4 wire touchscreens. The driver uses a simple conversion queue of precharge, touch detection, X measurement, Y measurement, precharge and another touch detection. This driver uses the regmap from the parent to setup some touch specific settings in the core driver and setup a idle configuration with touch detection. Signed-off-by:
Markus Pargmann <mpa@pengutronix.de> Signed-off-by:
Denis Carikli <denis@eukrea.com> [fix clock's period calculation] [fix calculation of the 'settling' value] Signed-off-by:
Juergen Borleis <jbe@pengutronix.de> Acked-by:
Dmitry Torokhov <dmitry.torokhov@gmail.com> Signed-off-by:
Lee Jones <lee.jones@linaro.org>
-
- 09 Feb, 2016 1 commit
-
-
Geert Uytterhoeven authored
The GPIO subsystem provides dummy GPIO consumer functions if GPIOLIB is not enabled. Hence drivers that depend on GPIOLIB, but use GPIO consumer functionality only, can still be compiled if GPIOLIB is not enabled. If COMPILE_TEST is enabled, relax the dependency on GPIOLIB for the recently introduced or relaxed symbols TOUCHSCREEN_GOODIX and TOUCHSCREEN_COLIBRI_VF50. Signed-off-by:
Geert Uytterhoeven <geert@linux-m68k.org> Signed-off-by:
Dmitry Torokhov <dmitry.torokhov@gmail.com>
-
- 18 Dec, 2015 1 commit
-
-
Irina Tirdea authored
After power on, it is recommended that the driver resets the device. The reset procedure timing is described in the datasheet and is used at device init (before writing device configuration) and for power management. It is a sequence of setting the interrupt and reset pins high/low at specific timing intervals. This procedure also includes setting the slave address to the one specified in the ACPI/device tree. This is based on Goodix datasheets for GT911 and GT9271 and on Goodix driver gt9xx.c for Android (publicly available in Android kernel trees for various devices). For reset the driver needs to control the interrupt and reset gpio pins (configured through ACPI/device tree). For devices that do not have the gpio pins properly declared, the functionality depending on these pins will not be available, but the device can still be used with basic functionality. For both device tree and ACPI, the interrupt gpio pin configuration is read from the "irq-gpios" property and the reset pin configuration is read from the "reset-gpios" property. For ACPI 5.1, named properties can be specified using the _DSD section. This functionality will not be available for devices that use indexed gpio pins declared in the _CRS section (we need to provide backward compatibility with devices that do not support using the interrupt gpio pin as output). For ACPI, the pins can be specified using ACPI 5.1: Device (STAC) { Name (_HID, "GDIX1001") ... Method (_CRS, 0, Serialized) { Name (RBUF, ResourceTemplate () { I2cSerialBus (0x0014, ControllerInitiated, 0x00061A80, AddressingMode7Bit, "\\I2C0", 0x00, ResourceConsumer, , ) GpioInt (Edge, ActiveHigh, Exclusive, PullNone, 0x0000, "\\I2C0", 0x00, ResourceConsumer, , ) { // Pin list 0 } GpioIo (Exclusive, PullDown, 0x0000, 0x0000, IoRestrictionOutputOnly, "\\I2C0", 0x00, ResourceConsumer, , ) { 1 } }) Return (RBUF) } Name (_DSD, Package () { ToUUID("daffd814-6eba-4d8c-8a91-bc9bbf4aa301"), Package () { Package (2) {"irq-gpios", Package() {^STAC, 0, 0, 0 }}, Package (2) {"reset-gpios", Package() {^STAC, 1, 0, 0 }}, ... } } Signed-off-by:
Octavian Purdila <octavian.purdila@intel.com> Signed-off-by:
Irina Tirdea <irina.tirdea@intel.com> Acked-by:
Rob Herring <robh@kernel.org> Acked-by:
Bastien Nocera <hadess@hadess.net> Tested-by:
Bastien Nocera <hadess@hadess.net> Tested-by:
Aleksei Mamlin <mamlinav@gmail.com> Signed-off-by:
Dmitry Torokhov <dmitry.torokhov@gmail.com>
-
- 16 Dec, 2015 2 commits
-
-
Damien Riegel authored
On this board, the touchscreen, an ads7843, is not handled directly by Linux but by a companion FPGA. This FPGA is memory-mapped and the IP design is very similar to the mk712. This commit adds the support for this IP. Signed-off-by:
Damien Riegel <damien.riegel@savoirfairelinux.com> Acked-by:
Rob Herring <robh@kernel.org> Signed-off-by:
Dmitry Torokhov <dmitry.torokhov@gmail.com>
-
Böszörményi Zoltán authored
There are two EETI touchscreen drivers in the kernel (eeti_ts and egalax_ts) but both are for I2C-connected panels. This is for a different, serial and not multi-touch touchscreen panel. The protocol documentation is at http://www.eeti.com.tw/pdf/Software%20Programming%20Guide_v2.0.pdfSigned-off-by:
Böszörményi Zoltán <zboszor@pr.hu> Signed-off-by:
Dmitry Torokhov <dmitry.torokhov@gmail.com>
-
- 01 Dec, 2015 1 commit
-
-
Arnd Bergmann authored
S3C_ADC is only available on machines that don't do ARCH_MULTIPLATFORM, so changing the 'select' into 'depends on' here helps us move to ARCH_MULTIPLATFORM without introducing regressions. Signed-off-by:
Arnd Bergmann <arnd@arndb.de> Acked-by:
Dmitry Torokhov <dmitry.torokhov@gmail.com> Reviewed-by:
Krzysztof Kozlowski <k.kozlowski@samsung.com>
-
- 03 Nov, 2015 2 commits
-
-
Michael Welling authored
This adds support for the i2c based tsc2004 touchscreen controller. Signed-off-by:
Michael Welling <mwelling@ieee.org> Acked-by:
Rob Herring <robh@kernel.org> Signed-off-by:
Dmitry Torokhov <dmitry.torokhov@gmail.com>
-
Michael Welling authored
This patch separates the SPI functionality from core functionality that overlaps with the tsc2004. Prepares kernel for new tsc2004 driver without much redundant code. Signed-off-by:
Michael Welling <mwelling@ieee.org> Signed-off-by:
Dmitry Torokhov <dmitry.torokhov@gmail.com>
-
- 18 Oct, 2015 1 commit
-
-
Randy Dunlap authored
Fix build errors due to missing Kconfig dependency. drivers/built-in.o: In function `sur40_disconnect': sur40.c:(.text+0x22be6e): undefined reference to `video_unregister_device' sur40.c:(.text+0x22be77): undefined reference to `v4l2_device_unregister' drivers/built-in.o: In function `sur40_process_video': sur40.c:(.text+0x22c1d4): undefined reference to `v4l2_get_timestamp' drivers/built-in.o: In function `sur40_probe': sur40.c:(.text+0x22ca82): undefined reference to `v4l2_device_register' sur40.c:(.text+0x22cb1a): undefined reference to `v4l2_device_unregister' sur40.c:(.text+0x22cbf7): undefined reference to `video_device_release_empty' sur40.c:(.text+0x22cc53): undefined reference to `__video_register_device' sur40.c:(.text+0x22cc90): undefined reference to `video_unregister_device' drivers/built-in.o: In function `sur40_vidioc_querycap': sur40.c:(.text+0x22ccb0): undefined reference to `video_devdata' Signed-off-by:
Randy Dunlap <rdunlap@infradead.org> Signed-off-by:
Dmitry Torokhov <dmitry.torokhov@gmail.com>
-
- 06 Oct, 2015 1 commit
-
-
Yoichi Yuasa authored
This adds support for ROHM BU21023/24 Dual touch resistive touchscreens. Signed-off-by:
Yoichi Yuasa <yuasa@linux-mips.org> Signed-off-by:
Dmitry Torokhov <dmitry.torokhov@gmail.com>
-
- 02 Oct, 2015 1 commit
-
-
Noralf Trønnes authored
This adds support for the FT6x06 and the FT6x36 family of capacitive touch panel controllers, in particular the FT6236. Signed-off-by:
Noralf Trønnes <noralf@tronnes.org> Signed-off-by:
Dmitry Torokhov <dmitry.torokhov@gmail.com>
-
- 05 Sep, 2015 2 commits
-
-
Haibo Chen authored
Freescale i.MX6UL contains a internal touchscreen controller, this patch add a driver to support this controller. Signed-off-by:
Haibo Chen <haibo.chen@freescale.com> Signed-off-by:
Dmitry Torokhov <dmitry.torokhov@gmail.com>
-
Sanchayan Maity authored
The Colibri Vybrid VF50 module supports 4-wire touchscreens using FETs and ADC inputs. This driver uses the IIO consumer interface and relies on the vf610_adc driver based on the IIO framework. Signed-off-by:
Sanchayan Maity <maitysanchayan@gmail.com> Signed-off-by:
Dmitry Torokhov <dmitry.torokhov@gmail.com>
-
- 04 Aug, 2015 1 commit
-
-
Geert Uytterhoeven authored
The GPIO subsystem provides dummy GPIO consumer functions if GPIOLIB is not enabled. Hence drivers that depend on GPIOLIB, but use GPIO consumer functionality only, can still be compiled if GPIOLIB is not enabled. Relax the dependency on GPIOLIB if COMPILE_TEST is enabled, where appropriate. Signed-off-by:
Geert Uytterhoeven <geert@linux-m68k.org> Acked-by:
Linus Walleij <linus.walleij@linaro.org> Signed-off-by:
Dmitry Torokhov <dmitry.torokhov@gmail.com>
-
- 28 Jul, 2015 2 commits
-
-
Sebastian Reichel authored
Convert driver so that it uses regmap instead of directly using spi_transfer for all register accesses. Signed-off-by:
Sebastian Reichel <sre@kernel.org> Signed-off-by:
Dmitry Torokhov <dmitry.torokhov@gmail.com>
-
Sebastian Reichel authored
Replace spaces with tab, so that the tsc2005 Kconfig entry matches the other entries in drivers/input/touchscreen/Kconfig. Signed-off-by:
Sebastian Reichel <sre@kernel.org> Signed-off-by:
Dmitry Torokhov <dmitry.torokhov@gmail.com>
-
- 12 Jul, 2015 1 commit
-
-
Dmitry Torokhov authored
Let's switch form OF to device properties so that common parsing code could work not only on device tree but also on ACPI-based platforms. Reviewed-by:
Roger Quadros <rogerq@ti.com> Signed-off-by:
Dmitry Torokhov <dmitry.torokhov@gmail.com>
-
- 24 Jun, 2015 1 commit
-
-
HungNien Chen authored
This is a driver for Weida HiTech WDT87xx series touchscreen controller. Signed-off-by:
HungNien Chen <hn.chen@weidahitech.com> Signed-off-by:
Dmitry Torokhov <dmitry.torokhov@gmail.com>
-
- 26 May, 2015 1 commit
-
-
Dmitry Torokhov authored
The STMPE MFD is only used with device tree configured systems (and STMPE MFD core depends on OF), so force the configuration to come from device tree only. Tested-by:
Heiner Kallweit <hkallweit1@gmail.com> Reviewed-by:
Marek Vasut <marex@denx.de> Acked-by:
Lee Jones <lee.jones@linaro.org> Signed-off-by:
Dmitry Torokhov <dmitry.torokhov@gmail.com>
-