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 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 6A19DC433EF for ; Fri, 1 Oct 2021 06:49: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 09FEA615A4 for ; Fri, 1 Oct 2021 06:49:32 +0000 (UTC) DMARC-Filter: OpenDMARC Filter v1.4.1 mail.kernel.org 09FEA615A4 Authentication-Results: mail.kernel.org; dmarc=none (p=none dis=none) header.from=renesas.com Authentication-Results: mail.kernel.org; spf=pass smtp.mailfrom=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 DBE4A16CE; Fri, 1 Oct 2021 08:48:40 +0200 (CEST) DKIM-Filter: OpenDKIM Filter v2.11.0 alsa0.perex.cz DBE4A16CE DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=alsa-project.org; s=default; t=1633070971; bh=0NPOueqlyqMUIqL0DKwXRxkFYkcsamhYE+ipkUIihPI=; h=Date:From:To:Subject:In-Reply-To:References:Cc:List-Id: List-Unsubscribe:List-Archive:List-Post:List-Help:List-Subscribe: From; b=ZiwM+w16N4i29LrWipbZI3TfCNK5CS4+fiouBcbHCHd2mDyu/zM13TTGqtC3TmbVU gHYAQK4MnX5eLR+suBa7GrM3CctSLdlgKgvQ8qmbaZ0GXAJoq70osiTkugyeJBvNN4 fFyNXRZxgC1zbIKd+yJ2gWXCejJFGhttzuAXSlWU= Received: from alsa1.perex.cz (localhost.localdomain [127.0.0.1]) by alsa1.perex.cz (Postfix) with ESMTP id 5EB5CF80227; Fri, 1 Oct 2021 08:48:40 +0200 (CEST) Received: by alsa1.perex.cz (Postfix, from userid 50401) id 55876F80245; Fri, 1 Oct 2021 08:48:39 +0200 (CEST) Received: from relmlie5.idc.renesas.com (relmlor1.renesas.com [210.160.252.171]) by alsa1.perex.cz (Postfix) with ESMTP id 8FB89F800F3 for ; Fri, 1 Oct 2021 08:48:31 +0200 (CEST) DKIM-Filter: OpenDKIM Filter v2.11.0 alsa1.perex.cz 8FB89F800F3 Date: 01 Oct 2021 15:48:26 +0900 X-IronPort-AV: E=Sophos;i="5.85,337,1624287600"; d="scan'208";a="95626374" Received: from unknown (HELO relmlir6.idc.renesas.com) ([10.200.68.152]) by relmlie5.idc.renesas.com with ESMTP; 01 Oct 2021 15:48:26 +0900 Received: from mercury.renesas.com (unknown [10.166.252.133]) by relmlir6.idc.renesas.com (Postfix) with ESMTP id 99F804228ED5; Fri, 1 Oct 2021 15:48:26 +0900 (JST) Message-ID: <87a6jt9r5x.wl-kuninori.morimoto.gx@renesas.com> From: Kuninori Morimoto To: =?UTF-8?Q?P=c3=a9ter_Ujfalusi?= Subject: Re: [PATCH v3 00/16] ASoC: Add Rich Graph Card support In-Reply-To: References: <87tuitusy4.wl-kuninori.morimoto.gx@renesas.com> User-Agent: Wanderlust/2.15.9 Emacs/26.3 Mule/6.0 MIME-Version: 1.0 (generated by SEMI-EPG 1.14.7 - "Harue") Content-Type: text/plain; charset=US-ASCII Cc: Linux-ALSA , Mark Brown , Rob Herring 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" Hi Peter, Mark Thank you for your feedback > I understand is that naming is difficult, but a rich-graph-card sounds a > bit awkward? > Will we see a wealthy-graph-card if the rich is not resourceful enough? ;) > > The current generation of graph based generic audio card is > audio-graph-card > > This is going to be an (incompatible) evolution, the Next/New > Generation. Would it sound better if it is named > audio-graph-card-ng / ng-audio-graph-card > > The 'rich' sound really out of place (if not rich then poor?). > > Next Generation, New Generation, Extended, etc > or just drop the graph and > generic-audio-card To be honest, I don't think this version will be final version of Generic audio card driver. We will want to have more advanced generic audio card if framework was updated, and/or new feature was added, and/or want to use more complex connection, etc, etc, etc... In such case, because of Device-Tree, it is very difficult to update driver with keeping compatibility. This means, we need to keep old version generic audio card as-is, and add new generic audio card, like this version. New / Next / Extended / Rich are not best naming IMO. For example, we will confuse if we add new generic audio card at 10 years later (It should be more new/next/extended/rich than this version). And yes, people should not feel bad from driver naming. Thus, my honest opinion is that using v2, v3, ... is easy to understand, especially for audio-graph-card. (audio-graph-card2, audio-graph-card3, ...) But, any naming is very welcome for me if Mark and/or all people are accepted. Thank you for your help !! Best regards --- Kuninori Morimoto