linux-kernel - Re: [RFC/HELP] add support for POWER-A/THQ BDA NSW Nintendo Controller

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-Id: <35EDK8BDVWSCG.2CILU67NZJL48@homearch.localdomain>
Date: Tue, 28 Jan 2025 21:04:41 +0100
From: "Silvan Jegen" <s.jegen@...il.com>
To: Ethan Carter Edwards <ethan@...ancedwards.com>
Cc: djogorchock@...il.com, jikos@...nel.org, bentiss@...nel.org,
 linux-input@...r.kernel.org, linux-kernel@...r.kernel.org,
 kernelnewbies@...nelnewbies.org
Subject: Re: [RFC/HELP] add support for POWER-A/THQ BDA NSW Nintendo
 Controller

Hi Ethan

Ethan Carter Edwards <ethan@...ancedwards.com> wrote:
> Hello all,
> 
> I have an unofficial USB Nintendo Switch Pro controller that I have had
> for a few years and want to try to use on Linux. For reference, the
> vendor id and device ids are as follows:
> 
> Vendor: 20d6
> Device: 0002
> 
> I tried adding the device to the hid-nintendo module to add support but
> that did not work (see below for code). I recieved a few errors from dmesg
> 
> nintendo 0003:20D6:0002.0011: Failed to get joycon info; ret=-110
> nintendo 0003:20D6:0002.0011: Failed to retrieve controller info; ret=-110
> nintendo 0003:20D6:0002.0011: Failed to initialize controller; ret=-110
> nintendo 0003:20D6:0002.0011: probe - fail = -110
> nintendo 0003:20D6:0002.0011: probe with driver nintendo failed with error -110
> 
> I understand that -110 is a timeout. But I don't understand much else.

I have tried to write a test for the Nintendo HID driver for a while and
think I have encountered this error as well. If I remember correctly,
this timeout happens because the controller does not respond with the
reply that the driver is expecting (or at least not in time).

> And I am not sure where to go from here. Any suggestions?

I'm a newbie as well but my understanding is that you would have
to figure out what the controller is actually sending back and how it
differs from what the driver expects. Then you might be able to either
adapt the driver accordingly (if the behaviour of the device is similar
enough to the official pro controller) or write a separate driver that
can handle this controller ...

Cheers,
Silvan