From: "Gorski, Mateusz" <mateusz.gorski@linux.intel.com>
To: Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>,
alsa-devel@alsa-project.org
Cc: cezary.rojewski@intel.com, tiwai@suse.com
Subject: Re: [PATCH v2] topology: Add topology file for generic HDA DSP machine driver
Date: Wed, 25 Mar 2020 13:21:05 +0100 [thread overview]
Message-ID: <07efcaf1-c6fd-49f3-1e76-e20c370d4a70@linux.intel.com> (raw)
In-Reply-To: <00bd3e15-b088-c185-4473-8d928da01b9c@linux.intel.com>
>>
>> We have a mechanism to choose the PCM configuration of given topology
>> path via amixer control. That way we can include both 2ch and 4ch
>> DMIC configurations in one topology file and simply change DMIC
>> pipeline configuration on runtime.
>>
>> Unfortunately this mechanism is not currently available on upstream.
>>
>> As said before, this is a reference topology, if needed I can also
>> upload modified version with 4ch DMIC path.
>
> I don't understand the concept of 'reference topology'. It's not like
> anyone is going to modify this file, which is seriously cryptic, so
> it's got to be a 'usable topology', turn-key really.
>
> You would need three files, with no dmic, with 2 dmic with 4 dmic and
> a driver level code selection. Today the code loads the topology name
> coming from NHLT or dfw_sst.bin, you'd need a more elaborate logic to
> deal with the hardware variants and without requiring any fiddling,
> rename or edits of topology files.
>
>
I prepared 3 different topology .conf files and sent them in patch set.
These topologies cover all three cases (no DMIC, 2ch DMIC capture and
4ch DMIC capture). I also prepared and sent kernel patch adding third
way of selecting topology binary file so that its name depends on used
machine driver.
Thanks,
Mateusz
prev parent reply other threads:[~2020-03-25 12:22 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-09 12:09 [PATCH v2] topology: Add topology file for generic HDA DSP machine driver Mateusz Gorski
2020-03-09 17:10 ` Pierre-Louis Bossart
2020-03-11 9:13 ` Gorski, Mateusz
2020-03-11 14:48 ` Pierre-Louis Bossart
2020-03-13 7:08 ` Gorski, Mateusz
2020-03-13 16:13 ` Pierre-Louis Bossart
2020-03-25 12:21 ` Gorski, Mateusz [this message]
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=07efcaf1-c6fd-49f3-1e76-e20c370d4a70@linux.intel.com \
--to=mateusz.gorski@linux.intel.com \
--cc=alsa-devel@alsa-project.org \
--cc=cezary.rojewski@intel.com \
--cc=pierre-louis.bossart@linux.intel.com \
--cc=tiwai@suse.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.