All of lore.kernel.org
 help / color / mirror / Atom feed
From: GitHub pull_request - opened <github@alsa-project.org>
To: alsa-devel@alsa-project.org
Subject: ucm2: Qualcomm: Radxa Dragon Q6A: keep the headphone route when using HDMI
Date: Wed, 11 Nov 2026 12:05:19 +0100 (CET)	[thread overview]
Message-ID: <18e6f8da2606f100-webhooks-bot@alsa-project.org> (raw)
In-Reply-To: <alsa-project/alsa-ucm-conf/pr/906@alsa-project.org>

alsa-project/alsa-ucm-conf pull request #906 was opened from MarcHT91:

MultiMedia1 (hw:0) feeds the headphones and MultiMedia2 (hw:1) feeds
DisplayPort/HDMI. Each AudioReach back end accepts a single front end, so
connecting MultiMedia2 to RX_CODEC_DMA_RX_0 disconnects MultiMedia1.

The HiFi verb did exactly that ('RX_CODEC_DMA_RX_0 Audio Mixer
MultiMedia2' = 1), and the HDMI device then wrote 0 to the same control,
which on current kernels also clears the back end's link. After

  alsaucm -c hw:0 set _verb HiFi set _enadev HDMI

the headphones are disconnected, and a stream started on hw:0 never
advances (hw_ptr stays at 0):

  before: RX<-MM1=on   RX<-MM2=off  DP<-MM2=on
  after:  RX<-MM1=off  RX<-MM2=off  DP<-MM2=on

Keep each front end on its own back end: the verb clears the unused
routes and connects MultiMedia1 to the headphones, and the HDMI device
only switches 'DISPLAY_PORT_RX_0 Audio Mixer MultiMedia2'. The zero
writes come before the connections, so the order is also safe on kernels
where writing 0 to a route control drops whatever link the back end has
(fix sent to ASoC: "ASoC: qcom: audioreach: only disconnect the route a
mixer control owns").

Tested on a Radxa Dragon Q6A: verb only, verb + HDMI, verb + Headphones
+ HDMI, HDMI enable/disable: the headphone route stays connected in all
cases.

Fixes: 67628fb4871e ("ucm2: Qualcomm: add Radxa Dragon Q6A")

Request URL   : https://github.com/alsa-project/alsa-ucm-conf/pull/906
Patch URL     : https://github.com/alsa-project/alsa-ucm-conf/pull/906.patch
Repository URL: https://github.com/alsa-project/alsa-ucm-conf

           reply	other threads:[~2026-11-11 11:06 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <alsa-project/alsa-ucm-conf/pr/906@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=18e6f8da2606f100-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.