search

raspberrypi / linux

Kernel source tree for Raspberry Pi-provided kernel builds. Issues unrelated to the linux kernel should be posted on the community forum at https://forums.raspberrypi.com/
Other
11.09k stars 4.97k forks source link

Bullseye touchscrren issue #4881

Open borsegbr opened 2 years ago

borsegbr commented 2 years ago

Describe the bug

with burst version touchscreen works properly evtest show correctly /dev/input/event0: raspberrypi-ts but with bullseye version touchscreen flicker random touch arround the screen and evtest show /dev/input/event0: generic ft5x06 (80)

Steps to reproduce the behaviour

use bullseye version of raspian with BTT PITFT5.0 V1.0 (clone of official touchscreen)

Device (s)

Raspberry Pi 4 Mod. B

System

cat /etc/rpi-issue using pi-gen, https://github.com/RPi-Distro/pi-gen, fbe448ccdc995d295d24c7596e5f0ef62cc2488f, stage4

vcgencmd version Jan 20 2022 13:56:48 Copyright (c) 2012 Broadcom version bd88f66f8952d34e4e0613a85c7a6d3da49e13e2

uname -a Linux pi 5.10.92-v8+ #1514 SMP PREEMPT Mon Jan 17 17:39:38 GMT 2022 aarch64 GNU/Linux

Logs

evtest \dev\input\event0

Input driver version is 1.0.1 Input device ID: bus 0x18 vendor 0x0 product 0x0 version 0x0 Input device name: "generic ft5x06 (80)" Supported events: Event type 0 (EV_SYN) Event type 1 (EV_KEY) Event code 330 (BTN_TOUCH) Event type 3 (EV_ABS) Event code 0 (ABS_X) Value 684 Min 0 Max 799 Event code 1 (ABS_Y) Value -2849 Min 0 Max 479 Event code 47 (ABS_MT_SLOT) Value 3 Min 0 Max 9 Event code 53 (ABS_MT_POSITION_X) Value 0 Min 0 Max 799 Event code 54 (ABS_MT_POSITION_Y) Value 0 Min 0 Max 479 Event code 57 (ABS_MT_TRACKING_ID) Value 0 Min 0 Max 65535 Properties: Property type 1 (INPUT_PROP_DIRECT) Testing ... (interrupt to exit) Event: time 1644407529.409569, type 3 (EV_ABS), code 47 (ABS_MT_SLOT), value 5 Event: time 1644407529.409569, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value -1 Event: time 1644407529.409569, -------------- SYN_REPORT ------------ Event: time 1644407529.433630, type 3 (EV_ABS), code 47 (ABS_MT_SLOT), value 3 Event: time 1644407529.433630, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 3111 Event: time 1644407529.433630, -------------- SYN_REPORT ------------ Event: time 1644407529.457600, type 3 (EV_ABS), code 47 (ABS_MT_SLOT), value 5 Event: time 1644407529.457600, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 3112 Event: time 1644407529.457600, type 3 (EV_ABS), code 47 (ABS_MT_SLOT), value 3 Event: time 1644407529.457600, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value -1 Event: time 1644407529.457600, -------------- SYN_REPORT ------------ Event: time 1644407529.485502, type 3 (EV_ABS), code 47 (ABS_MT_SLOT), value 5 Event: time 1644407529.485502, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value -1 Event: time 1644407529.485502, -------------- SYN_REPORT ------------ Event: time 1644407529.509511, type 3 (EV_ABS), code 47 (ABS_MT_SLOT), value 3 Event: time 1644407529.509511, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 3113 Event: time 1644407529.509511, -------------- SYN_REPORT ------------ Event: time 1644407529.533535, type 3 (EV_ABS), code 47 (ABS_MT_SLOT), value 5 Event: time 1644407529.533535, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 3114 Event: time 1644407529.533535, type 3 (EV_ABS), code 47 (ABS_MT_SLOT), value 3 Event: time 1644407529.533535, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value -1 Event: time 1644407529.533535, -------------- SYN_REPORT ------------ Event: time 1644407529.557499, type 3 (EV_ABS), code 47 (ABS_MT_SLOT), value 5 Event: time 1644407529.557499, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value -1 Event: time 1644407529.557499, -------------- SYN_REPORT ------------ Event: time 1644407529.585520, type 3 (EV_ABS), code 47 (ABS_MT_SLOT), value 3 Event: time 1644407529.585520, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 3115 Event: time 1644407529.585520, -------------- SYN_REPORT ------------ Event: time 1644407529.609566, type 3 (EV_ABS), code 47 (ABS_MT_SLOT), value 5 Event: time 1644407529.609566, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 3116 Event: time 1644407529.609566, type 3 (EV_ABS), code 47 (ABS_MT_SLOT), value 3 Event: time 1644407529.609566, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value -1 Event: time 1644407529.609566, -------------- SYN_REPORT ------------ Event: time 1644407529.633521, type 3 (EV_ABS), code 47 (ABS_MT_SLOT), value 5 Event: time 1644407529.633521, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value -1 Event: time 1644407529.633521, -------------- SYN_REPORT ------------ Event: time 1644407529.657522, type 3 (EV_ABS), code 47 (ABS_MT_SLOT), value 3 Event: time 1644407529.657522, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 3117 Event: time 1644407529.657522, -------------- SYN_REPORT ------------ Event: time 1644407529.681556, type 3 (EV_ABS), code 47 (ABS_MT_SLOT), value 5 Event: time 1644407529.681556, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 3118 Event: time 1644407529.681556, type 3 (EV_ABS), code 47 (ABS_MT_SLOT), value 3 Event: time 1644407529.681556, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value -1 Event: time 1644407529.681556, -------------- SYN_REPORT ------------ Event: time 1644407529.705540, type 3 (EV_ABS), code 47 (ABS_MT_SLOT), value 5 Event: time 1644407529.705540, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value -1 Event: time 1644407529.705540, -------------- SYN_REPORT ------------ Event: time 1644407529.729522, type 3 (EV_ABS), code 47 (ABS_MT_SLOT), value 3 Event: time 1644407529.729522, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 3119 Event: time 1644407529.729522, -------------- SYN_REPORT ------------ Event: time 1644407529.753561, type 3 (EV_ABS), code 47 (ABS_MT_SLOT), value 5 Event: time 1644407529.753561, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 3120 Event: time 1644407529.753561, type 3 (EV_ABS), code 47 (ABS_MT_SLOT), value 3 Event: time 1644407529.753561, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value -1 and loooooop

