From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S933439AbeEWO6v (ORCPT ); Wed, 23 May 2018 10:58:51 -0400 Received: from mx2.suse.de ([195.135.220.15]:37452 "EHLO mx2.suse.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S933232AbeEWO6t (ORCPT ); Wed, 23 May 2018 10:58:49 -0400 Date: Wed, 23 May 2018 16:58:48 +0200 Message-ID: From: Takashi Iwai To: Guenter Roeck Cc: pierre-louis.bossart@linux.intel.com, Mark Brown , alsa-devel@alsa-project.org, Guenter Roeck , Liam Girdwood , "Patel, Chintan M" , linux-kernel Subject: Re: [alsa-devel] [RFC/RFT PATCH] ASoC: topology: Improve backwards compatibility with v4 topology files In-Reply-To: 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 16:49:35 +0200, Guenter Roeck wrote: > > On Wed, May 23, 2018 at 6:56 AM Takashi Iwai wrote: > > > > > > > > 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... > > > Not really, or not only. My problem, in particular, is that I want (need) > to be able to run different kernel versions with the same distribution, and > I want to be able to swap kernel versions without having to update the root > file system. That doesn't work if I have to use v4 configuration files for > v4.4 and older kernels, and v5 configuration files for v4.9 and later > kernels (besides, as I mentioned, that the v5 configuration files I found > were all incomplete). In my opinion, thre should be exactly one > configuration file for a given device, and there should be no need for > users (or distributions) to hunt for the correct version of the file. No doubt about the kernel backward compatibility, it should be supported. It's another problem, though, that downstream takes some wild stuff without properly upstreaming. A known story everywhere. Takashi From mboxrd@z Thu Jan 1 00:00:00 1970 From: Takashi Iwai Subject: Re: [RFC/RFT PATCH] ASoC: topology: Improve backwards compatibility with v4 topology files Date: Wed, 23 May 2018 16:58:48 +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" Content-Transfer-Encoding: 7bit Return-path: Received: from mx2.suse.de (mx2.suse.de [195.135.220.15]) by alsa0.perex.cz (Postfix) with ESMTP id A0B2E26705D for ; Wed, 23 May 2018 16:58:49 +0200 (CEST) In-Reply-To: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: alsa-devel-bounces@alsa-project.org Sender: alsa-devel-bounces@alsa-project.org To: Guenter Roeck Cc: alsa-devel@alsa-project.org, linux-kernel , pierre-louis.bossart@linux.intel.com, Liam Girdwood , Mark Brown , "Patel, Chintan M" , Guenter Roeck List-Id: alsa-devel@alsa-project.org On Wed, 23 May 2018 16:49:35 +0200, Guenter Roeck wrote: > > On Wed, May 23, 2018 at 6:56 AM Takashi Iwai wrote: > > > > > > > > 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... > > > Not really, or not only. My problem, in particular, is that I want (need) > to be able to run different kernel versions with the same distribution, and > I want to be able to swap kernel versions without having to update the root > file system. That doesn't work if I have to use v4 configuration files for > v4.4 and older kernels, and v5 configuration files for v4.9 and later > kernels (besides, as I mentioned, that the v5 configuration files I found > were all incomplete). In my opinion, thre should be exactly one > configuration file for a given device, and there should be no need for > users (or distributions) to hunt for the correct version of the file. No doubt about the kernel backward compatibility, it should be supported. It's another problem, though, that downstream takes some wild stuff without properly upstreaming. A known story everywhere. Takashi