From: Vicki Pfau <vi@endrift.com>
To: Jiri Kosina <jikos@kernel.org>,
Benjamin Tissoires <bentiss@kernel.org>,
linux-input@vger.kernel.org
Cc: Vicki Pfau <vi@endrift.com>,
Yousef Alhouseen <alhouseenyousef@gmail.com>
Subject: [PATCH v3 00/10] HID: steam: General cleanup and improvements
Date: Thu, 9 Jul 2026 19:00:35 -0700 [thread overview]
Message-ID: <20260710020048.2337655-1-vi@endrift.com> (raw)
This is the first half of a patch series improving the hid-steam driver.
This series contains a few notable changes:
- As I've been maintaining it downstream in SteamOS as well as writing
general improvements, I'm marking myself as the maintainer of the driver.
- Renames some stuff, notably marking the original Steam Controller as
Steam Controller (2015) in preparation of adding support for the Steam
Controller (2026), which will be in the second half of this series once
it's ready for submission.
- Adds IMU support for the Steam Controller (2015).
- Some reliability improvements, especially surrounding edge cases
regarding scheduled work during teardown.
- Fixes a short read issue reported by syzkaller.
Hopefully the second half of the series will be ready soon, but I am
waiting on more testing by SteamOS users before I submit it.
This is a minor interation on v2 that fixes a few issues that came up
during review of v2.
Vicki Pfau (10):
HID: steam: Update documentation
HID: steam: Refactor and clean up report parsing
HID: steam: Rename some constants that got renamed upstream
HID: steam: Add support for sensor events on the Steam Controller
(2015)
HID: steam: Coalesce rumble packets
HID: steam: Fully unregister controller when hidraw is opened
HID: steam: Rearrange teardown sequences
HID: steam: Improve logging and other cleanup
HID: steam: Reject short reads
HID: steam: Retry send/recv reports if stale
MAINTAINERS | 6 +
drivers/hid/hid-steam.c | 720 +++++++++++++++++++++++++++-------------
2 files changed, 490 insertions(+), 236 deletions(-)
--
2.54.0
next reply other threads:[~2026-07-10 2:02 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-10 2:00 Vicki Pfau [this message]
2026-07-10 2:00 ` [PATCH v3 01/10] HID: steam: Update documentation Vicki Pfau
2026-07-10 2:00 ` [PATCH v3 02/10] HID: steam: Refactor and clean up report parsing Vicki Pfau
2026-07-10 2:14 ` sashiko-bot
2026-07-10 2:00 ` [PATCH v3 03/10] HID: steam: Rename some constants that got renamed upstream Vicki Pfau
2026-07-10 2:00 ` [PATCH v3 04/10] HID: steam: Add support for sensor events on the Steam Controller (2015) Vicki Pfau
2026-07-10 2:19 ` sashiko-bot
2026-07-10 2:00 ` [PATCH v3 05/10] HID: steam: Coalesce rumble packets Vicki Pfau
2026-07-10 2:19 ` sashiko-bot
2026-07-10 2:00 ` [PATCH v3 06/10] HID: steam: Fully unregister controller when hidraw is opened Vicki Pfau
2026-07-10 2:17 ` sashiko-bot
2026-07-10 2:00 ` [PATCH v3 07/10] HID: steam: Rearrange teardown sequences Vicki Pfau
2026-07-10 2:18 ` sashiko-bot
2026-07-10 2:00 ` [PATCH v3 08/10] HID: steam: Improve logging and other cleanup Vicki Pfau
2026-07-10 2:17 ` sashiko-bot
2026-07-10 2:00 ` [PATCH v3 09/10] HID: steam: Reject short reads Vicki Pfau
2026-07-10 2:27 ` sashiko-bot
2026-07-10 2:00 ` [PATCH v3 10/10] HID: steam: Retry send/recv reports if stale Vicki Pfau
2026-07-10 2:31 ` sashiko-bot
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=20260710020048.2337655-1-vi@endrift.com \
--to=vi@endrift.com \
--cc=alhouseenyousef@gmail.com \
--cc=bentiss@kernel.org \
--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