All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mark Brown <broonie@kernel.org>
To: Guenter Roeck <groeck@google.com>
Cc: Liam Girdwood <lgirdwood@gmail.com>,
	Jaroslav Kysela <perex@perex.cz>, Takashi Iwai <tiwai@suse.com>,
	alsa-devel@alsa-project.org, linux-kernel@vger.kernel.org,
	Chintan Patel <chintan.m.patel@intel.com>,
	Guenter Roeck <groeck@chromium.org>,
	Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>
Subject: Re: [RFC/RFT PATCH] ASoC: topology: Improve backwards compatibility with v4 topology files
Date: Tue, 22 May 2018 18:14:31 +0100	[thread overview]
Message-ID: <20180522171431.GF24776@sirena.org.uk> (raw)
In-Reply-To: <20180522165842.233949-1-groeck@google.com>

[-- Attachment #1: Type: text/plain, Size: 1086 bytes --]

On Tue, May 22, 2018 at 09:58:42AM -0700, Guenter Roeck wrote:

> Both problems have been widely reported. Various attempts were made to
> fix the problem, usually by providing v5 configuration files. However,
> all those attempts result in incomplete ASoC configuration.

This is the first time I've heard that there were still ongoing issues,
it's extremely disappointing - I'm guessing the attempts have all been
at the distro level.  Userspace fixes clearly aren't the thing to do
here, as discussed at the time the original fixes were done this is an
ABI and needs to be treated as such.

None of the systems I have access to have ever used topology so I've had
poor visibility of how this is working in practice, I guess I'm going to
start seeing this stuff next time I upgrade my laptop (unless someone is
making suitable non-x86 laptops by then!).

> Let's implement backward compatibility properly to solve the problem
> for good.

Thanks for doing this.  I'll give this some time for review from the
Intel people - adding Pierre as well since this is a bit of a device
thing.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

WARNING: multiple messages have this Message-ID (diff)
From: Mark Brown <broonie@kernel.org>
To: Guenter Roeck <groeck@google.com>
Cc: Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>,
	alsa-devel@alsa-project.org, Liam Girdwood <lgirdwood@gmail.com>,
	linux-kernel@vger.kernel.org, Takashi Iwai <tiwai@suse.com>,
	Chintan Patel <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: Tue, 22 May 2018 18:14:31 +0100	[thread overview]
Message-ID: <20180522171431.GF24776@sirena.org.uk> (raw)
In-Reply-To: <20180522165842.233949-1-groeck@google.com>


[-- Attachment #1.1: Type: text/plain, Size: 1086 bytes --]

On Tue, May 22, 2018 at 09:58:42AM -0700, Guenter Roeck wrote:

> Both problems have been widely reported. Various attempts were made to
> fix the problem, usually by providing v5 configuration files. However,
> all those attempts result in incomplete ASoC configuration.

This is the first time I've heard that there were still ongoing issues,
it's extremely disappointing - I'm guessing the attempts have all been
at the distro level.  Userspace fixes clearly aren't the thing to do
here, as discussed at the time the original fixes were done this is an
ABI and needs to be treated as such.

None of the systems I have access to have ever used topology so I've had
poor visibility of how this is working in practice, I guess I'm going to
start seeing this stuff next time I upgrade my laptop (unless someone is
making suitable non-x86 laptops by then!).

> Let's implement backward compatibility properly to solve the problem
> for good.

Thanks for doing this.  I'll give this some time for review from the
Intel people - adding Pierre as well since this is a bit of a device
thing.

[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

[-- Attachment #2: Type: text/plain, Size: 0 bytes --]



  reply	other threads:[~2018-05-22 17:15 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 [this message]
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           ` [alsa-devel] " Takashi Iwai
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=20180522171431.GF24776@sirena.org.uk \
    --to=broonie@kernel.org \
    --cc=alsa-devel@alsa-project.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=perex@perex.cz \
    --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.