fix(Hardware Support) Improve support for GPD Devices

[pastaq]

• All devices have a dedicated guide button. Remove the QAM mapping to
  allow full support of both paddles. (Win Mini, Win 4, Win 5)
• Remove unused GPD capability maps, rename gpd4 -> gpd2.
• Adds support for GPD Win Max.
• Adds support for GPD Win 4 2023 (7640u/7840u) versions.
• Adds support for GPD Win 4 2024 (8840u) version.
• Adds support for GPD Win 5 2025 (HX 370)version.
• Separated GPD Win Mini 2023, 2024.
• Adds support for GPD Win Mini 2025 version.
• Adds back paddle support. GPD Win 4 and Win 5 devices use the same back
  paddle device as the Win Wini line.

Closes #454
Closes #573
Closes #636
Closes #640
Closes #645
Closes #652

Awaiting testing:
Win 4 2024
Win 4 2025

Tested:
Win Max
Win 4 2023
Win 5 2025
Win Mini 2024
Win Mini 2025

[DrewRS]

GPD Win Mini 2025: I'm able to access OGUI in game mode now and inputplumber device 0 is showing as GPD WinMini. Trackpad no longer functions in both game mode and desktop mode. L4 and R4 buttons are still not mappable and are not displaying in inputplumber device test.
inputplumber-journal3.txt

GPD Win Max 2 2025: Buttons, back paddles, and trackpad are all working as expected. Able to access OGUI in game mode, but not able to map the back paddles, and inputplumber device 0 is showing as GPD WinMax2

[TigraTT-Driver]

Suggested change

	y: [0, -1, 0]
	z: [0, 0, 1]
	y: [0, 0, 1]
	z: [0, -1, 0]

should fix the gyro axes on the win 4 2022

[pastaq]

GPD Win Mini 2025: I'm able to access OGUI in game mode now and inputplumber device 0 is showing as GPD WinMini. Trackpad no longer functions in both game mode and desktop mode. L4 and R4 buttons are still not mappable and are not displaying in inputplumber device test. inputplumber-journal3.txt

Can you hold guide and use the track pad? The win mini has a track pad driver and for some reason Valve has the deck configured such that the mouse activity doesn't work in the steam UI, just in desktop or in game, unless you hold guide.

GPD Win Max 2 2025: Buttons, back paddles, and trackpad are all working as expected. Able to access OGUI in game mode, but not able to map the back paddles, and inputplumber device 0 is showing as GPD WinMax2

[DrewRS]

GPD Win Mini 2025: I'm able to access OGUI in game mode now and inputplumber device 0 is showing as GPD WinMini. Trackpad no longer functions in both game mode and desktop mode. L4 and R4 buttons are still not mappable and are not displaying in inputplumber device test. inputplumber-journal3.txt

Can you hold guide and use the track pad? The win mini has a track pad driver and for some reason Valve has the deck configured such that the mouse activity doesn't work in the steam UI, just in desktop or in game, unless you hold guide.

Holding the menu button and using the track pad isn't working both in game mode and desktop mode.

GPD Win Max 2 2025: Buttons, back paddles, and trackpad are all working as expected. Able to access OGUI in game mode, but not able to map the back paddles, and inputplumber device 0 is showing as GPD WinMax2

[YifePlayte]

To make paddles work, L4 and R4 should config to PrtSc/SysRq and Pause. If you used Handheld Daemon and used the F20/F21 configuration, you might need to restore that.

I'm using GPD Win Mini 2024 8840U, and track pad is also not working.

Input driver version is 1.0.1
Input device ID: bus 0x18 vendor 0x911 product 0x5288 version 0x100
Input device name: "HTIX5288:00 0911:5288 Touchpad"
Supported events:
  Event type 0 (EV_SYN)
  Event type 1 (EV_KEY)
    Event code 272 (BTN_LEFT)
    Event code 325 (BTN_TOOL_FINGER)
    Event code 330 (BTN_TOUCH)
    Event code 333 (BTN_TOOL_DOUBLETAP)
    Event code 334 (BTN_TOOL_TRIPLETAP)
    Event code 335 (BTN_TOOL_QUADTAP)
  Event type 3 (EV_ABS)
    Event code 0 (ABS_X)
      Value   2628
      Min        0
      Max     2628
      Resolution      39
    Event code 1 (ABS_Y)
      Value   1332
      Min        0
      Max     1332
      Resolution      28
    Event code 47 (ABS_MT_SLOT)
      Value      0
      Min        0
      Max        3
    Event code 53 (ABS_MT_POSITION_X)
      Value      0
      Min        0
      Max     2628
      Resolution      39
    Event code 54 (ABS_MT_POSITION_Y)
      Value      0
      Min        0
      Max     1332
      Resolution      28
    Event code 57 (ABS_MT_TRACKING_ID)
      Value      0
      Min        0
      Max    65535
  Event type 4 (EV_MSC)
    Event code 5 (MSC_TIMESTAMP)
Key repeat handling:
  Repeat type 20 (EV_REP)
    Repeat code 0 (REP_DELAY)
      Value    250
    Repeat code 1 (REP_PERIOD)
      Value     33
