public inbox for linux-input@vger.kernel.org
 help / color / mirror / Atom feed
From: Saihaj Johal <personal@sjohal.net>
To: linux-input@vger.kernel.org
Subject: hid_nintendo Switch 2 Pro Controller support - where to start?
Date: Sat, 05 Jul 2025 19:48:12 +0100	[thread overview]
Message-ID: <3642543.dWV9SEqChM@saihaj-mainpc> (raw)

Hello,
I recently got a Nintendo Switch 2 Pro Controller that is not currently 
directly supported by the kernel like how the Switch 1 controllers are. 
Looking in "hid-ids.h", there is no product ID for the new controller (got 
0x2069 from "lsusb -v"). The device class shows as miscellaneous device, and 
the controller does not show the player LEDs to show it is active (it only 
charges over USB, alongside showing in "lsusb" as well as showing as a USB 
audio device for the headphone jack on the bottom). However, I have managed to 
get it to work as a HID device using this website (https://
handheldlegend.github.io/procon2tool/) which uses WebUSB to send the right 
commands to make the controller turn on fully. After enabling, this setup 
seemingly works with the existing evdev system, although with some bizarre 
changes like the left stick's up and down being reversed (at least in KDE's 
game controller settings). The first step would likely be to add the device ID 
to "hid-ids.h", but from there where should I go in order to perhaps work on 
full support? I assume anything would work on the things discovered already by 
the WebUSB enabler tool, however I am very new to C and kernel development in 
general. 

Thanks,
Saihaj



             reply	other threads:[~2025-07-05 18:48 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-07-05 18:48 Saihaj Johal [this message]
2025-07-06  6:27 ` hid_nintendo Switch 2 Pro Controller support - where to start? Aditya Garg
2025-07-06 21:48   ` linux
2025-07-07 15:22     ` Saihaj Johal
2025-07-16 23:54       ` Vicki Pfau

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=3642543.dWV9SEqChM@saihaj-mainpc \
    --to=personal@sjohal.net \
    --cc=linux-input@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox