Skip to contentSkip to conversation

OMAP tsc210x touchscreens?

DISCUSSION Dirk Behme 2 participants 4 messages Oct 29, 2007

lore
Share & tools
lore

Dirk Behme

author
#0 lore raw

Because of [1] I looked into drivers/input/touchscreen/omap/ts_hx.c what need to be done there. And, mmh, looks like

drivers/input/touchscreen/omap

can/should be completely removed? I couldn't find any Kconfig using TOUCHSCREEN_OMAP, so touchscreen/omap will never compile?

Instead, touchscreen/tsc210x_ts.c should be used? tsc2102_ts.c is outdated and replaced by tsc210x_ts.c now as well?

Regards

Dirk

[1] http://linux.omap.com/pipermail/linux-omap-open-source/2007-October/011767.html

#1 lore raw

Hi,

Quoted 11 lines · Dirk Behme

Because of [1] I looked into drivers/input/touchscreen/omap/ts_hx.c what need to be done there. And, mmh, looks like

drivers/input/touchscreen/omap

can/should be completely removed? I couldn't find any Kconfig using TOUCHSCREEN_OMAP, so touchscreen/omap will never compile?

Instead, touchscreen/tsc210x_ts.c should be used? tsc2102_ts.c is outdated and replaced by tsc210x_ts.c now as well?

Yes, kindof, the tsc210x* files were supposed to replace tsc2101* and tsc2102* but tsc210x completely doesn't support audio yet, and there's probably more work to be done on it (not meaning that the tsc2101 or tsc2102 drivers in drivers/spi/ are more complete, except audio).

Regards

author
#2 lore raw
Quoted 12 lines · andrzej zaborowski

Hi,

Quoted 8 lines · Dirk Behme

Because of [1] I looked into drivers/input/touchscreen/omap/ts_hx.c what need to be done there. And, mmh, looks like

drivers/input/touchscreen/omap

can/should be completely removed? I couldn't find any Kconfig using TOUCHSCREEN_OMAP, so touchscreen/omap will never compile?

Quoted 6 lines
Quoted 2 lines

Instead, touchscreen/tsc210x_ts.c should be used? tsc2102_ts.c is outdated and replaced by tsc210x_ts.c now as well?

Yes, kindof, the tsc210x* files were supposed to replace tsc2101* and tsc2102* but tsc210x completely doesn't support audio yet,

Anything in touchscreen/* should be completely independent from audio? In touchscreen/* tsc210x* should be sufficent then and tsc2102* & omap/* in *input/touchscreen* are redundant?

Dirk

#3 lore raw
Quoted 13 lines · Dirk Behme
Quoted 12 lines · andrzej zaborowski

Hi,

Quoted 8 lines · Dirk Behme

Because of [1] I looked into drivers/input/touchscreen/omap/ts_hx.c what need to be done there. And, mmh, looks like

drivers/input/touchscreen/omap

can/should be completely removed? I couldn't find any Kconfig using TOUCHSCREEN_OMAP, so touchscreen/omap will never compile?

Quoted 8 lines
Quoted 6 lines
Quoted 2 lines

Instead, touchscreen/tsc210x_ts.c should be used? tsc2102_ts.c is outdated and replaced by tsc210x_ts.c now as well?

Yes, kindof, the tsc210x* files were supposed to replace tsc2101* and tsc2102* but tsc210x completely doesn't support audio yet,

Anything in touchscreen/* should be completely independent from audio?

The thing is that drivers/input/touchscreen/tsc2102_ts.c is selectable only if driver/spi/tsc2102.c is enabled, likewise with tsc210x* and other multi-function chips drivers. So, if you need audio you will need to select a tsc2102_ts.c (or whatever H2 uses), but hopefully soon this will change and tsc2102* will be dropped.

Quoted 2 lines

In touchscreen/* tsc210x* should be sufficent then and tsc2102* & omap/* in *input/touchscreen* are redundant?

I think it was decided that drivers/input/touchscreen/omap/* was going to be slowly removed. The code there is very platform dependent, but it does have an advantage of being very simple and fast as is usual for platform specific code.

Regards