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] ASoC: Intel: Skylake: Add alternative topology binary name
Date: Thu, 2 Apr 2020 16:40:38 +0200 [thread overview]
Message-ID: <d343fc58-5a8a-02db-bb1e-d45b408a0750@linux.intel.com> (raw)
In-Reply-To: <6ae14d4b-41e2-c48c-d0de-24a692468009@linux.intel.com>
>>
>> The intention of this patch was not to deal with the different DMIC
>> configurations problem. It only simplifies the topology binary
>> selection. As you mentioned in one of previous mails, currently there
>> are two options:
>>
>> - name based on NHLT, which is pretty complicated, especially for end
>> user, and is also depending on things like OEM name so the same
>> topology will need to be renamed multiple times different devices
>> (additionally, there are laptops on the market that do not have NHLT
>> table at all)
>>
>> - dfw_sst.bin, which is only a fallback binary name and should not be
>> actually used because it could be misleading for users/distro
>> intergrators
>>
>> This change adds the third option, which is, in my opinion, the right
>> way to deal with this problem. This name is simpler, does not depend
>> on existence of NHLT, and makes life easier for users/distros.
>
> Right, and that's fine to avoid the NHLT-name and dfw_sst.bin, no
> issue here. The point is to go one step further and require ZERO
> configuration from users.
>
>> And as for the mentioned DMIC confguration problem - I am doing a
>> research to find the simplest way to deal with this.
>
> Just append the number of mics detected to the topology file name?
> Asking users to copy/symlink hda_dsp_DMIC_2ch.tplg as hda-dsp.tplg
> doesn't really help, you can make things simpler.
Sent another patch to add path multiconfiguration feature to the driver.
This way we will have one topology binary for multiple DMIC
configurations, so we do not need to select different file according to
its name. Also new version of topology conf was provided, the one with
multiple configs.
Thanks,
Mateusz
next prev parent reply other threads:[~2020-04-02 14:41 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-25 12:22 [PATCH] ASoC: Intel: Skylake: Add alternative topology binary name Mateusz Gorski
2020-03-25 14:33 ` Pierre-Louis Bossart
2020-03-26 15:00 ` Gorski, Mateusz
2020-03-26 15:26 ` Pierre-Louis Bossart
2020-04-02 14:40 ` Gorski, Mateusz [this message]
-- strict thread matches above, loose matches on Subject: below --
2020-11-03 14:10 Mateusz Gorski
2020-11-03 14:10 ` Mateusz Gorski
2020-11-03 15:35 ` Greg KH
2020-11-03 15:35 ` Greg KH
2020-11-04 11:46 ` Gorski, Mateusz
2020-11-04 11:46 ` Gorski, Mateusz
2020-11-04 11:58 ` Greg KH
2020-11-04 11:58 ` Greg KH
2020-11-08 16:17 ` Rojewski, Cezary
2020-11-08 16:17 ` Rojewski, Cezary
2020-11-08 17:00 ` Greg KH
2020-11-08 17:00 ` Greg KH
2020-11-09 8:38 ` Rojewski, Cezary
2020-11-09 8:38 ` Rojewski, Cezary
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=d343fc58-5a8a-02db-bb1e-d45b408a0750@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.