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 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 C8A74C54FCB for ; Wed, 22 Apr 2020 20:24:34 +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 4E1A920857 for ; Wed, 22 Apr 2020 20:24:34 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (1024-bit key) header.d=alsa-project.org header.i=@alsa-project.org header.b="GUHFvZDs" DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org 4E1A920857 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 94EBE169B; Wed, 22 Apr 2020 22:23:42 +0200 (CEST) DKIM-Filter: OpenDKIM Filter v2.11.0 alsa0.perex.cz 94EBE169B DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=alsa-project.org; s=default; t=1587587072; bh=nSHoD5R5XnFFR6Rz98j4QhvoxxJ61DndzPy3X6Q0JlE=; h=Date:From:To:Subject:In-Reply-To:References:Cc:List-Id: List-Unsubscribe:List-Archive:List-Post:List-Help:List-Subscribe: From; b=GUHFvZDsaOS5Bs/fcV/3e1h9h8KEYpazI806zPQEcV0xnoMr7SBgc909sm7rW3llr O2FUcsiqTMRn3ZyAh0cQTc/17WpBW+wt3f8ziwSXwVpE7dDBHXrYfCXojQApgt6B36 oMMGhN3jCSeD+AQUNc8NV9hkjuN4FEp7Sbg0/yak= Received: from alsa1.perex.cz (localhost.localdomain [127.0.0.1]) by alsa1.perex.cz (Postfix) with ESMTP id 25146F80142; Wed, 22 Apr 2020 22:23:42 +0200 (CEST) Received: by alsa1.perex.cz (Postfix, from userid 50401) id D0656F801D9; Wed, 22 Apr 2020 22:23:39 +0200 (CEST) Received: from mx2.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 66AADF800F2 for ; Wed, 22 Apr 2020 22:23:36 +0200 (CEST) DKIM-Filter: OpenDKIM Filter v2.11.0 alsa1.perex.cz 66AADF800F2 X-Virus-Scanned: by amavisd-new at test-mx.suse.de Received: from relay2.suse.de (unknown [195.135.220.254]) by mx2.suse.de (Postfix) with ESMTP id E85D0AE9A; Wed, 22 Apr 2020 20:23:34 +0000 (UTC) Date: Wed, 22 Apr 2020 22:23:34 +0200 Message-ID: From: Takashi Iwai To: Jaroslav Kysela Subject: Re: ASoC driver names In-Reply-To: References: 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") Content-Type: text/plain; charset=US-ASCII Cc: ALSA development , Mark Brown , Srinivas Kandagatla , Pierre-louis Bossart 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: , Errors-To: alsa-devel-bounces@alsa-project.org Sender: "Alsa-devel" On Wed, 22 Apr 2020 19:04:36 +0200, Jaroslav Kysela wrote: > > Hi all, > > I am fighting actually with the ASoC driver names. The current > situation, where each hardware variant (card name) is mapped to the > driver name is not very practical (and not correct). The driver name > should describe the common part (usually the controller - like > 'HDA-Intel' or bus 'USB-Audio'). > > I am talking about the situation, where the ASoC card name is set > via the device tree (snd_soc_of_parse_card_name) like in [1], but the > change may be considered for other drivers like Intel SST: > > Card driver name: Lenovo-YOGA-C63 > Card name: Lenovo-YOGA-C630-13Q50 > Card long name: LENOVO-81JL-LenovoYOGAC630_13Q50-LNVNB161216 > > [1] > https://github.com/alsa-project/alsa-tests/pull/3/commits/1b5a552cff06c6039fbcf41b3117fc73712010df > > My question is, can we change / add the more apropriate driver names > conditionally with a new kernel CONFIG option? Will you accept this > change? It's a last resort, but it's more or less acceptable, IMO. > The goal is to group the related UCM2 configurations and do the > required split inside the UCM2 top-level configuration file based on > card components string or other card identificators (related to the > driver). Wasn't an idea to use the component string feasible? e.g. if a driver sets a certain component string, it's preferred over the standard driver name / long name mapping. thanks, Takashi