From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S933222AbeEWN4m (ORCPT ); Wed, 23 May 2018 09:56:42 -0400 Received: from mx2.suse.de ([195.135.220.15]:59575 "EHLO mx2.suse.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S932900AbeEWN4l (ORCPT ); Wed, 23 May 2018 09:56:41 -0400 Date: Wed, 23 May 2018 15:56:40 +0200 Message-ID: From: Takashi Iwai To: "Pierre-Louis Bossart" Cc: "Mark Brown" , , "Guenter Roeck" , "Liam Girdwood" , "Guenter Roeck" , "Chintan Patel" , Subject: Re: [alsa-devel] [RFC/RFT PATCH] ASoC: topology: Improve backwards compatibility with v4 topology files In-Reply-To: <521b23cd-f083-6a19-1374-fde7057c869b@linux.intel.com> References: <20180522165842.233949-1-groeck@google.com> <20180523082424.GA4828@sirena.org.uk> <521b23cd-f083-6a19-1374-fde7057c869b@linux.intel.com> User-Agent: Wanderlust/2.15.9 (Almost Unreal) SEMI/1.14.6 (Maruoka) FLIM/1.14.9 (=?UTF-8?B?R29qxY0=?=) APEL/10.8 Emacs/25.3 (x86_64-suse-linux-gnu) MULE/6.0 (HANACHIRUSATO) MIME-Version: 1.0 (generated by SEMI 1.14.6 - "Maruoka") Content-Type: text/plain; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, 23 May 2018 15:42:59 +0200, Pierre-Louis Bossart wrote: > > 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. This sounds rather like a question how the upstream distributes the stuff properly... thanks, Takashi From mboxrd@z Thu Jan 1 00:00:00 1970 From: Takashi Iwai Subject: Re: [alsa-devel] [RFC/RFT PATCH] ASoC: topology: Improve backwards compatibility with v4 topology files Date: Wed, 23 May 2018 15:56:40 +0200 Message-ID: References: <20180522165842.233949-1-groeck@google.com> <20180523082424.GA4828@sirena.org.uk> <521b23cd-f083-6a19-1374-fde7057c869b@linux.intel.com> Mime-Version: 1.0 (generated by SEMI 1.14.6 - "Maruoka") Content-Type: text/plain; charset=US-ASCII Return-path: In-Reply-To: <521b23cd-f083-6a19-1374-fde7057c869b@linux.intel.com> Sender: linux-kernel-owner@vger.kernel.org To: Pierre-Louis Bossart Cc: Mark Brown , alsa-devel@alsa-project.org, Guenter Roeck , Liam Girdwood , Guenter Roeck , Chintan Patel , linux-kernel@vger.kernel.org List-Id: alsa-devel@alsa-project.org On Wed, 23 May 2018 15:42:59 +0200, Pierre-Louis Bossart wrote: > > 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. This sounds rather like a question how the upstream distributes the stuff properly... thanks, Takashi