-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
drivers: input: Clean up ft5x46 touchscreen test module and dead code
* Modify point 1 to format the ft5x46 driver Kconfig file Modify point 2 to clean up the focaltech_test_(ft5x46/ft8716) Modify point 3 to clean up focaltech_test_(ft5x46/ft8716) code Modify point 4 to delete the ft5x46_ts_spi touchscreen register (cherry picked from commit 8571d7a3ec9b684e4b3cce8455b86d38e8008dd5) Change-Id: Ib76ad3ef496c791b9890cf259554c193da61906a
- Loading branch information
1 parent
60e843e
commit 84588d6
Showing
10 changed files
with
35 additions
and
2,000 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,59 +1,46 @@ | ||
config TOUCHSCREEN_FT5X46 | ||
tristate "FocalTech touchscreens" | ||
depends on I2C | ||
help | ||
Say Y here if you have a FT5X46 touchscreen. | ||
Ft5x06 controllers are multi touch controllers which can | ||
report 5 touches at a time. | ||
tristate "FocalTech touchscreens" | ||
depends on I2C | ||
help | ||
Say Y here if you have a FT5X46 touchscreen. | ||
Ft5x06 controllers are multi touch controllers which can | ||
report 5 touches at a time. | ||
|
||
If unsure, say N. | ||
If unsure, say N. | ||
|
||
To compile this driver as a module, choose M here: the | ||
module will be called ft5x46_ts. | ||
To compile this driver as a module, choose M here: the | ||
module will be called ft5x46_ts. | ||
|
||
config TOUCHSCREEN_FT5X46_CALIBRATE | ||
bool "calibrate after flash firmware" | ||
depends on TOUCHSCREEN_FT5X46 | ||
default y | ||
help | ||
must turn off after all pre-production device get upgrade. | ||
bool "calibrate after flash firmware" | ||
depends on TOUCHSCREEN_FT5X46 | ||
default y | ||
help | ||
must turn off after all pre-production device get upgrade. | ||
|
||
config TOUCHSCREEN_FT5X46_TYPEB | ||
bool "use type B for touch report" | ||
depends on TOUCHSCREEN_FT5X46 | ||
default y | ||
help | ||
enable typeB for multi-touch report. | ||
bool "use type B for touch report" | ||
depends on TOUCHSCREEN_FT5X46 | ||
default y | ||
help | ||
enable typeB for multi-touch report. | ||
|
||
config TOUCHSCREEN_FT5X46_I2C | ||
tristate "Focaltech FT5X0X I2C touchscreens" | ||
depends on I2C | ||
select TOUCHSCREEN_FT5X46 | ||
help | ||
Say Y here if you have a Focaltech FT5X46 I2C touchscreen connected | ||
to your system. | ||
tristate "Focaltech FT5X0X I2C touchscreens" | ||
depends on I2C | ||
select TOUCHSCREEN_FT5X46 | ||
help | ||
Say Y here if you have a Focaltech FT5X46 I2C touchscreen connected | ||
to your system. | ||
|
||
If unsure, say N. | ||
If unsure, say N. | ||
|
||
To compile this driver as a set of modules, choose M here: the | ||
modules will be called ft5x46_ts_i2c. | ||
|
||
config TOUCHSCREEN_FT5X46_SPI | ||
tristate "Focaltech FT5X0X SPI touchscreens" | ||
depends on SPI | ||
select TOUCHSCREEN_FT5X46 | ||
help | ||
Say Y here if you have a Focaltech FT5X46 SPI touchscreen connected | ||
to your system. | ||
|
||
If unsure, say N. | ||
|
||
To compile this driver as a set of modules, choose M here: the | ||
modules will be called ft5x46_ts_spi. | ||
To compile this driver as a set of modules, choose M here: the | ||
modules will be called ft5x46_ts_i2c. | ||
|
||
config TOUCHSCREEN_FT5X46P_PROXIMITY | ||
bool "focaltech touch proximity enable" | ||
depends on TOUCHSCREEN_FT5X46 | ||
default n | ||
help | ||
focaltech touch proximity enable. | ||
bool "focaltech touch proximity enable" | ||
depends on TOUCHSCREEN_FT5X46 | ||
default n | ||
help | ||
focaltech touch proximity enable. |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.