I tried Lukas' patch on both the latest gen x360 15z and 13z (model is 13z-ag000), and while it sometimes work perfectly, on some boots I get a "irq 7: nobody cared (try booting with the "irqpoll" option)" line followed by a "Disabling IRQ #7" message in dmesg, and the touchscreen stops working.
Booting with "irqpoll" does ensure a working touchscreen, but it seems to have a negative impact on battery life due to there being 8-9k IRQs per second constantly. Also, some new warning messages appeared in dmesg once irqpoll is enabled: a "hpet1: lost 9601 rtc interrupts" message repeats every 1-2 seconds ("hpet=disable" removes this, but doesn't help with the high number of IRQs per second), and a "i2c_hid i2c-ELAN0732:00: i2c_hid_get_input: incomplete report (67/65535)" warning happens with every touchscreen event.
I have a dual-boot setup with Windows 10, and the issue seems to be somehow affected by the other OS - rebooting from Windows 10 seems to guarantee a non-working touchscreen; however, cold booting directly into Linux (I tried Fedora 28 & Fedora Rawhide) does not guarantee a working touchscreen.
Did anyone experience the same problem? Or have ideas what the root cause or any workarounds might be?
I tried Lukas' patch on both the latest gen x360 15z and 13z (model is 13z-ag000), and while it sometimes work perfectly, on some boots I get a "irq 7: nobody cared (try booting with the "irqpoll" option)" line followed by a "Disabling IRQ #7" message in dmesg, and the touchscreen stops working.
Booting with "irqpoll" does ensure a working touchscreen, but it seems to have a negative impact on battery life due to there being 8-9k IRQs per second constantly. Also, some new warning messages appeared in dmesg once irqpoll is enabled: a "hpet1: lost 9601 rtc interrupts" message repeats every 1-2 seconds ("hpet=disable" removes this, but doesn't help with the high number of IRQs per second), and a "i2c_hid i2c-ELAN0732:00: i2c_hid_get_input: incomplete report (67/65535)" warning happens with every touchscreen event.
I have a dual-boot setup with Windows 10, and the issue seems to be somehow affected by the other OS - rebooting from Windows 10 seems to guarantee a non-working touchscreen; however, cold booting directly into Linux (I tried Fedora 28 & Fedora Rawhide) does not guarantee a working touchscreen.
Did anyone experience the same problem? Or have ideas what the root cause or any workarounds might be?