All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jaroslav Kysela <perex@perex.cz>
To: "Diederik de Haas" <didi.debian@cknow.org>,
	"Liam Girdwood" <lgirdwood@gmail.com>,
	"Mark Brown" <broonie@kernel.org>,
	"Takashi Iwai" <tiwai@suse.com>,
	"Kuninori Morimoto" <kuninori.morimoto.gx@renesas.com>,
	"Thierry Reding" <treding@nvidia.com>,
	"Jon Hunter" <jonathanh@nvidia.com>,
	"Stephan Gerhold" <stephan@gerhold.net>,
	alsa-devel@alsa-project.org, linux-kernel@vger.kernel.org,
	"Guido Günther" <agx@sigxcpu.org>
Subject: Re: [PATCH] ASoC: simple-card: Fill in driver name
Date: Mon, 11 Oct 2021 19:16:37 +0200	[thread overview]
Message-ID: <f7efde11-067d-8822-45fa-7cdbe2d17d93@perex.cz> (raw)
In-Reply-To: <5069869.zQgEQKRxDW@bagend>

On 10. 10. 21 12:40, Diederik de Haas wrote:
> 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
> https://github.com/LibreELEC/LibreELEC.tv/tree/master/projects/Rockchip/
> filesystem/usr/share/alsa/cards

Apparently, the alsa-lib configuration is used in this case.

It seems that there are four sound cards (Analog/HDMI/I2S/SPDIF) created for 
your hardware. The alsa-lib configuration is a bit weird - an obfuscation for 
the simple-card driver use. The simple way to resolve this is to create a 
proper UCM configuration.

If you need further assistance, create an issue for alsa-lib or alsa-ucm-conf 
on github and with an output from the 'alsa-info.sh' script.

						Jaroslav

-- 
Jaroslav Kysela <perex@perex.cz>
Linux Sound Maintainer; ALSA Project; Red Hat, Inc.

  parent reply	other threads:[~2021-10-11 17:16 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
2021-10-10 11:25       ` Guido Günther
2021-10-10 11:25         ` Guido Günther
2021-10-11 17:16       ` Jaroslav Kysela [this message]
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:
  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=f7efde11-067d-8822-45fa-7cdbe2d17d93@perex.cz \
    --to=perex@perex.cz \
    --cc=agx@sigxcpu.org \
    --cc=alsa-devel@alsa-project.org \
    --cc=broonie@kernel.org \
    --cc=didi.debian@cknow.org \
    --cc=jonathanh@nvidia.com \
    --cc=kuninori.morimoto.gx@renesas.com \
    --cc=lgirdwood@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=stephan@gerhold.net \
    --cc=tiwai@suse.com \
    --cc=treding@nvidia.com \
    /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.