Fedora touchscreen not working

Ask Fedora
,
1

The following is a report compiled by chat gpt (I know I’m not happy about using it either but i’d rather it helps me use linux than i give money to windows & palantir)

Lenovo Yoga 7 (83JR): WACF2200 touchscreen not detected on Fedora 44

Hardware

  • Manufacturer: Lenovo

  • System product: 83JR

  • Baseboard: LNVNB161216

  • BIOS version: QXCN15WW

  • Fedora: Fedora Linux 44

  • Kernel: 7.2.13-200.fc44.x86_64

Problem

The touchscreen on my Lenovo Yoga 7 no longer works in Fedora. It previously worked in Fedora and Windows. I want to restore touchscreen functionality on the current kernel.

Diagnostics

  • ACPI exposes a touchscreen device with hardware ID WACF2200 and compatible ID PNP0C50.

  • Its ACPI resources specify I²C controller \_SB.I2CC, address 0x000A, and an active-low GPIO interrupt on pin 157.

  • The device exists at /sys/bus/i2c/devices/i2c-WACF2200:00, but has no driver bound.

  • waiting_for_supplier reports 0.

  • The i2c_hid_acpi driver is present, but only the touchpad device is bound to it.

  • GPIO 157 appears in the AMD GPIO debug output as an input with pull-up enabled, but no interrupt is shown as registered.

  • Kernel logs contain no relevant messages for WACF2200, AMDI0010:02, or i2c_designware.

  • The touchscreen did not start working after a power reset.

  • Testing older installed kernels did not resolve the issue.

Related upstream investigation

I found an upstream GPIO interrupt workaround for the Lenovo Yoga 7 14AGP11 (product 83TD) involving GPIO 157 and the WACF2200 touchscreen. My system reports product 83JR and the same baseboard identifier, LNVNB161216.

The workaround was reverted upstream, and a subsequent I²C probe-ordering approach was also reverted. I have not applied either patch to my running system.

Request

Could someone advise whether the GPIO interrupt initialization or I²C probe ordering could explain why the WACF2200 device is present in ACPI but never binds to i2c_hid_acpi on this 83JR system? Is there a current fix or a recommended diagnostic procedure?