Skip to content

topology2: uaol: Name the PCMs "USB Offload <n>" - #11406

Merged
kv2019i merged 1 commit into
thesofproject:mainfrom
ujfalusi:peter/topic/uaol-pcm-names
Nov 6, 2026
Merged

kv2019i merged 1 commit into
thesofproject:mainfrom
ujfalusi:peter/topic/uaol-pcm-names

Conversation

@ujfalusi

@ujfalusi ujfalusi commented Nov 5, 2026

Copy link
Copy Markdown
Contributor

The frontend PCMs of the UAOL topologies are named after the link they run on, "UAOL0" and "UAOL1". What the user sees in aplay -l should say what the PCM is for, not which link carries it: "UAOL" is the name of Intel's link in the specifications and in the DAI names, the function is USB audio offload.

Name the PCMs "USB Offload 0" and "USB Offload 1", with the deep buffers following as "Deepbuffer USB Offload " like "Deepbuffer HDA Analog" does. This also pairs them by name with the kernel's "USB Offload Playback Route" / "USB Offload Capture Route" controls and the "USB Offload Jack", so that PCM, route control and jack of a stream share one name and the number tells them apart. The mixer volume controls derive their names from the PCM and follow along.

The DAI copiers and the backend DAI links keep their UAOL names: those are the link and are matched by the machine driver.

The frontend PCMs of the UAOL topologies are named after the link they
run on, "UAOL0" and "UAOL1". What the user sees in aplay -l should say
what the PCM is for, not which link carries it: "UAOL" is the name of
Intel's link in the specifications and in the DAI names, the function is
USB audio offload.

Name the PCMs "USB Offload 0" and "USB Offload 1", with the deep buffers
following as "Deepbuffer USB Offload <n>" like "Deepbuffer HDA Analog"
does. This also pairs them by name with the kernel's "USB Offload <n>
Playback Route" / "USB Offload <n> Capture Route" controls and the "USB
Offload Jack", so that PCM, route control and jack of a stream share one
name and the number tells them apart. The mixer volume controls derive
their names from the PCM and follow along.

The DAI copiers and the backend DAI links keep their UAOL names: those
are the link and are matched by the machine driver.

Signed-off-by: Peter Ujfalusi <peter.ujfalusi@linux.intel.com>
Copilot AI balanced review requested due to automatic review settings November 5, 2026 12:30

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🟢 Approval recommended

No active review issues are recorded for the USB Offload PCM renaming change.

No open issues 🎉

What changed in this PR

Renames UAOL frontend PCMs to user-facing “USB Offload” names, aligning them with the kernel’s route controls and jack naming while preserving backend link identifiers.

Changes:

  • Renames normal playback and capture PCMs for streams 0 and 1.
  • Renames deep-buffer PCMs to “Deepbuffer USB Offload 0/1”; derived mixer volume names follow.
  • Leaves UAOL DAI names, PCM IDs, and pipeline IDs unchanged.
File Description
tools/​topology/​topology2/​development/​sof-hda-generic-uaol.conf Applies USB Offload naming to the HDA-generic UAOL topology.
tools/​topology/​topology2/​cavs-uaol.conf Applies the same naming to the cAVS UAOL topology.

Review effort: Balanced

@intel-sofci

intel-sofci commented Nov 5, 2026 •

Copy link
Copy Markdown

PR 11406: test results

Run date: 2026-11-06 08:31 UTC

Tested commit: 2967b3849eb4301fdf7b64947c32cfeb8a602982

mtl pass rate lnl pass rate ptl pass rate wcl pass rate nvl pass rate

@kv2019i
kv2019i merged commit 0ebaf49 into thesofproject:main Nov 6, 2026
44 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

6 participants