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 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 smtp.lore.kernel.org (Postfix) with ESMTPS id A1F14CA101F for ; Mon, 8 Sep 2025 02:01:23 +0000 (UTC) Received: from alsa1.perex.cz (alsa1.perex.cz [45.14.194.44]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (No client certificate requested) by alsa0.perex.cz (Postfix) with ESMTPS id 594A7601F9; Mon, 8 Sep 2025 04:01:06 +0200 (CEST) DKIM-Filter: OpenDKIM Filter v2.11.0 alsa0.perex.cz 594A7601F9 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=alsa-project.org; s=default; t=1757296876; bh=dHtCNQggg/KHKzmzNHz0lDdYkQVmjDjJqtb+gJIffiI=; h=From:To:In-Reply-To:References:Subject:Date:List-Id:List-Archive: List-Help:List-Owner:List-Post:List-Subscribe:List-Unsubscribe: From; b=GZqRMiDehNgg/Zb0ACrrtjgr+xWo6gWZiPJIpIwujoAVsMyBf1emvO4obZVzBqlTH Mu31G66OMEHjet/5mKEn51/ND7ARbzhSJcKBYhvEsH6uv34LQkqLb0PU6f/EWTtud6 LtO4nJIzkwRxVx4I+5NAYR/yiRZKpHTMlXFtpC7w= Received: by alsa1.perex.cz (Postfix, from userid 50401) id 84A23F805C9; Mon, 8 Sep 2025 04:00:44 +0200 (CEST) Received: from mailman-core.alsa-project.org (mailman-core.alsa-project.org [10.254.200.10]) by alsa1.perex.cz (Postfix) with ESMTP id EB7B6F805C2; Mon, 8 Sep 2025 04:00:43 +0200 (CEST) Received: by alsa1.perex.cz (Postfix, from userid 50401) id 6FB31F80185; Mon, 8 Sep 2025 04:00:29 +0200 (CEST) Received: from webhooks-bot.alsa-project.org (vmi2259423.contaboserver.net [45.14.194.44]) by alsa1.perex.cz (Postfix) with ESMTP id 2B747F8016E for ; Mon, 8 Sep 2025 04:00:24 +0200 (CEST) DKIM-Filter: OpenDKIM Filter v2.11.0 alsa1.perex.cz 2B747F8016E MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit From: GitHub issues - opened To: alsa-devel@alsa-project.org Message-Id: <18632c26b8b2b200-webhooks-bot@alsa-project.org> In-Reply-To: <18632c26b7126d00-webhooks-bot@alsa-project.org> References: <18632c26b7126d00-webhooks-bot@alsa-project.org> Subject: Feature Request: conf.d for USB-Audio Date: Mon, 8 Sep 2025 04:00:29 +0200 (CEST) Message-ID-Hash: JXTT6NDVOLEYNWHL77DDQORJLURXBZ3R X-Message-ID-Hash: JXTT6NDVOLEYNWHL77DDQORJLURXBZ3R X-MailFrom: github@alsa-project.org X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-alsa-devel.alsa-project.org-0; header-match-alsa-devel.alsa-project.org-1; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header X-Mailman-Version: 3.3.9 Precedence: list List-Id: "Alsa-devel mailing list for ALSA developers - http://www.alsa-project.org" Archived-At: List-Archive: List-Help: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: alsa-project/alsa-ucm-conf issue #609 was opened from FrostyCoolSlug: The release cadence of `alsa-ucm-conf` tends to be a little on the slow side (generally around 6 months between releases), but the problem I'm hitting currently is the requirement for users to manually edit `USB-Audio.conf` in order to get support for their devices (and depending on distribution, support could be delayed upwards of two years). I think a method where a package could be created to drop files into a conf.d style directory would allow for a users device to be configured, without the need for manually editing `USB-Audio.conf` to add support. Issue URL : https://github.com/alsa-project/alsa-ucm-conf/issues/609 Repository URL: https://github.com/alsa-project/alsa-ucm-conf