1# 2# Mouse driver configuration 3# 4menuconfig INPUT_TOUCHSCREEN 5 bool "Touchscreens" 6 help 7 Say Y here, and a list of supported touchscreens will be displayed. 8 This option doesn't affect the kernel. 9 10 If unsure, say Y. 11 12if INPUT_TOUCHSCREEN 13 14config TOUCHSCREEN_ADS7846 15 tristate "ADS 7846 based touchscreens" 16 depends on SPI_MASTER 17 help 18 Say Y here if you have a touchscreen interface using the 19 ADS7846 controller, and your board-specific initialization 20 code includes that in its table of SPI devices. 21 22 If unsure, say N (but it's safe to say "Y"). 23 24 To compile this driver as a module, choose M here: the 25 module will be called ads7846. 26 27config TOUCHSCREEN_BITSY 28 tristate "Compaq iPAQ H3600 (Bitsy) touchscreen" 29 depends on SA1100_BITSY 30 select SERIO 31 help 32 Say Y here if you have the h3600 (Bitsy) touchscreen. 33 34 If unsure, say N. 35 36 To compile this driver as a module, choose M here: the 37 module will be called h3600_ts_input. 38 39config TOUCHSCREEN_CORGI 40 tristate "SharpSL (Corgi and Spitz series) touchscreen driver" 41 depends on PXA_SHARPSL 42 default y 43 help 44 Say Y here to enable the driver for the touchscreen on the 45 Sharp SL-C7xx and SL-Cxx00 series of PDAs. 46 47 If unsure, say N. 48 49 To compile this driver as a module, choose M here: the 50 module will be called corgi_ts. 51 52config TOUCHSCREEN_GUNZE 53 tristate "Gunze AHL-51S touchscreen" 54 select SERIO 55 help 56 Say Y here if you have the Gunze AHL-51 touchscreen connected to 57 your system. 58 59 If unsure, say N. 60 61 To compile this driver as a module, choose M here: the 62 module will be called gunze. 63 64config TOUCHSCREEN_ELO 65 tristate "Elo serial touchscreens" 66 select SERIO 67 help 68 Say Y here if you have an Elo serial touchscreen connected to 69 your system. 70 71 If unsure, say N. 72 73 To compile this driver as a module, choose M here: the 74 module will be called elo. 75 76config TOUCHSCREEN_MTOUCH 77 tristate "MicroTouch serial touchscreens" 78 select SERIO 79 help 80 Say Y here if you have a MicroTouch (3M) serial touchscreen connected to 81 your system. 82 83 If unsure, say N. 84 85 To compile this driver as a module, choose M here: the 86 module will be called mtouch. 87 88config TOUCHSCREEN_MK712 89 tristate "ICS MicroClock MK712 touchscreen" 90 help 91 Say Y here if you have the ICS MicroClock MK712 touchscreen 92 controller chip in your system. 93 94 If unsure, say N. 95 96 To compile this driver as a module, choose M here: the 97 module will be called mk712. 98 99config TOUCHSCREEN_HP600 100 tristate "HP Jornada 680/690 touchscreen" 101 depends on SH_HP6XX && SH_ADC 102 help 103 Say Y here if you have a HP Jornada 680 or 690 and want to 104 support the built-in touchscreen. 105 106 If unsure, say N. 107 108 To compile this driver as a module, choose M here: the 109 module will be called hp680_ts_input. 110 111config TOUCHSCREEN_PENMOUNT 112 tristate "Penmount serial touchscreen" 113 select SERIO 114 help 115 Say Y here if you have a Penmount serial touchscreen connected to 116 your system. 117 118 If unsure, say N. 119 120 To compile this driver as a module, choose M here: the 121 module will be called penmount. 122 123config TOUCHSCREEN_TOUCHRIGHT 124 tristate "Touchright serial touchscreen" 125 select SERIO 126 help 127 Say Y here if you have a Touchright serial touchscreen connected to 128 your system. 129 130 If unsure, say N. 131 132 To compile this driver as a module, choose M here: the 133 module will be called touchright. 134 135config TOUCHSCREEN_TOUCHWIN 136 tristate "Touchwin serial touchscreen" 137 select SERIO 138 help 139 Say Y here if you have a Touchwin serial touchscreen connected to 140 your system. 141 142 If unsure, say N. 143 144 To compile this driver as a module, choose M here: the 145 module will be called touchwin. 146 147config TOUCHSCREEN_UCB1400 148 tristate "Philips UCB1400 touchscreen" 149 select AC97_BUS 150 help 151 This enables support for the Philips UCB1400 touchscreen interface. 152 The UCB1400 is an AC97 audio codec. The touchscreen interface 153 will be initialized only after the ALSA subsystem has been 154 brought up and the UCB1400 detected. You therefore have to 155 configure ALSA support as well (either built-in or modular, 156 independently of whether this driver is itself built-in or 157 modular) for this driver to work. 158 159 To compile this driver as a module, choose M here: the 160 module will be called ucb1400_ts. 161 162endif 163