Seiko LCD: touch move but no touch press/release

[mkl]

Hi,

I have two i.MX53 Quick Start Boards, both with a Seiko WVGA-REV B LCD touch
screen. One of the boards has an odd issue with the touch screen, the other
works fine.

On one of the boards, the touch screen only reports touch move events, no touch
press or touch release events. Here is the output of evtest:

    $ ./evtest /dev/input/event1
    Input driver version is 1.0.0
    Input device ID: bus 0x13 vendor 0x15b6 product 0x9052 version 0x101
    Input device name: "da9052-tsi"
    Supported events:
      Event type 0 (Sync)
      Event type 1 (Key)
        Event code 330 (Touch)
      Event type 3 (Absolute)
        Event code 0 (X)
          Value    985
          Min        0
          Max     1023
        Event code 1 (Y)
          Value    954
          Min        0
          Max     1023
        Event code 24 (Pressure)
          Value      0
          Min        0
          Max     1023
    Testing ... (interrupt to exit)
    Event: time 401.560045, type 3 (Absolute), code 0 (X), value 59
    Event: time 401.560054, type 3 (Absolute), code 1 (Y), value 108
    Event: time 401.560056, -------------- Report Sync ------------
    Event: time 401.570080, type 3 (Absolute), code 0 (X), value 58
    Event: time 401.570089, type 3 (Absolute), code 1 (Y), value 104
    Event: time 401.570091, -------------- Report Sync ------------
    Event: time 402.180045, type 3 (Absolute), code 1 (Y), value 115
    Event: time 402.180053, -------------- Report Sync ------------
    Event: time 402.190063, type 3 (Absolute), code 0 (X), value 59
    Event: time 402.190071, type 3 (Absolute), code 1 (Y), value 111
    Event: time 402.190073, -------------- Report Sync ------------
    Event: time 402.200066, type 3 (Absolute), code 0 (X), value 60
    Event: time 402.200073, type 3 (Absolute), code 1 (Y), value 114
    Event: time 402.200075, -------------- Report Sync ------------
    Event: time 402.220035, type 3 (Absolute), code 0 (X), value 57
    Event: time 402.220041, type 3 (Absolute), code 1 (Y), value 110

As you can see, there are only "type 3" events. The output from the other board
looks like this:

    $ ./evtest /dev/input/event1
    Input driver version is 1.0.0
    Input device ID: bus 0x13 vendor 0x15b6 product 0x9052 version 0x101
    Input device name: "da9052-tsi"
    Supported events:
      Event type 0 (Sync)
      Event type 1 (Key)
        Event code 330 (Touch)
      Event type 3 (Absolute)
        Event code 0 (X)
          Value      0
          Min        0
          Max     1023
        Event code 1 (Y)
          Value      0
          Min        0
          Max     1023
        Event code 24 (Pressure)
          Value      0
          Min        0
          Max     1023
    Testing ... (interrupt to exit)
    Event: time 2769.011087, type 1 (Key), code 330 (Touch), value 1
    Event: time 2769.050033, type 3 (Absolute), code 0 (X), value 94
    Event: time 2769.050037, type 3 (Absolute), code 1 (Y), value 235
    Event: time 2769.050039, -------------- Report Sync ------------
    Event: time 2769.060030, type 3 (Absolute), code 0 (X), value 93
    Event: time 2769.060034, type 3 (Absolute), code 1 (Y), value 233
    Event: time 2769.060036, -------------- Report Sync ------------
    Event: time 2769.070029, type 3 (Absolute), code 0 (X), value 99
    Event: time 2769.070033, type 3 (Absolute), code 1 (Y), value 230
    Event: time 2769.070035, -------------- Report Sync ------------
    Event: time 2769.080030, type 3 (Absolute), code 0 (X), value 97
    Event: time 2769.080034, type 3 (Absolute), code 1 (Y), value 234
    Event: time 2769.080035, -------------- Report Sync ------------
    Event: time 2769.141843, type 1 (Key), code 330 (Touch), value 0
    Event: time 2769.141846, -------------- Report Sync ------------
    Event: time 2772.257008, type 1 (Key), code 330 (Touch), value 1
    Event: time 2772.290020, type 3 (Absolute), code 0 (X), value 121
    Event: time 2772.290024, type 3 (Absolute), code 1 (Y), value 286
    Event: time 2772.290025, -------------- Report Sync ------------
    Event: time 2772.371841, type 1 (Key), code 330 (Touch), value 0

On this board, there are type 1 and type 3 messages, and everything works just
fine.  Does anybody have any idea what the problem could be?

Thanks,
Markus

[mkl]

Ok, here is the solution. It is a known issue that touch is not working correctly. One of my images has a patched version of the input driver, the other hasn't. http://forums.freescale.com/t5/i-MX-Microprocessors/imx53-Quick-Start-Board-LCD-touch-screen-problem...