Alsa-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: GitHub issues - edited <github@alsa-project.org>
To: alsa-devel@alsa-project.org
Subject: ALC4082 - ASRock X870 Steel Legend
Date: Tue, 12 Nov 2024 19:50:41 +0100 (CET)	[thread overview]
Message-ID: <20241112185041.7A91CF8058C@alsa1.perex.cz> (raw)
In-Reply-To: <1731437439059799671-webhooks-bot@alsa-project.org>

alsa-project/alsa-ucm-conf issue #462 was edited from cybik:

| Following up | Relevant PR | Related issues |
| ------------------| ---------------- | ---------------- |
| https://github.com/alsa-project/alsa-ucm-conf/issues/334 | https://github.com/alsa-project/alsa-ucm-conf/pull/461 | #434 |



The card "works", but there is one feature missing - though I hesitate to call it "critical": S/PDIF / TOSLINK support is incomplete.

While sound works "fine" (ish), it's limited to 2 channels.
* Plugging in another USB device (CM106-type, for example) gives out a plethora of configuration options (per the screenshot), though this also comes with having to select the right output
* The "USB" audio outs are output-specific, which is VERY welcome, but the S/PDIF out does not allow for any advanced selection like "Supported Codecs", and the HiFi 5.1 and 7.1 do not appear to enable any IEC958/AC3 support in the background

Is there something missing in the config files to allow for such support?

![image](https://github.com/user-attachments/assets/906ea829-0210-49a8-ba16-ad1b5b1285ae)

Issue URL     : https://github.com/alsa-project/alsa-ucm-conf/issues/462
Repository URL: https://github.com/alsa-project/alsa-ucm-conf

       reply	other threads:[~2024-11-12 18:51 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1731437439059799671-webhooks-bot@alsa-project.org>
2024-11-12 18:50 ` GitHub issues - edited [this message]
     [not found] <1731439980438632250-webhooks-bot@alsa-project.org>
2024-11-12 19:33 ` ALC4082 - ASRock X870 Steel Legend GitHub issues - edited
     [not found] <1731439920448478699-webhooks-bot@alsa-project.org>
2024-11-12 19:32 ` GitHub issues - edited
     [not found] <1731438037685908556-webhooks-bot@alsa-project.org>
2024-11-12 19:00 ` GitHub issues - edited
     [not found] <1731428020820724726-webhooks-bot@alsa-project.org>
2024-11-12 16:13 ` GitHub issues - edited
     [not found] <1731369902446803570-webhooks-bot@alsa-project.org>
2024-11-12  0:05 ` GitHub issues - edited
     [not found] <1731369894869204521-webhooks-bot@alsa-project.org>
2024-11-12  0:04 ` GitHub issues - edited
     [not found] <1731369853246054411-webhooks-bot@alsa-project.org>
2024-11-12  0:04 ` GitHub issues - edited
     [not found] <1731369782468131065-webhooks-bot@alsa-project.org>
2024-11-12  0:03 ` GitHub issues - edited
     [not found] <1731369770321220875-webhooks-bot@alsa-project.org>
2024-11-12  0:02 ` GitHub issues - opened

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=20241112185041.7A91CF8058C@alsa1.perex.cz \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox