All of
 help / color / mirror / Atom feed
From: Diederik de Haas <>
To: "Liam Girdwood" <>,
	"Mark Brown" <>,
	"Takashi Iwai" <>,
	"Kuninori Morimoto" <>,
	"Thierry Reding" <>,
	"Jon Hunter" <>,
	"Stephan Gerhold" <>,,,
	"Guido Günther" <>,
	"Jaroslav Kysela" <>
Subject: Re: [PATCH] ASoC: simple-card: Fill in driver name
Date: Sun, 10 Oct 2021 12:40:00 +0200	[thread overview]
Message-ID: <5069869.zQgEQKRxDW@bagend> (raw)
In-Reply-To: <>

[-- Attachment #1: Type: text/plain, Size: 1966 bytes --]

On Sunday, 10 October 2021 10:40:09 CEST Jaroslav Kysela wrote:
> > Unfortunately this change broke multichannel audio on my Rock64 device
> > running Debian. My Rock64 is connected to my AVR (Pioneer SC-1224) via a
> > HDMI cable.
> This looks like an user space configuration problem.

I have placed ALSA card definitions (I think) from LibreELEC on my system from

I have just prepended "LE-" and appended ".bak" to those files and rebooted and 
that resulted in only "output:stereo-fallback" profiles.
Just like in what I considered 'failures' that I tracked down to this commit.

So it appears that LE's card definitions *gave* me multichannel output, whereas 
I wouldn't have had it otherwise. 
It also explains why the sound issue occurs with LE too.

Note that I took/used LE's work as 'inspiration' to improve things on Debian.
Their work seems very good to me and one of their card definitions was also 
referenced from (kernel) commit 25572fb5aa986bdbb35d06c0fb52a9b9d9b3b2c9 
titled "arm64: dts: rockchip: enable HDMI sound nodes for rk3328-rock64"

> if a PA profile or an UCM configuration is used (in the PA debug log).

While I don't consider myself clueless wrt Linux (running Sid for 10+ years), 
I am clueless wrt how ALSA/PA/audio-in-general works (on Linux).
When I do 'journalctl -b -u pulseaudio --since="2021-10-10 12:00:00"' I get a 
lot of output and also several 'errors', but I have no clue how to interpret 
that. I also get that when AFAIC (from a user standpoint) everything 'works'.
So I'd need some help with that.

I could attach output of (several runs of) "journalctl" and f.e. the output of 
'alsa-info', but I haven't yet as it may not be appropriate and may also no 
longer be considered a kernel problem (and the 'To:' list is (far) larger then 
I'm used to). So I'd need some guidance with that too.


[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 228 bytes --]

  reply	other threads:[~2021-10-10 10:40 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-22  8:27 [PATCH] ASoC: simple-card: Fill in driver name Guido Günther
2021-06-22 15:14 ` Mark Brown
2021-10-10  7:47 ` Diederik de Haas
2021-10-10  8:40   ` Jaroslav Kysela
2021-10-10 10:40     ` Diederik de Haas [this message]
2021-10-10 11:25       ` Guido Günther
2021-10-10 11:25         ` Guido Günther
2021-10-11 17:16       ` Jaroslav Kysela
2021-10-11 21:48         ` didi.debian
2021-10-11 21:48           ` didi.debian
2021-10-12  7:09           ` Jaroslav Kysela
2021-10-12  7:09             ` Jaroslav Kysela

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=5069869.zQgEQKRxDW@bagend \ \ \ \ \ \ \ \ \ \ \ \ \

* 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.