From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-5.8 required=3.0 tests=DKIM_SIGNED,DKIM_VALID, HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,MENTIONS_GIT_HOSTING, SPF_HELO_NONE,SPF_PASS,URIBL_BLOCKED autolearn=ham autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 4359EC5DF60 for ; Thu, 7 Nov 2019 06:49:56 +0000 (UTC) Received: from alsa0.perex.cz (alsa0.perex.cz [77.48.224.243]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPS id 3D63621D79 for ; Thu, 7 Nov 2019 06:49:54 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (1024-bit key) header.d=alsa-project.org header.i=@alsa-project.org header.b="lz1OIMML" DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org 3D63621D79 Authentication-Results: mail.kernel.org; dmarc=none (p=none dis=none) header.from=suse.de Authentication-Results: mail.kernel.org; spf=pass smtp.mailfrom=alsa-devel-bounces@alsa-project.org Received: from alsa1.perex.cz (alsa1.perex.cz [207.180.221.201]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by alsa0.perex.cz (Postfix) with ESMTPS id D345842; Thu, 7 Nov 2019 07:49:02 +0100 (CET) DKIM-Filter: OpenDKIM Filter v2.11.0 alsa0.perex.cz D345842 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=alsa-project.org; s=default; t=1573109392; bh=iCsFS0roQ77794J1Qe+KIheGLnNA0XVukXtFyLEmKTY=; h=Date:From:To:In-Reply-To:References:Cc:Subject:List-Id: List-Unsubscribe:List-Archive:List-Post:List-Help:List-Subscribe: From; b=lz1OIMML4tXuz3nVCJJOFqrHdvfkDzAlF/AOu36iqEo6IKwRJXqsrUb6e+L7BptPl Hyb16jcqaDgrrS4ndtJ/QVpbx/ZxP919BbiWg95LbdeFO2WhBazcEg4qiJS3TFRLp8 alkY5FYF85+P0+hvPdd/+TgdLxcJgGkWmdGU3k9o= Received: from alsa1.perex.cz (localhost.localdomain [127.0.0.1]) by alsa1.perex.cz (Postfix) with ESMTP id 4728FF80446; Thu, 7 Nov 2019 07:49:02 +0100 (CET) Received: by alsa1.perex.cz (Postfix, from userid 50401) id DBDD6F8049B; Thu, 7 Nov 2019 07:48:59 +0100 (CET) Received: from mx1.suse.de (mx2.suse.de [195.135.220.15]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by alsa1.perex.cz (Postfix) with ESMTPS id 1BC70F800F3 for ; Thu, 7 Nov 2019 07:48:56 +0100 (CET) DKIM-Filter: OpenDKIM Filter v2.11.0 alsa1.perex.cz 1BC70F800F3 X-Virus-Scanned: by amavisd-new at test-mx.suse.de Received: from relay2.suse.de (unknown [195.135.220.254]) by mx1.suse.de (Postfix) with ESMTP id 5B03CAF6B; Thu, 7 Nov 2019 06:48:55 +0000 (UTC) Date: Thu, 07 Nov 2019 07:48:54 +0100 Message-ID: From: Takashi Iwai To: Jaroslav Kysela In-Reply-To: <6dcc3e0d-0df5-90cf-220f-59253d3b5c7c@perex.cz> References: <6dcc3e0d-0df5-90cf-220f-59253d3b5c7c@perex.cz> 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") Cc: ALSA development , Mark Brown , Kai Vehmanen Subject: Re: [alsa-devel] UCM extensions X-BeenThere: alsa-devel@alsa-project.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: "Alsa-devel mailing list for ALSA developers - http://www.alsa-project.org" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Errors-To: alsa-devel-bounces@alsa-project.org Sender: "Alsa-devel" On Tue, 05 Nov 2019 20:36:28 +0100, Jaroslav Kysela wrote: > > Hi all, > > I make some internal ucm code cleanups in alsa-lib and added > three major extensions to allow more complex configurations which we > require for the SOF kernel driver. > > The first thing is the added substitution for the value strings: > > https://github.com/alsa-project/alsa-lib/commit/f1e637b285e8e04e6761248a070f58f3a8fde6fc > > The second thing is the If block: > > https://github.com/alsa-project/alsa-lib/commit/985715ce8148dc7ef62c8e3d8ce5a0c2ac51f8df > > The third thing is the card / hardware like specifier passed > as the ucm name to snd_use_case_mgr_open() to support multiple card > instances: > > https://github.com/alsa-project/alsa-lib/commit/60164fc5886cdc6ca55eeed0c2e3f751a7d2b2c0 > > All those patches (with other cleanups) are in the ucm2 branch > on github for comments: > > https://github.com/alsa-project/alsa-lib/commits/ucm2 > > The proposed SOF UCM config diff is here: > > https://github.com/alsa-project/alsa-ucm-conf/commit/723b6da881721488229154e923ed36413955a051 > https://github.com/alsa-project/alsa-ucm-conf/commits/ucm2 > > I added everything to keep the interface backward compatible, > so the current applications should not observe any different > behavior. The applications like pulseaudio should use the > 'hw:CARD_INDEX' specifier for the open call in the future and > snd_use_case_parse_ctl_elem_id() helper for the element control names. The only concern with these extensions so far is the compatibility. Imagine that people run the new profile on the old parser, it'd break easily. I think other scripts often installing on the versioned directory if incompatibilities are seen. Can we do that for UCM as well? Or course, once after UCM parser is changed to be future-ready and allow some syntax for possible future extensions, we can keep that version directory in future, too. thanks, Takashi _______________________________________________ Alsa-devel mailing list Alsa-devel@alsa-project.org https://mailman.alsa-project.org/mailman/listinfo/alsa-devel