Additional context

No response

6by9 commented 2 years ago

I don't even know where one would buy a BTT PITFT5.0 panel. The drivers are written to support the Raspberry Pi 7" DSI panel. 3rd party products should be supported by their manufacturer.

There was a discussion on the mainline Linux kernel lists about trying to get the DFRobot DSI panels working. That vendor emulated an FT5x06 in a microcontroller, but relied on the very specific command sequence the firmware sent. The same may be true on your panel. https://lore.kernel.org/linux-input/CAJ+vNU341Qg_YDWR=0O2Ne4VF=W5kh3+WHuy8OGT+CfrmKiBgw@mail.gmail.com/T/

hoegge commented 2 years ago

Did you ever solve this? Have same issue with 5" display, that just gives errors in dmesg:

[  +0,024018] edt_ft5x06 10-0038: Unable to fetch data, error: -121
[  +0,024082] edt_ft5x06 10-0038: Unable to fetch data, error: -121
[  +0,031953] edt_ft5x06 10-0038: Unable to fetch data, error: -121
[  +0,015953] edt_ft5x06 10-0038: Unable to fetch data, error: -121
[  +0,024060] edt_ft5x06 10-0038: Unable to fetch data, error: -121
[  +0,024013] edt_ft5x06 10-0038: Unable to fetch data, error: -121
[  +0,023979] edt_ft5x06 10-0038: Unable to fetch data, error: -121
[  +0,023968] edt_ft5x06 10-0038: Unable to fetch data, error: -121
[  +0,024124] edt_ft5x06 10-0038: Unable to fetch data, error: -121
[  +4,803762] edt_ft5x06_ts_isr: 198 callbacks suppressed
[  +0,000028] edt_ft5x06 10-0038: Unable to fetch data, error: -121
[  +0,023973] edt_ft5x06 10-0038: Unable to fetch data, error: -121
[  +0,024094] edt_ft5x06 10-0038: Unable to fetch data, error: -121
[  +0,024321] edt_ft5x06 10-0038: Unable to fetch data, error: -121
[  +0,023581] edt_ft5x06 10-0038: Unable to fetch data, error: -121
[  +0,024045] edt_ft5x06 10-0038: Unable to fetch data, error: -121
[  +0,024208] edt_ft5x06 10-0038: Unable to fetch data, error: -121
[  +0,023772] edt_ft5x06 10-0038: Unable to fetch data, error: -121
[  +0,023993] edt_ft5x06 10-0038: Unable to fetch data, error: -121
[  +0,024061] edt_ft5x06 10-0038: Unable to fetch data, error: -121

continuously and evtest gives and never ends:

root@rpiraylibtest:/home/morten# evtest
No device specified, trying to scan all of /dev/input/event*
Available devices:
/dev/input/event0:  Lite-On Technology Corp. Lenovo USB Keyboard
/dev/input/event1:  Lite-On Technology Corp. Lenovo USB Keyboard System Control
/dev/input/event2:  Lite-On Technology Corp. Lenovo USB Keyboard Consumer Control
/dev/input/event3:  3Dconnexion CadMouse
/dev/input/event4:  3Dconnexion CadMouse
/dev/input/event5:  vc4
/dev/input/event6:  generic ft5x06 (ff)
Select the device event number [0-6]: 6
Input driver version is 1.0.1
Input device ID: bus 0x18 vendor 0x0 product 0x0 version 0x0
Input device name: "generic ft5x06 (ff)"
Supported events:
  Event type 0 (EV_SYN)
  Event type 1 (EV_KEY)
    Event code 330 (BTN_TOUCH)
  Event type 3 (EV_ABS)
    Event code 0 (ABS_X)
      Value      0
      Min        0
      Max      799
    Event code 1 (ABS_Y)
      Value      0
      Min        0
      Max      479
    Event code 47 (ABS_MT_SLOT)
      Value      0
      Min        0
      Max        9
    Event code 53 (ABS_MT_POSITION_X)
      Value      0
      Min        0
      Max      799
    Event code 54 (ABS_MT_POSITION_Y)
      Value      0
      Min        0
      Max      479
    Event code 57 (ABS_MT_TRACKING_ID)
      Value      0
      Min        0
      Max    65535
Properties:
  Property type 1 (INPUT_PROP_DIRECT)
Testing ... (interrupt to exit)