All of lore.kernel.org
 help / color / mirror / Atom feed
From: Takashi Iwai <tiwai@suse.de>
To: Guenter Roeck <groeck@google.com>
Cc: pierre-louis.bossart@linux.intel.com,
	Mark Brown <broonie@kernel.org>,
	alsa-devel@alsa-project.org, Guenter Roeck <groeck@chromium.org>,
	Liam Girdwood <lgirdwood@gmail.com>,
	"Patel, Chintan M" <chintan.m.patel@intel.com>,
	linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [alsa-devel] [RFC/RFT PATCH] ASoC: topology: Improve backwards compatibility with v4 topology files
Date: Wed, 23 May 2018 16:58:48 +0200	[thread overview]
Message-ID: <s5h4liypgev.wl-tiwai@suse.de> (raw)
In-Reply-To: <CABXOdTdGyfBdZUzG-DzGgfr0Afrh9dtgdXibQreOZm7nb4z3=w@mail.gmail.com>

On Wed, 23 May 2018 16:49:35 +0200,
Guenter Roeck wrote:
> 
> On Wed, May 23, 2018 at 6:56 AM Takashi Iwai <tiwai@suse.de> 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

WARNING: multiple messages have this Message-ID (diff)
From: Takashi Iwai <tiwai@suse.de>
To: Guenter Roeck <groeck@google.com>
Cc: alsa-devel@alsa-project.org,
	linux-kernel <linux-kernel@vger.kernel.org>,
	pierre-louis.bossart@linux.intel.com,
	Liam Girdwood <lgirdwood@gmail.com>,
	Mark Brown <broonie@kernel.org>,
	"Patel, Chintan M" <chintan.m.patel@intel.com>,
	Guenter Roeck <groeck@chromium.org>
Subject: Re: [RFC/RFT PATCH] ASoC: topology: Improve backwards compatibility with v4 topology files
Date: Wed, 23 May 2018 16:58:48 +0200	[thread overview]
Message-ID: <s5h4liypgev.wl-tiwai@suse.de> (raw)
In-Reply-To: <CABXOdTdGyfBdZUzG-DzGgfr0Afrh9dtgdXibQreOZm7nb4z3=w@mail.gmail.com>

On Wed, 23 May 2018 16:49:35 +0200,
Guenter Roeck wrote:
> 
> On Wed, May 23, 2018 at 6:56 AM Takashi Iwai <tiwai@suse.de> 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

  reply	other threads:[~2018-05-23 14:58 UTC|newest]

Thread overview: 42+ 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 17:14   ` Mark Brown
2018-05-22 19:59 ` [alsa-devel] " Pierre-Louis Bossart
2018-05-22 21:59   ` Guenter Roeck
2018-05-23  9:49     ` [alsa-devel] " Mark Brown
2018-05-23  9:49       ` Mark Brown
2018-05-23 13:15       ` Guenter Roeck
2018-05-23  8:24   ` [alsa-devel] " Mark Brown
2018-05-23  8:24     ` Mark Brown
2018-05-23 13:42     ` [alsa-devel] " Pierre-Louis Bossart
2018-05-23 13:42       ` Pierre-Louis Bossart
2018-05-23 13:56       ` [alsa-devel] " Takashi Iwai
2018-05-23 13:56         ` Takashi Iwai
2018-05-23 14:49         ` Guenter Roeck
2018-05-23 14:58           ` Takashi Iwai [this message]
2018-05-23 14:58             ` Takashi Iwai
2018-05-23 15:52           ` [alsa-devel] " Mark Brown
2018-05-23 13:54 ` Takashi Iwai
2018-05-23 13:54   ` Takashi Iwai
2018-05-23 13:56   ` Mark Brown
2018-05-23 13:56     ` Mark Brown
2018-05-23 15:54     ` Guenter Roeck
2018-05-23 15:58       ` Mark Brown
2018-05-23 15:58         ` Mark Brown
2018-05-23 16:17         ` Guenter Roeck
2018-05-24  9:52           ` Takashi Iwai
2018-05-24  9:52             ` Takashi Iwai
2018-05-24 14:18           ` Mark Brown
2018-05-24 14:18             ` Mark Brown
2018-05-24 14:55             ` Guenter Roeck
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=s5h4liypgev.wl-tiwai@suse.de \
    --to=tiwai@suse.de \
    --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=pierre-louis.bossart@linux.intel.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.