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=-2.5 required=3.0 tests=DKIM_SIGNED,DKIM_VALID, MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS,USER_AGENT_SANE_1 autolearn=no 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 38652C2BA19 for ; Thu, 23 Apr 2020 11:05:41 +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 B61252076C for ; Thu, 23 Apr 2020 11:05:40 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (1024-bit key) header.d=alsa-project.org header.i=@alsa-project.org header.b="ae6n/9xm"; dkim=fail reason="signature verification failed" (1024-bit key) header.d=kernel.org header.i=@kernel.org header.b="rAjuMThv" DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org B61252076C Authentication-Results: mail.kernel.org; dmarc=fail (p=none dis=none) header.from=kernel.org 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 C4BC2168D; Thu, 23 Apr 2020 13:04:48 +0200 (CEST) DKIM-Filter: OpenDKIM Filter v2.11.0 alsa0.perex.cz C4BC2168D DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=alsa-project.org; s=default; t=1587639938; bh=tBjsKKzMxTUfGVyJhOJtQEHqkY2vpIFIBNWq9vVPHeg=; h=Date:From:To:Subject:References:In-Reply-To:Cc:List-Id: List-Unsubscribe:List-Archive:List-Post:List-Help:List-Subscribe: From; b=ae6n/9xm6MOoSS6Fi5i3wt/MdP88FHdIWlS9MUzvCmZlO5INqaBkmfEAh9EZ4i7re fbUqInv6QBtlhSZvadl3VuI9l64N3zlJyJutEGQmMrxR0xKoIBU21fBIg1KT55lcSP BOYF0a5WZSPDkWXn2nxO4yCdnIa/KOJLIPkTk+vI= Received: from alsa1.perex.cz (localhost.localdomain [127.0.0.1]) by alsa1.perex.cz (Postfix) with ESMTP id 4FFD0F8014A; Thu, 23 Apr 2020 13:04:48 +0200 (CEST) Received: by alsa1.perex.cz (Postfix, from userid 50401) id 18E68F801EC; Thu, 23 Apr 2020 13:04:45 +0200 (CEST) Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by alsa1.perex.cz (Postfix) with ESMTPS id 5F764F800FF for ; Thu, 23 Apr 2020 13:04:42 +0200 (CEST) DKIM-Filter: OpenDKIM Filter v2.11.0 alsa1.perex.cz 5F764F800FF Authentication-Results: alsa1.perex.cz; dkim=pass (1024-bit key) header.d=kernel.org header.i=@kernel.org header.b="rAjuMThv" Received: from localhost (fw-tnat.cambridge.arm.com [217.140.96.140]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPSA id 756582076C; Thu, 23 Apr 2020 11:04:39 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1587639880; bh=tBjsKKzMxTUfGVyJhOJtQEHqkY2vpIFIBNWq9vVPHeg=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=rAjuMThvn8W9rGGct0O77oav5ngHlQwudWONPJXoOY4J9SiZOOTpmaK1flPKg8ImJ omQ0KfErcp6cnkNdu0eoTSXHbkYzJuJRO3Mm9AiZrifDmdSpKK6/n4MlNkBilI3J7f VR7bKKXPSp6ruZiZEHsvlnPIVw6bDVyj7aOfMUXI= Date: Thu, 23 Apr 2020 12:04:37 +0100 From: Mark Brown To: Jaroslav Kysela Subject: Re: ASoC driver names Message-ID: <20200423110437.GF4808@sirena.org.uk> References: MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="yH1ZJFh+qWm+VodA" Content-Disposition: inline In-Reply-To: X-Cookie: This unit... must... survive. User-Agent: Mutt/1.10.1 (2018-07-13) Cc: Takashi Iwai , ALSA development , 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" --yH1ZJFh+qWm+VodA Content-Type: text/plain; charset=us-ascii Content-Disposition: inline On Wed, Apr 22, 2020 at 07:04:36PM +0200, Jaroslav Kysela wrote: > 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'). With ASoC systems there is no clear controller - you've got a bunch of different components, usually connected by separate buses, and it's not super obvious what if anything should be the singular name that gets picked for some grouping of devices. The whole point of the subsystem is to glue a bunch of independent devices together, we've generally picked that glue as the driver name. > 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 > My question is, can we change / add the more apropriate driver names > conditionally with a new kernel CONFIG option? Will you accept this change? Without knowing what you're actually proposing it's hard to know, and there is the risk of userspace breakage here when you change things people are relying on. > 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). This sounds like you either want some enumeration of the card components or perhaps you're looking for some for some indication of the reference design that an individual board is based off so you can have a generic configuration for that reference design and then override bits of it? --yH1ZJFh+qWm+VodA Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQEzBAABCgAdFiEEreZoqmdXGLWf4p/qJNaLcl1Uh9AFAl6hdkQACgkQJNaLcl1U h9Aiwgf8DQSaA532iTxpomKwEqr/ViWQmXoUprIRF/Mrp31QmVngzTWpQzy9raCT 2VBPYa92waXVujNsy3l34NhjpiN44VuAm+p8ynT52kau1B9bVe3sVnYwh2veei5A tz9s8d5FkyGCT8ShzdF0NR/WXGl9113Pq3LIh82exprBF3PmnpDEZMONvy8UtC2r gTxUQRnJiGKHEHdYcSZaigBaPGyL0AcwmvsikNOxvyH7veaKC+y6IoQWy7uOQBaV JRSbMvAzzjNm47DXm3bv9XWj1ocmntzoApySkOLAvVGumwAFBOAC3CEm9QGRgxyC W2iBGMhY2BBtPzV38JnqNlqHDpHilw== =1h6w -----END PGP SIGNATURE----- --yH1ZJFh+qWm+VodA--