Hello Jack,
have you tried out the config options already in the launcher/touchpad file?
On Tue, May 07, 2024 at 03:29:47 CEST, Jack Curran wrote:
Do you have any guidance on how I would find the necessary values? I am not sure how I would find the GPIO values for my touchpad.
I have some hints you may try to disover your Touchpad config attributes. As the following example config demonstrates the current drivers requires the I2C bus address and HID descriptor address/register, which are touchpad device specific and differ between ELAN and SYNAPTICS. Further, we have to identify the GPIO interrupt pin used by the device to gain the drivers attention on input events (as I2C alone is missing such a mechanism).
<config gpio_pin="3" bus_addr="44" hid_addr="32" info="Framework Gen12/Gen13"/>
Let's first hunt for the touchpad-device properties. Please start Linux on the ZBook and gain root privileges. Run "journalctl --dmesg" and search for a line like the following.
# journalctl --dmesg | grep -i touchpad input: PIXA3854:00 093A:0274 Touchpad as /devices/pci0000:00/0000:00:15.3/i2c_designware.2/i2c-3/i2c-PIXA3854:00/0018:093A:0274.0002/input/input7
The output is on Framework 13 and tells us its a PixArt 3854 device that uses the same bus_addr="44" and hid_addr="32" as SYNAPTICS. If your device seems not to match PIXA or SYNA in the output you may go for the ELAN attributes bus_addr="21" and hid_addr="1".
Now we have to look out for the GPIO pin with "grep intel-gpio /proc/interrupts" (or alternatively the device string, e.g., PIXA3854, as search term).
# grep PIXA3854 /proc/interrupts 164: ... intel-gpio 3 PIXA3854:00
The number between intel-gpio and the model identifier specifies gpio_pin="3". After these steps, you hopefully discovered the config attributes of your device.
As you may already anticipate the manual discovery of the touchpad configuration is just an intermediate annoyance with the experimental touchpad support. In the future, these information will be automatically read via ACPI functions.
Regards