- #Goodix touch hid edge scrolling how to#
- #Goodix touch hid edge scrolling driver#
- #Goodix touch hid edge scrolling Patch#
- #Goodix touch hid edge scrolling verification#
- #Goodix touch hid edge scrolling code#
#Goodix touch hid edge scrolling driver#
intel_sst_acpi 808622A8:00: No matching machine driver found How can we create this firmware file (and for the Chuwi Hi10 as well)?
#Goodix touch hid edge scrolling code#
This is because I added the ID 9111 to the code which is specific to the Chuwi Hi12. Goodix-TS i2c-GDIX1001:00: Direct firmware load for goodix_9111_cfg.bin failed with error -2 One obvious thing I saw in the log is the line: Now every time it's registering touches in the wrong place. However the user reports the symptoms when it's "working" now is worse than before. The patches are rebased on top of your github code ( ), so they should apply with no conflicts.Ĭould you forward a driver with these changes to the user and check if this solves the problem? You should also enable debug for the driver so we can see all messages (0002-Input-goodix-enable-debug.patch).
#Goodix touch hid edge scrolling Patch#
Given the information you provided, I made a test patch that will enable reset for the device (0001-Input-goodix-enable-reset-sequence-for-Chuwi-Hi12-ta.patch). The problem might be caused by not having the proper power-on timings. Normally the device configuration and ACPI settings for the irq flags should match, but in this case they are opposite. Also, as Dmitry mentioned, according to the ACPI table, the driver should work with the default of trigger_type = 1. Seems to me there is more going on than just having the wrong interrupt type in this case, since it still does not work when setting trigger_type to 0. Also appended to the end of this log is output from > fluke as he has not been reporting this type of problem happening > registering touch events in the wrong place. > read_config was succeeding but the user reported the touchscreen was > Also: following is an older log prior to my code changes where > input: Goodix Capacitive TouchScreen as > Goodix-TS i2c-GDIX1001:00: Invalid config, using defaults > x_max: 0, y_max: 0, touch_num: 0, trigger_type: 0 > time* is curious because he said before it was working like 9 out of His statement that it's not working *every > that setting the default trigger_type=0 when read_config fails does "the TS is not working every time, here is Irina, here is the ACPI table data you requested for this device Could you share the ACPI table so I can see if the gpio pins are properly declared? You can find the binary acpi tables in /sys/firmware/acpi/tables/* and you can decompile them with iasl -G *. For backwards compatibility, the reset sequence is only available if the interrupt and reset gpio pins are connected and configured through _DSD properties in the ACPI table or DT properties. Resetting the device at boot fixed the problem for me.
#Goodix touch hid edge scrolling how to#
The datasheet recommends using the reset procedure at power on, so I could not find any information on how to make the device work reliably without it. Īlthough the touch screen was initialized and I could read/write to/from the device, I read only 0s from the configuration registers. I had similar problems with some Goodix devices until I enabled the reset sequence. So I changed the code to set the defaults (when read_config fails) to trigger_type=0 and put the touch_num=10 as it was originally.Īwaiting test results/logs from the user. Goodix-TS i2c-GDIX1001:00: Invalid config, using defaults
#Goodix touch hid edge scrolling verification#
goodix_backport: module verification failed: signature and/or required key missing - tainting kernel goodix_backport: loading out-of-tree module taints kernel.
0 kommentar(er)
