From: Vicki Pfau <vi@endrift.com>
To: Dmitry Torokhov <dmitry.torokhov@gmail.com>,
Jiri Kosina <jikos@kernel.org>,
Benjamin Tissoires <bentiss@kernel.org>,
linux-input@vger.kernel.org
Cc: Vicki Pfau <vi@endrift.com>
Subject: [PATCH v2 0/3] Input: Add BTN_GRIP*
Date: Wed, 16 Jul 2025 17:01:37 -0700 [thread overview]
Message-ID: <20250717000143.1902875-1-vi@endrift.com> (raw)
Many controllers these days have started including grip buttons. As there has
been no particular assigned BTN_* constants for these, they've been
hapharzardly assigned to BTN_TRIGGER_HAPPY*. Unfortunately, the assignemnt of
these has varied significantly between drivers.
This series adds, documents, and uses those buttons in the xpad and hid-steam
drivers. The only other driver I was able to find that supports grip buttons
was the BPF patch for the Xbox Elite 2 controller. Unfortunately, I'm not sure
how to clean that up and add support in HID descriptor parsing, so I'll have
to leave that to Benjamin.
Version 2 changes the hid-steam patch to use BTN_GRIPL/BTN_GRIPR for the Steam
Controller, not just the Steam Deck. All other patches are unchanged.
Vicki Pfau (3):
Input: Add and document BTN_GRIP*
Input - xpad: Use new BTN_GRIP* buttons
HID: hid-steam: Use new BTN_GRIP* buttons
Documentation/input/gamepad.rst | 13 ++++++++++
drivers/hid/hid-debug.c | 2 ++
drivers/hid/hid-steam.c | 35 ++++++++++++-------------
drivers/input/joystick/xpad.c | 36 +++++++++++++-------------
include/uapi/linux/input-event-codes.h | 5 ++++
5 files changed, 54 insertions(+), 37 deletions(-)
--
2.49.0
next reply other threads:[~2025-07-17 0:02 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-17 0:01 Vicki Pfau [this message]
2025-07-17 0:01 ` [PATCH v2 1/3] Input: Add and document BTN_GRIP* Vicki Pfau
2025-07-17 0:01 ` [PATCH v2 2/3] Input - xpad: Use new BTN_GRIP* buttons Vicki Pfau
2025-07-27 8:23 ` Dmitry Torokhov
2025-07-17 0:01 ` [PATCH v2 3/3] HID: hid-steam: " Vicki Pfau
2025-08-04 13:40 ` Jiri Kosina
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=20250717000143.1902875-1-vi@endrift.com \
--to=vi@endrift.com \
--cc=bentiss@kernel.org \
--cc=dmitry.torokhov@gmail.com \
--cc=jikos@kernel.org \
--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