Could you please elaborate a little bit better about this conflict?
hid-steam and hid-nintendo seem to be supporting different VID/PID
combinations, so that's not the conflict I guess.

Is Steam implementing some (proprietary?) userspace driver for conflicting
VID/PID with hid-nintendo, using hidraw?

Thanks,

--
Jiri Kosina
SUSE Labs

Hi Jiri,

Yes, Steam implements its own userspace driver using hidraw for the
nintendo switch pro controller. As things stand now, this can lead to
issues when running Steam while the hid-nintendo driver is in use,
where userspace and the kernel can be both sending reports to the
controller. My understanding is that hid-steam uses a virtual hidraw
device to workaround a similar issue with the steam controller
(backing off and not sending reports when it sees hidraw in use).

hid-nintendo does set the most significant bit of the the hid device's
version to allow userspace to distinguish from the standard hid driver
(same thing hid-sony does for things like libSDL mappings). Maybe that
will be sufficient for applications to choose whether to use their own
userspace driver or not. I'm not sure if that's considered acceptable
in the spirit of trying not to break userspace functionality.

Thanks,
Daniel