From: Jaroslav Kysela <perex@perex.cz>
To: Christian Hewitt <christianshewitt@gmail.com>,
alsa-devel@alsa-project.org
Cc: Matthias Reichl <hias@horus.com>,
linux-amlogic@lists.infradead.org,
Jerome Brunet <jbrunet@baylibre.com>
Subject: Re: [RESEND] Amlogic DPCM audio card(s) speaker placement issue
Date: Sun, 26 Dec 2021 18:30:14 +0100 [thread overview]
Message-ID: <3cd96113-3272-1efe-aa81-39de952d1e68@perex.cz> (raw)
In-Reply-To: <ECC56215-1E02-4735-82F3-B68E73F56CB4@gmail.com>
On 26. 12. 21 12:43, Christian Hewitt wrote:
> **** List of PLAYBACK Hardware Devices ****
> card 0: LIBRETECHCC [LIBRETECH-CC], device 0: fe.dai-link-0 (*) []
> Subdevices: 1/1
> Subdevice #0: subdevice #0
> numid=12,iface=PCM,name='ELD',device=2
> numid=11,iface=PCM,name='IEC958 Playback Default',device=2
> numid=10,iface=PCM,name='IEC958 Playback Mask',device=2
> numid=9,iface=PCM,name='Playback Channel Map',device=2
>
> https://github.com/torvalds/linux/blob/master/arch/arm64/boot/dts/amlogic/meson-gxl-s905x-libretech-cc.dts#L136-L188
Have you tried to reorder the dai-link-# sections in DT? It appears to me that sound/soc/codecs/hdmi-codec.c / hdmi_codec_pcm_new() gets the internal PCM
device rather than the exported PCM device for the user space.
If the DAI routing cannot be changed, then the hdmi-codec.c should be modified to export the correct device number for the user space:
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/sound/soc/codecs/hdmi-codec.c?h=v5.16-rc6#n805
Jaroslav
--
Jaroslav Kysela <perex@perex.cz>
Linux Sound Maintainer; ALSA Project; Red Hat, Inc.
_______________________________________________
linux-amlogic mailing list
linux-amlogic@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-amlogic
next prev parent reply other threads:[~2021-12-26 17:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-26 11:43 Christian Hewitt
2021-12-26 17:30 ` Jaroslav Kysela [this message]
2021-12-30 8:28 ` Christian Hewitt
2022-01-03 9:57 ` Jerome Brunet
2022-01-03 11:04 ` 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=3cd96113-3272-1efe-aa81-39de952d1e68@perex.cz \
--to=perex@perex.cz \
--cc=alsa-devel@alsa-project.org \
--cc=christianshewitt@gmail.com \
--cc=hias@horus.com \
--cc=jbrunet@baylibre.com \
--cc=linux-amlogic@lists.infradead.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
all inboxes | Powered by JetHome®