From: GitHub pull_request - opened <github@alsa-project.org>
To: alsa-devel@alsa-project.org
Subject: USB-Audio: Add support for DualSense PS5 controller
Date: Mon, 3 Nov 2025 21:33:03 +0100 (CET) [thread overview]
Message-ID: <1874995909bf7a00-webhooks-bot@alsa-project.org> (raw)
In-Reply-To: <alsa-project/alsa-ucm-conf/pr/634@alsa-project.org>
alsa-project/alsa-ucm-conf pull request #634 was opened from cristicc:
The Sony DualSense wireless controller (PS5) has an internal mono speaker and a microphone, in addition to a 3.5mm jack socket for headphone output and headset microphone input.
Because this is a UAC1 device, it doesn't advertise any jack detection capability. However, since kernel v6.18-rc1 (see [1]), the controller is able to report HP & MIC insert events via HID, i.e. through a dedicated input device managed by the hid-playstation driver. This is further used by a quirk in the generic USB audio driver (added in v6.17, see [2]), which creates the Headphone Jack & Headset Mic Jack controls and receives hotplug events from the HID driver via input handlers.
Moreover, the device provides haptic feedback functionality, which is controlled by a pair of dedicated channels in a quadraphonic audio stream.
Ensure proper support for audio switching between headphones/headset and internal speaker/microphone by adding a UCM to split the 4.0 PCM stream into 4 mono channels or a pair of stereo (FL+FR) channels, depending on the active output device/profile.
[1] https://lore.kernel.org/all/20250625-dualsense-hid-jack-v2-0-596c0db14128@collabora.com/
[2] https://lore.kernel.org/all/20250526-dualsense-alsa-jack-v1-0-1a821463b632@collabora.com/
Request URL : https://github.com/alsa-project/alsa-ucm-conf/pull/634
Patch URL : https://github.com/alsa-project/alsa-ucm-conf/pull/634.patch
Repository URL: https://github.com/alsa-project/alsa-ucm-conf
parent reply other threads:[~2025-11-03 20:34 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <alsa-project/alsa-ucm-conf/pr/634@alsa-project.org>]
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=1874995909bf7a00-webhooks-bot@alsa-project.org \
--to=github@alsa-project.org \
--cc=alsa-devel@alsa-project.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.