Silead Touchscreen Driver Free
Silead Touchscreen Driver Reviews
Silead Touch Driver Windows 10

This page collects all the information about the various touch screen controllers in use on sunxi hardware.

Dec 20, 2018 This repository contains firmware images for the Silead touchscreen controllers in various tablet (and other) devices. There is also a number of conversion tools here that help with extraction and preparation of firmware images. The firmware files were extracted from Android and Windows device drivers, as published by device manufacturers.

1General information
- 1.5Hardware Configuration and Fex
2Manufacturers
- 2.2Elan
- 2.3Focaltech
  - 2.3.4FT5x06
- 2.4Goodix
- 2.5Ilitek
- 2.7Solomon Systech Limited
- 2.8TCM
- 2.9ZEITEC Semiconductor

General information. In general touchscreens are configured by the ctppara in the fex file. There's also support for resistive touch panels by setting rtppara in the fex.
Below is a list of our most popular Silead product support software drivers. To download, select the Model Name/Number of your device, then click the Download button. If you do not see the right driver, enter the model into the search box below and Search our Driver Support Database.
Below is a list of our most popular Silead product support software drivers. To download, select the Model Name/Number of your device, then click the Download button. If you do not see the right driver, enter the model into the search box below and Search our Driver Support Database.
Sileadts ships with the Linux kernel since version 4.8 and is the recommended driver. Gslx680tsacpi can still be useful for initial testing or if sileadts does not work for you. When Silead touchscreen support was added to ACPI (PC) platforms, the integrator did not anticipate any uses cases outside the device vendor's ecosystems.

In general touchscreens are configured by the ctp_para in the fex file. There's also support for resistive touch panels by setting rtp_para in the fex. An example for built in RTP (resistive touch panel) built in controller can be found in the Fex Guide.

An example (for ft5x) would be:

Example for built in RTP:

Hardware

In general a capacitive touchscreen hardware consists of 6 Pins:

RST - Reset Pin (Input), Used by the CPU to reset the touchscreen.
SDA - I2C SDA (IO)
SCL - I2C SDL (Input)
INT - Interrupt Pin (Output, can be input during startup), used by the Touchscreen to indicate to the CPU that there are new events
VCC - Power Supply
GND - GND

Some touchscreen have wakeup pins to allow the touchscreen to go to sleep mode to save battery.

Mainly the I2C pins are connected to any i2c port on the CPU and is used to communicate with the touchscreen.

In the other way a resistive touchscreen has 4 wires. Details can be found in the user manuals for Allwinner chips, in the section TP (touch panel). The interesting thing is that sun4i, sun6i and sun7i have essentially the same RTP controllers so the sun4i_ts driver can work for all of them. Testing was done on an A20 platform and gave exceptionally good results.

Startup Procedure

Usually any touchscreen has a startup procedure during which resets are sent to the touchscreen by the cpu to indicate this procedure. During the reset/startup procedure usually the touchscreen profile data is sent to the touchscreen. Also in some cases the I2C address is set by this rest procedure (for instance, GT911).

The interrupt Pin can be part of the startup procedure for handshakes or indications. In some cases the interrupt pin is also used as input to read additional data from the cpu during reset.

Touchscreen profiles

Some touchscreen (for instance, GT911) require a so call Touchscreen Profile/Configuration. This configuration is sent during or right after the reset procedure of the touchscreen and is usually written to the controller memory (in some cases selectable persistent in eeprom). The Profile/Config defines the parameters of the touchscreen (such as physical size, active area(s). also it can include touchscreen button areas, touchscreen mode and more.

THIS CONFIGURATION MUST BE PROVIDED BY THE TOUCHSCREEN PRODUCER!

Example:

Touchscreen modes

There is 2 modes a touchscreen can work in:

Polling Mode
Interrupt Mode

This mode is usually defined by the Touchscreen profile/config or the startup/reset procedure.

The preferred mode a capacitive touchscreen should work in is always interrupt mode. In Interrupt mode every time an event on the touchscreen occurs the INT pin triggers and notifies the CPU. the cpu then read the new event from the touchscreen.

In Polling mode the cpu periodically requests the touchscreen data from the touchscreen. This means that there will be a lot of communication on the i2c port since this has to happen once every few ms.

As stated above whenever possible use interrupt mode!

Hardware Configuration and Fex

It is very important to configure the FEX file correctly for your touchscreen.

Step 1

In your hardware schematics identify the I2C pins of your touchscreen and see which I2C it is connected to and set the ctp_twi_id to the id of i2c port.Now you need to find our your i2c address of your touchscreen. this is something you can get out of the chip datasheet or your touchscreen manufacture.

Remember that the address of the touchscreen might be changed when sending the profile/config or via the reset procedure.

Step 2

In your schematics find out which GPIO Pin the INT Pin is connected to.

Define:

please also note the <6> part in the line above. Verify that the Interrupt setting of your Int pin is Function number 6 of the mux setting or modify the <X> according.

Note that on some touchscreens (ft5x) it is required to define another port called the IO port on the same port as the interrupt port:

It's a highly affordable, portable PC, and when you think of it that way, why wouldn't you get one? The horrors of the super-budget netbooks are long behind us, and we find now a range of top quality products at super affordable prices.Not just a tablet, but an affordable, quality PC.That means for less than $200 now you can get a great looking display, plenty of internal storage and RAM, with support from an optional keyboard and digital pen if you want them.That's ultimately what the Hi10 Air is. Best 7 inch windows tablet. It's not just a great tablet with killer specs for its bargain-basement price.

This setting will define the same port with mux setting 0 as output to allow the driver to switch to IO mode.

Step 3

In your schematics find out which GPIO Pin the RST Pin is connected to.

Note that <1> sets the port as an output.

It might be required to define additional pins for your touchscreen

Software Calibration

Calibration of a touchscreen device can be done with the xinput_calibrator. The xinput_calibrator is very simple tool which enables you to go through standard calibration procedure (press a few points on the screen) and then produces a snippet for xorg.conf.

There can be problems with produced configuration so it's good to test and see what's actually happening. Try to move your finger over the screen and see if there's some sings of miscalibration. Produced config actually scales values from touchscreen controller to map to the screen so it may happen that one axis works ok and another doesn't. Anyways, xinput_calibrator can give you good hint for start and you can tweak it further manually. Detailed list of options can be found in the evdev manual page.

ChipOne

Mainline kernel driver: icn8138
WIP drivers:
- icn85xx - WIP branch (announcement)

Silead Touchscreen Driver