Properties:
  Property type 0 (INPUT_PROP_POINTER)
  Property type 2 (INPUT_PROP_BUTTONPAD)

[pastaq]

I'm using GPD Win Mini 2024 8840U, and track pad is also not working.

can you do inputplumber device 0 test and confirm it isn't working in the tester?

[YifePlayte]

can you do inputplumber device 0 test and confirm it isn't working in the tester?

it's not working

[plrusek]

I initially reported the 2023 version of Win 4. I can confirm it's working fine for my device for a while now.

[plrusek]

Win Max 2020 tested, InputPlumber recognizes it just fine.

[YifePlayte]

I found that the implemented touchpad driver is not suitable for GPD Win Mini 2024 (8840u), and I found that my touchpad shares the same VID and PID with Orange Pi Neo's touchpads.

I never code in rust before, so I tried to let AI to make it work. Here's the code for reference. Based on ea52cde9.

gpd-win-mini-2024-8840u.patch

It works for me on my device, but there may be AI slops.

And I can't help noticing that only single finger works, no multi-finger. But AI told me that the 2023 driver only implemented single-touch too, so I called it a success.

[pastaq]

I found that the implemented touchpad driver is not suitable for GPD Win Mini 2024 (8840u), and I found that my touchpad shares the same VID and PID with Orange Pi Neo's touchpads.

I never code in rust before, so I tried to let AI to make it work. Here's the code for reference. Based on ea52cde9.

gpd-win-mini-2024-8840u.patch

It works for me on my device, but there may be AI slops.

And I can't help noticing that only single finger works, no multi-finger. But AI told me that the 2023 driver only implemented single-touch too, so I called it a success.

Please submit as a separate PR. I see a few things I'd like to change, but it's difficult to review when the patch is posted like this.

Since the device matches the orange pi touchpad, I'm curious if you attempted to use that driver at all?

[YifePlayte]

Please submit as a separate PR. I see a few things I'd like to change, but it's difficult to review when the patch is posted like this.

So should I submit it based on the main branch?

Since the device matches the orange pi touchpad, I'm curious if you attempted to use that driver at all?

orange pi touchpad returns completely different data, since orange pi has dual-touchpad and they are single-touch 512x512 touchpads, while gpd win mini 2024 has a 4 finger multi-touch 2628x1332 touchpad. so it's better to use a separate driver.

[pastaq]

So should I submit it based on the main branch?

You can target this branch, I'll pull it in before I merge.

[sideeffectdk]

heya can finally test and report back.
gpd win4 2022 (6800U) does not currently work with inputplumber and OGUI.
i have tried on both on bazzite testing-44.20260902.3 and stable 44.20260902
guide + B does nothing, gyro does not show up when doing inputplumber device 0 test. It looks like a generic xbox controller.
Here are all my logs:
cpu_model.log
dmesg.txt
dmi.log
inputplumber_device_0_info.log
inputplumber_device_0_targets_list.log
inputplumber_devices.log
extra logs gpd win4 2022.txt
journalctl.log
proc_devs.log

[YifePlayte]

i have tried on both on bazzite testing-44.20260902.3 and stable 44.20260902 guide + B does nothing

Just a reminder: you should build the latest RPM yourself, including this PR and any other necessary PRs, and then install it over the existing version on Bazzite using whatever method works before testing.

Bazzite gets InputPlumber from the Terra repository. However, the spec file used by Terra to build the RPM has merged three PRs, but it does not get updated automatically as those PRs are updated. Therefore, the InputPlumber package currently installed on your system may very likely contain outdated fixes.

[saiyanpickle]

Here are the logs you asked for. There was no output for hidraw5-9 @pastaq

cat_proc_bus_input_devices.txt
libinput_debug_events.txt
lscpu_grep_model.txt
lsusb_testing.txt
udevadm_info_device0.txt
udevadm_info_hidraw0.txt
udevadm_info_hidraw1.txt
udevadm_info_hidraw2.txt
udevadm_info_hidraw3.txt
udevadm_info_hidraw4.txt

[plrusek]

I initially reported the 2023 version of Win 4. I can confirm it's working fine for my device for a while now.

Regression, no longer works. inputplumber-custom device 0 test returns Error: "Composite device does not exist with number: 0"

logs-this-boot.txt

Device is only recognized if I put back this old 50-gpd_win4.yaml profile I had for a while into /etc/inputplumber/devices.d

50-gpd_win4.yaml

[pastaq]

I initially reported the 2023 version of Win 4. I can confirm it's working fine for my device for a while now.

Regression, no longer works. inputplumber-custom device 0 test returns Error: "Composite device does not exist with number: 0"

logs-this-boot.txt

Device is only recognized if I put back this old 50-gpd_win4.yaml profile I had for a while into /etc/inputplumber/devices.d

50-gpd_win4.yaml

Each year had been broken up by cpu model. can you provide lscpu | grep Model and cat /proc/bus/input/devices so I can identify the difference? The file you linked is the old one where everything was combined.

[plrusek]

Win 2023 7640u back to working status.