All of lore.kernel.org
 help / color / mirror / Atom feed
From: GitHub pull_request - edited <github@alsa-project.org>
To: alsa-devel@alsa-project.org
Subject: sof-soundwire: cleanups for codecs with multiple functions
Date: Fri,  5 Jun 2026 11:49:02 +0200 (CEST)	[thread overview]
Message-ID: <18b6266a4950f000-webhooks-bot@alsa-project.org> (raw)
In-Reply-To: <alsa-project/alsa-ucm-conf/pr/775@alsa-project.org>

alsa-project/alsa-ucm-conf pull request #775 was edited from perexg:

The load mechanism assumed only one multi-codec in the system, but
    we saw in #774 multiple instances of those codecs (rt1320 and rt713).
    
    Make the load mechanism straight:
    
    - introduce file variables
    - remove shadow variables
    - probe multi-codecs separately and modify the file variables
    - test for duplicate file inclusion (in both sof-soundwire / HiFi configs)
    - merge dmic configs for rt712,rt713 to one file
    
    This change also removes filters for speaker/headset/mic init includes.
    The file variables + multi-codec probe replaces this functionality and
    if the driver reports an "unknown" codec, UCM config should be updated anyway.


Link: https://github.com/alsa-project/alsa-ucm-conf/issues/774

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

  parent reply	other threads:[~2026-06-05  9:49 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <alsa-project/alsa-ucm-conf/pr/775@alsa-project.org>
2026-06-04 13:54 ` sof-soundwire: cleanups for rt712, rt713 and rt722 multi codec GitHub pull_request - opened
2026-06-05  9:48 ` sof-soundwire: cleanups for codecs with multiple functions GitHub pull_request - edited
2026-06-05  9:49 ` GitHub pull_request - edited [this message]
2026-06-05  9:49 ` GitHub pull_request - edited

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=18b6266a4950f000-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.