From: Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>
To: Mark Brown <broonie@kernel.org>
Cc: Guenter Roeck <groeck@google.com>,
Liam Girdwood <lgirdwood@gmail.com>,
alsa-devel@alsa-project.org, linux-kernel@vger.kernel.org,
Takashi Iwai <tiwai@suse.com>,
Chintan Patel <chintan.m.patel@intel.com>,
Guenter Roeck <groeck@chromium.org>
Subject: Re: [alsa-devel] [RFC/RFT PATCH] ASoC: topology: Improve backwards compatibility with v4 topology files
Date: Wed, 23 May 2018 08:42:59 -0500 [thread overview]
Message-ID: <521b23cd-f083-6a19-1374-fde7057c869b@linux.intel.com> (raw)
In-Reply-To: <20180523082424.GA4828@sirena.org.uk>
On 5/23/18 3:24 AM, Mark Brown wrote:
> On Tue, May 22, 2018 at 02:59:35PM -0500, Pierre-Louis Bossart wrote:
>
>> I am also not convinced by the notion that maintaining topology files is
>> only a userspace/distro issue. This would mean some distros will have access
>> to the required topology files, possibly enabling DSP processing
>> capabilities, but other will not and will not be able to enable even basic
>> playback/capture. Just like we have a basic firmware with limited
>> functionality in /lib/firmware/intel, it would make sense to require a basic
>> .conf file in alsa-lib for every upstream machine driver - along possibly
>> with a basic UCM file so that audio works no matter what distro people use.
>
> The point here is that people should be able to update their kernel
> without updating their userspace so things have to work with whatever
> they have right now - anything that relies on shipping new firmware or
> configuration files to userspace is a problem.
Agree.
My point was a bit different: distributions like Gallium start without
the relevant topology files and UCM settings, and we should have a
reference to quickly enable audio without having to borrow and modify
files from another distro. I faced this issue when I worked with the
Gallium folks to enable audio on Rambi and Cyan Chromebooks and ended-up
creating this reference myself.
next prev parent reply other threads:[~2018-05-23 13:43 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-22 16:58 [RFC/RFT PATCH] ASoC: topology: Improve backwards compatibility with v4 topology files Guenter Roeck
2018-05-22 17:14 ` Mark Brown
2018-05-22 19:59 ` [alsa-devel] " Pierre-Louis Bossart
2018-05-23 8:24 ` Mark Brown
2018-05-23 13:42 ` Pierre-Louis Bossart [this message]
2018-05-23 13:56 ` Takashi Iwai
[not found] ` <CABXOdTdGyfBdZUzG-DzGgfr0Afrh9dtgdXibQreOZm7nb4z3=w@mail.gmail.com>
2018-05-23 14:58 ` Takashi Iwai
2018-05-23 15:52 ` Mark Brown
[not found] ` <CABXOdTd5+QJHOZ6BcSO-TfJCqcLzdd+Gbnf4HYh9i9cG+UH+1g@mail.gmail.com>
2018-05-23 9:49 ` Mark Brown
2018-05-23 13:54 ` Takashi Iwai
2018-05-23 13:56 ` Mark Brown
[not found] ` <CABXOdTeCr-ExO9O3XAHK-DnNf5yLGO0TPkXgs60TB90jGNB2_Q@mail.gmail.com>
2018-05-23 15:58 ` Mark Brown
2018-05-23 16:17 ` Guenter Roeck
2018-05-24 9:52 ` Takashi Iwai
2018-05-24 14:18 ` Mark Brown
2018-05-24 14:55 ` Guenter Roeck
2018-05-24 15:11 ` Mark Brown
2018-05-25 9:04 ` [alsa-devel] " Lin, Mengdong
2018-05-25 13:20 ` Guenter Roeck
2018-05-23 16:29 ` Guenter Roeck
2018-05-23 20:28 ` [alsa-devel] " Pierre-Louis Bossart
2018-05-23 21:22 ` Guenter Roeck
2018-05-24 3:38 ` Pierre-Louis Bossart
2018-05-25 13:40 ` Shreyas NC
2018-05-25 14:09 ` Guenter Roeck
2018-05-25 17:41 ` Guenter Roeck
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=521b23cd-f083-6a19-1374-fde7057c869b@linux.intel.com \
--to=pierre-louis.bossart@linux.intel.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=chintan.m.patel@intel.com \
--cc=groeck@chromium.org \
--cc=groeck@google.com \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).