From: Daniel Ogorchock <djogorchock@gmail.com>
To: Jiri Kosina <jikos@kernel.org>
Cc: "open list:HID CORE LAYER" <linux-input@vger.kernel.org>,
Roderick Colenbrander <thunderbird2k@gmail.com>,
Billy Laws <blaws05@gmail.com>,
Benjamin Tissoires <benjamin.tissoires@redhat.com>,
"Colenbrander, Roelof" <Roderick.Colenbrander@sony.com>,
Siarhei Vishniakou <svv@google.com>,
s.jegen@gmail.com, Carl Mueller <carmueller@gmail.com>,
"Pierre-Loup A. Griffais" <pgriffais@valvesoftware.com>,
Bastien Nocera <hadess@hadess.net>
Subject: Re: [PATCH v12 00/14] HID: nintendo
Date: Thu, 27 Aug 2020 10:23:22 -0500 [thread overview]
Message-ID: <CAEVj2tmgHg1zL4yAJKhcSmZZDw=odyvrxKAwKYOCC4zg-JMZwQ@mail.gmail.com> (raw)
In-Reply-To: <nycvar.YFH.7.76.2008271121150.27422@cbobk.fhfr.pm>
>
> 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
prev parent reply other threads:[~2020-08-27 15:23 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-23 4:41 [PATCH v12 00/14] HID: nintendo Daniel J. Ogorchock
2020-08-23 4:41 ` [PATCH v12 01/14] HID: nintendo: add nintendo switch controller driver Daniel J. Ogorchock
2021-02-15 14:15 ` Silvan Jegen
2020-08-23 4:41 ` [PATCH v12 02/14] HID: nintendo: add player led support Daniel J. Ogorchock
2020-08-23 4:41 ` [PATCH v12 03/14] HID: nintendo: add power supply support Daniel J. Ogorchock
2021-02-15 14:25 ` Silvan Jegen
2020-08-23 4:41 ` [PATCH v12 04/14] HID: nintendo: add home led support Daniel J. Ogorchock
2021-02-15 14:29 ` Silvan Jegen
2020-08-23 4:41 ` [PATCH v12 05/14] HID: nintendo: add rumble support Daniel J. Ogorchock
2021-02-15 14:33 ` Silvan Jegen
2020-08-23 4:41 ` [PATCH v12 06/14] HID: nintendo: improve subcommand reliability Daniel J. Ogorchock
2020-08-23 4:41 ` [PATCH v12 07/14] HID: nintendo: send subcommands after receiving input report Daniel J. Ogorchock
2020-08-23 4:41 ` [PATCH v12 08/14] HID: nintendo: reduce device removal subcommand errors Daniel J. Ogorchock
2020-08-23 4:41 ` [PATCH v12 09/14] HID: nintendo: patch hw version for userspace HID mappings Daniel J. Ogorchock
2020-08-23 4:41 ` [PATCH v12 10/14] HID: nintendo: set controller uniq to MAC Daniel J. Ogorchock
2021-02-15 14:42 ` Silvan Jegen
2020-08-23 4:41 ` [PATCH v12 11/14] HID: nintendo: add support for charging grip Daniel J. Ogorchock
2020-08-23 4:41 ` [PATCH v12 12/14] HID: nintendo: add support for reading user calibration Daniel J. Ogorchock
2020-08-23 4:41 ` [PATCH v12 13/14] HID: nintendo: prevent needless queueing of the rumble worker Daniel J. Ogorchock
2020-08-23 4:41 ` [PATCH v12 14/14] HID: nintendo: add IMU support Daniel J. Ogorchock
2021-02-15 14:53 ` Silvan Jegen
2020-08-27 9:22 ` [PATCH v12 00/14] HID: nintendo Jiri Kosina
2020-08-27 15:23 ` Daniel Ogorchock [this message]
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='CAEVj2tmgHg1zL4yAJKhcSmZZDw=odyvrxKAwKYOCC4zg-JMZwQ@mail.gmail.com' \
--to=djogorchock@gmail.com \
--cc=Roderick.Colenbrander@sony.com \
--cc=benjamin.tissoires@redhat.com \
--cc=blaws05@gmail.com \
--cc=carmueller@gmail.com \
--cc=hadess@hadess.net \
--cc=jikos@kernel.org \
--cc=linux-input@vger.kernel.org \
--cc=pgriffais@valvesoftware.com \
--cc=s.jegen@gmail.com \
--cc=svv@google.com \
--cc=thunderbird2k@gmail.com \
/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;
as well as URLs for NNTP newsgroup(s).