From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S970596AbeEXOzZ (ORCPT ); Thu, 24 May 2018 10:55:25 -0400 Received: from mail-yb0-f196.google.com ([209.85.213.196]:34575 "EHLO mail-yb0-f196.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S966012AbeEXOzT (ORCPT ); Thu, 24 May 2018 10:55:19 -0400 X-Google-Smtp-Source: ADUXVKIX+0zRNO2M9LSMM1f2+KvZYvXAPxAQImK7y3CQspVN1I3KE8yMqjaGXISiU6pmWp/5CEQt15BD+jZOy/J42Ls= MIME-Version: 1.0 References: <20180522165842.233949-1-groeck@google.com> <20180523135609.GK4828@sirena.org.uk> <20180523155811.GO4828@sirena.org.uk> <20180524141842.GW4828@sirena.org.uk> In-Reply-To: <20180524141842.GW4828@sirena.org.uk> From: Guenter Roeck Date: Thu, 24 May 2018 07:55:06 -0700 Message-ID: Subject: Re: [RFC/RFT PATCH] ASoC: topology: Improve backwards compatibility with v4 topology files To: Mark Brown Cc: Takashi Iwai , Liam Girdwood , alsa-devel@alsa-project.org, Guenter Roeck , "Patel, Chintan M" , Jaroslav Kysela , linux-kernel Content-Type: text/plain; charset="UTF-8" Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thu, May 24, 2018 at 7:18 AM Mark Brown wrote: > On Wed, May 23, 2018 at 09:17:23AM -0700, Guenter Roeck wrote: > > On Wed, May 23, 2018 at 8:58 AM Mark Brown wrote: > > > I'm saying we should move them there. They're clearly part of the > > > userspace ABI and therefore belong in uapi, it was a mistake to let them > > > be elsewhere. > > They define a firmware file format. Not sure if I would call that userspace > > ABI. > It's a binary provided by userspace to the kernel, I'd say that's > clearly an ABI. > > I don't mind adding the structures to > > sound/soc/intel/skylake/skl-tplg-interface.h, > > but it seems a bit out of scope to tie this with moving the file to > > include/uapi/sound. > > I think that should be a separate discussion. > Is there some reason not to just do it while we're looking at this? I > don't see why we wouldn't want to do this. I don't mind doing this. However, keeping the change local and in a single patch would make it easier to backport, and I think that the ability to backport would be essential to get more than one-person test coverage. I also would have liked feedback from someone at Intel, at least for the Skylake specific structures. Anyway, what file do you have in mind for the structure definitions, both for the ones in soc-tolopogy.c and the ones needed in skl-topology.c ? Everything into asoc.h, or something else ? Guenter From mboxrd@z Thu Jan 1 00:00:00 1970 From: Guenter Roeck Subject: Re: [RFC/RFT PATCH] ASoC: topology: Improve backwards compatibility with v4 topology files Date: Thu, 24 May 2018 07:55:06 -0700 Message-ID: References: <20180522165842.233949-1-groeck@google.com> <20180523135609.GK4828@sirena.org.uk> <20180523155811.GO4828@sirena.org.uk> <20180524141842.GW4828@sirena.org.uk> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: Received: from mail-yb0-f196.google.com (mail-yb0-f196.google.com [209.85.213.196]) by alsa0.perex.cz (Postfix) with ESMTP id AAB9D266C1C for ; Thu, 24 May 2018 16:55:20 +0200 (CEST) Received: by mail-yb0-f196.google.com with SMTP id w14-v6so689607ybm.5 for ; Thu, 24 May 2018 07:55:20 -0700 (PDT) In-Reply-To: <20180524141842.GW4828@sirena.org.uk> 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: Mark Brown Cc: alsa-devel@alsa-project.org, Takashi Iwai , linux-kernel , Liam Girdwood , "Patel, Chintan M" , Guenter Roeck List-Id: alsa-devel@alsa-project.org On Thu, May 24, 2018 at 7:18 AM Mark Brown wrote: > On Wed, May 23, 2018 at 09:17:23AM -0700, Guenter Roeck wrote: > > On Wed, May 23, 2018 at 8:58 AM Mark Brown wrote: > > > I'm saying we should move them there. They're clearly part of the > > > userspace ABI and therefore belong in uapi, it was a mistake to let them > > > be elsewhere. > > They define a firmware file format. Not sure if I would call that userspace > > ABI. > It's a binary provided by userspace to the kernel, I'd say that's > clearly an ABI. > > I don't mind adding the structures to > > sound/soc/intel/skylake/skl-tplg-interface.h, > > but it seems a bit out of scope to tie this with moving the file to > > include/uapi/sound. > > I think that should be a separate discussion. > Is there some reason not to just do it while we're looking at this? I > don't see why we wouldn't want to do this. I don't mind doing this. However, keeping the change local and in a single patch would make it easier to backport, and I think that the ability to backport would be essential to get more than one-person test coverage. I also would have liked feedback from someone at Intel, at least for the Skylake specific structures. Anyway, what file do you have in mind for the structure definitions, both for the ones in soc-tolopogy.c and the ones needed in skl-topology.c ? Everything into asoc.h, or something else ? Guenter