From: Jaroslav Kysela <perex@perex.cz>
To: Hui Wang <hui.wang@canonical.com>, alsa-devel@alsa-project.org
Subject: Re: [alsa-devel] [alsa-lib][PATCH] conf: SOF-Intel: map pcm device for sof driver
Date: Mon, 16 Dec 2019 22:00:57 +0100 [thread overview]
Message-ID: <084ab279-3eef-e1bb-070b-1e4f1c8f26c7@perex.cz> (raw)
In-Reply-To: <20191216125136.6709-1-hui.wang@canonical.com>
Dne 16. 12. 19 v 13:51 Hui Wang napsal(a):
> On the machines with HDA codec, the sof driver will use the legacy hda
> codec driver, as a result, most mixer controls are same as before.
>
> There are only 2 difference:
> - HDMI pcm index is 3, 4 and 5 instead of 3, 7, 8...
> - dmic is on device 6, 7 instead of 0
>
> After applying this patch, we will get (aplay -L):
> hdmi:CARD=sofsklhdacard,DEV=0
> sof-skl_hda_card,
> HDMI Audio Output
> hdmi:CARD=sofsklhdacard,DEV=1
> sof-skl_hda_card,
> HDMI Audio Output
> hdmi:CARD=sofsklhdacard,DEV=2
> sof-skl_hda_card,
> HDMI Audio Output
>
> and (arecord -L):
> dmic:CARD=sofsklhdacard,DEV=0
> sof-skl_hda_card,
> Digital Mic connected to the PCH directly
> dmic:CARD=sofsklhdacard,DEV=1
> sof-skl_hda_card,
> Digital Mic connected to the PCH directly
>
> Then we could add minor changes in the pulseaudio configuration, after
> that, all output and input devices will work under pulseaudio.
>
> This is a supplement for ucm, the ucm for sof driver has higher
> priority than this conf, if there is no ucm for sof driver, this conf
> will take effect.
Exactly. The dmic definitions should not be a standard in my eyes. I would not
like to accept this. I can accept the standard definitions for the playback
devices for this driver, but UCM will replace everything. It's better to
define the special PA config for now until we resolve all the UCM issues like:
http://people.redhat.com/~jkysela/sof/carbon-x1-pulse.tar.gz2
The 2nd PA UCM patchset which is working with the current UCM in ALSA's repos
for this hardware:
https://gitlab.freedesktop.org/pulseaudio/pulseaudio/merge_requests/217
But it is just a start. There are plenty unresolved abstraction issues with this.
Jaroslav
--
Jaroslav Kysela <perex@perex.cz>
Linux Sound Maintainer; ALSA Project; Red Hat, Inc.
_______________________________________________
Alsa-devel mailing list
Alsa-devel@alsa-project.org
https://mailman.alsa-project.org/mailman/listinfo/alsa-devel
next prev parent reply other threads:[~2019-12-16 21:02 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-16 12:51 [alsa-devel] [alsa-lib][PATCH] conf: SOF-Intel: map pcm device for sof driver Hui Wang
2019-12-16 21:00 ` Jaroslav Kysela [this message]
2019-12-20 1:30 ` Hui Wang
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=084ab279-3eef-e1bb-070b-1e4f1c8f26c7@perex.cz \
--to=perex@perex.cz \
--cc=alsa-devel@alsa-project.org \
--cc=hui.wang@canonical.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox