[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <0015aace-fe32-9707-d3c9-0dea6f5fc48c@roeck-us.net>
Date: Fri, 1 Jun 2018 06:17:05 -0700
From: Guenter Roeck <linux@...ck-us.net>
To: Mark Brown <broonie@...nel.org>
Cc: Takashi Iwai <tiwai@...e.com>, Liam Girdwood <lgirdwood@...il.com>,
Jaroslav Kysela <perex@...ex.cz>,
Chintan Patel <chintan.m.patel@...el.com>,
alsa-devel@...a-project.org, linux-kernel@...r.kernel.org,
Pierre-Louis Bossart <pierre-louis.bossart@...ux.intel.com>,
Guenter Roeck <groeck@...omium.org>
Subject: Re: [PATCH v2 1/3] ASoC: topology: Improve backwards compatibility
with v4 topology files
On 06/01/2018 03:25 AM, Mark Brown wrote:
> On Thu, May 24, 2018 at 12:49:21PM -0700, Guenter Roeck wrote:
>> From: Guenter Roeck <groeck@...omium.org>
>>
>> Commit dc31e741db49 ("ASoC: topology: ABI - Add the types for BE
>> DAI") introduced sound topology files version 5. Initially, this
>> change made the topology code incompatible with v4 topology files.
>
> No review on these from anyone at Intel?
>
The only actionable feedback I have seen is that the header file
changes should be in uapi, which is done in patches 2 and 3.
Other than that, there was a question if this is a Linux issue or
a Chromebook issue (it appears that only Chromebooks shipped with
v4 configuration files). I took that as rhetorical since upstream
kernels (at least v4.4 and v4.5) support topology v4 configuration
files, and it should not matter which products shipped using those.
Guenter
Powered by blists - more mailing lists