Comment 37 for bug 1900254

(In reply to Jan-Marek Glogowski from comment #28)
> To all the Intel *IIL05 users: please open a new bug report and handle the
> problems with that touchpad / touchscreen in there. It's different HW and
> needs completely different fixes.
>
> Maybe the reporter can update the title of the bug report?
>
> ----
>
> The whole bug was originally about the *touchpad* on the AMD version of the
> Lenovo Ideapad 5 15 AKA *ARE05, where the *touchscreen* elants_i2c driver
> wrongly claims the *touchpad* device.
>
> For the AMD version AKA *ARE05 we have a working workaround in comment 17,
> that fixes:
> 1. the touchpad
> 2. suspend to RAM (comment 19)
>
> The device eventually uses a different touchscreen driver, which was never
> affected (see comment 19 again).
>
> The bug: the elants_i2c driver finds the device by the ACPI id ELAN0001. It
> then probes the device, to detect if it's actually working. It even fails in
> there, but instead of giving up on it, it offers a driver interface to flash
> the "broken" firmware to some working state, and keeps trying to decode
> messages. Flashing would obviously also fail in this case, as the device is
> no touchscreen, but a touchpad. So the driver still claims the device and
> get's really "confused" by all the unknown i2c HID touchpad messages.
>
> Maybe the elants_i2c can detect the HID state of the device and then give up?

New bug report opened: https://bugzilla.kernel.org/show_bug.cgi?id=209521