From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mx1.sberdevices.ru (mx1.sberdevices.ru [37.18.73.165]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id 2055C1448E8; Mon, 8 Apr 2024 18:40:43 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=37.18.73.165 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1712601647; cv=none; b=J1e/EVHUBouf8ihisAJZWZCqAQzPHJxT8vgwOyfAUQWkj8/DU5HtZUMP8M/hM8AspNybdSB0qpKGB0dSX0OG0+Orqqgq5Rxu1KFbrSRTTz3w+ZkuXsZ80bRqC/kWnP5cX3nEwbLf+azpKctmVTPJgQTzEAY8Lq1F+aySXr9Xcvk= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1712601647; c=relaxed/simple; bh=TWMhq47+AaotDo5kYErPNH/lOTLWt7BalzXTfwvRjFc=; h=Date:From:To:CC:Subject:Message-ID:References:MIME-Version: Content-Type:Content-Disposition:In-Reply-To; b=Vq8MK7OIVuM3/dlxmwrYbtqd2OyT6XlHHyUX2v9ptEBualVin0lT8KGRp+LkjtL2wbFwO3K6U5kBNK6joVuKxyKFpUCPOELzW7jq39DiK8rrhHgTy06IRDKZwwAWMCp4UiYxE6AXAl8V5tpa/BbSnY+N4Iv6P0zYgREVBHmXMOc= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=salutedevices.com; spf=pass smtp.mailfrom=salutedevices.com; dkim=pass (2048-bit key) header.d=salutedevices.com header.i=@salutedevices.com header.b=WKgeijvs; arc=none smtp.client-ip=37.18.73.165 Authentication-Results: smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=salutedevices.com Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=salutedevices.com Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=salutedevices.com header.i=@salutedevices.com header.b="WKgeijvs" Received: from p-infra-ksmg-sc-msk01 (localhost [127.0.0.1]) by mx1.sberdevices.ru (Postfix) with ESMTP id B0C57100041; Mon, 8 Apr 2024 21:40:41 +0300 (MSK) DKIM-Filter: OpenDKIM Filter v2.11.0 mx1.sberdevices.ru B0C57100041 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=salutedevices.com; s=mail; t=1712601641; bh=FdcH8XsrOUDq4JN+ynsMalsWgvjtdzSqlvJuabgOE4Q=; h=Date:From:To:Subject:Message-ID:MIME-Version:Content-Type:From; b=WKgeijvszbZNG4oHb9dvfXyoDaxkAcJv+EvtPvl4uKNnpAKYKomAp7w2ZQfMl4hFD aN8wC7k5qy/UiNyA70xZbSY7mlgaycttMGp9nKlj+BJenLdaWgKcl38JKCtsp7iltT wy99Rdo3wqOJaopej7Yo6jNcAfuTG7pTRzArOwuTjvztknyySbgZKrN63Rfsuo0Qsu jGwFkqe0Ltap0+M95yCLhx1X5b/jJS0YR2gcG4FGhy8KWVm5Z74XV64p4eCSzavvpm neLw/nIPW6Zr9X8WcYCx9tF2TsQoX6PD1uRInZgHh3bpmK1Qrh8rtuHgfxxKmjyk/G Fd1sXxO9zeOTQ== Received: from smtp.sberdevices.ru (p-i-exch-sc-m02.sberdevices.ru [172.16.192.103]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx1.sberdevices.ru (Postfix) with ESMTPS; Mon, 8 Apr 2024 21:40:41 +0300 (MSK) Received: from localhost (100.64.160.123) by p-i-exch-sc-m02.sberdevices.ru (172.16.192.103) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.2.1118.40; Mon, 8 Apr 2024 21:40:41 +0300 Date: Mon, 8 Apr 2024 21:40:41 +0300 From: Dmitry Rokosov To: Jerome Brunet CC: , , , , , , , , , , , , , , , , , Subject: Re: [PATCH v1 2/2] ASoC: meson: implement link-name optional property in meson card utils Message-ID: <20240408184041.3jcav5tabxiblpn4@CAB-WSD-L081021> References: <20240408164947.30717-1-ddrokosov@salutedevices.com> <20240408164947.30717-3-ddrokosov@salutedevices.com> <1j1q7fpv1n.fsf@starbuckisacylon.baylibre.com> Precedence: bulk X-Mailing-List: linux-kernel@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Disposition: inline In-Reply-To: <1j1q7fpv1n.fsf@starbuckisacylon.baylibre.com> User-Agent: NeoMutt/20220415 X-ClientProxiedBy: p-i-exch-sc-m01.sberdevices.ru (172.16.192.107) To p-i-exch-sc-m02.sberdevices.ru (172.16.192.103) X-KSMG-Rule-ID: 10 X-KSMG-Message-Action: clean X-KSMG-AntiSpam-Lua-Profiles: 184624 [Apr 08 2024] X-KSMG-AntiSpam-Version: 6.1.0.4 X-KSMG-AntiSpam-Envelope-From: ddrokosov@salutedevices.com X-KSMG-AntiSpam-Rate: 0 X-KSMG-AntiSpam-Status: not_detected X-KSMG-AntiSpam-Method: none X-KSMG-AntiSpam-Auth: dkim=none X-KSMG-AntiSpam-Info: LuaCore: 15 0.3.15 adb41f89e2951eb37b279104a7abb8e79494a5e7, {Track_E25351}, {Tracking_from_domain_doesnt_match_to}, 127.0.0.199:7.1.2;100.64.160.123:7.1.2;d41d8cd98f00b204e9800998ecf8427e.com:7.1.1;salutedevices.com:7.1.1;smtp.sberdevices.ru:7.1.1,5.0.1, FromAlignment: s, ApMailHostAddress: 100.64.160.123 X-MS-Exchange-Organization-SCL: -1 X-KSMG-AntiSpam-Interceptor-Info: scan successful X-KSMG-AntiPhishing: Clean X-KSMG-LinksScanning: Clean X-KSMG-AntiVirus: Kaspersky Secure Mail Gateway, version 2.0.1.6960, bases: 2024/04/08 15:55:00 #24711186 X-KSMG-AntiVirus-Status: Clean, skipped On Mon, Apr 08, 2024 at 08:15:54PM +0200, Jerome Brunet wrote: > > On Mon 08 Apr 2024 at 19:49, Dmitry Rokosov wrote: > > > The 'link-name' property presents an optional DT feature that empowers > > users to customize the name associated with the DAI link and PCM stream. > > This functionality reflects the approach often employed in Qualcomm > > audio cards, providing enhanced flexibility in DAI naming conventions > > for improved system integration and userspace experience. > > > > It allows userspace program to easy determine PCM stream purpose, e.g.: > > ~ # cat /proc/asound/pcm > > 00-00: speaker (*) : : playback 1 > > 00-01: mics (*) : : capture 1 > > 00-02: loopback (*) : : capture 1 > > The example above is exactly what you should not do with link names, at > least with the amlogic audio system. > > Userspace pcm, otherwise known as DPCM frontend, are merely that: > frontends. What they do is entirely defined by the routing defined by > the userspace (amixer and friends) > > So naming the interface in DT (the FW describing the HW) after what the > the userspace SW could possibly set later on is wrong. > > Bottom line: I have mixed feeling about this change. It could allow all > sort of bad names to be set. > > The only way it could make sense HW wise is if the only allowed names > where (fr|to)ddr_[abcd], which could help maps the interface and the > kcontrol. > > Such restriction should be documented in the binding doc. > The link-name is an optional parameter. Yes, you are right, it can be routed in a way that it no longer functions as a speaker in most cases. However, if you plan to use your board's dt for common purposes, you should not change the common names for DAI links. But if you know that you have a static setup for speakers, microphones, loopback, or other references (you 100% know it, because you are HW developer of this board), why not help the user understand the PCM device assignment in the easiest way? Ultimately, it is the responsibility of the DT board developer to define specific DAIs and name them based on their own knowledge about HW and understanding of the board's usage purposes. > > > > The previous naming approach using auto-generated fe or be strings > > continues to be utilized as a fallback. > > > > Signed-off-by: Dmitry Rokosov > > --- > > sound/soc/meson/meson-card-utils.c | 12 ++++++++---- > > 1 file changed, 8 insertions(+), 4 deletions(-) > > > > diff --git a/sound/soc/meson/meson-card-utils.c b/sound/soc/meson/meson-card-utils.c > > index ed6c7e2f609c..7bae72905a9b 100644 > > --- a/sound/soc/meson/meson-card-utils.c > > +++ b/sound/soc/meson/meson-card-utils.c > > @@ -94,10 +94,14 @@ static int meson_card_set_link_name(struct snd_soc_card *card, > > struct device_node *node, > > const char *prefix) > > { > > - char *name = devm_kasprintf(card->dev, GFP_KERNEL, "%s.%s", > > - prefix, node->full_name); > > - if (!name) > > - return -ENOMEM; > > + const char *name; > > + > > + if (of_property_read_string(node, "link-name", &name)) { > > + name = devm_kasprintf(card->dev, GFP_KERNEL, "%s.%s", > > + prefix, node->full_name); > > + if (!name) > > + return -ENOMEM; > > + } > > > > link->name = name; > > link->stream_name = name; > > > -- > Jerome -- Thank you, Dmitry