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 059B4C77B72 for ; Thu, 20 Apr 2023 12:55:46 +0000 (UTC) Received: from alsa1.perex.cz (alsa1.perex.cz [207.180.221.201]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by alsa0.perex.cz (Postfix) with ESMTPS id 9164711C; Thu, 20 Apr 2023 14:54:54 +0200 (CEST) DKIM-Filter: OpenDKIM Filter v2.11.0 alsa0.perex.cz 9164711C DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=alsa-project.org; s=default; t=1681995344; bh=fHa1tNpr67Bn7zA+BMVPgFZVZpYZCKEYkm+qEGf8yX0=; h=Date:From:To:Subject:In-Reply-To:References:CC:List-Id: List-Archive:List-Help:List-Owner:List-Post:List-Subscribe: List-Unsubscribe:From; b=Wlka/9svyrOVtMKsyM9RJ1XzOyIFcM2dkVzOoOFxkelE8hx4bLvhGI1HjdzW1j98u wkB/8uuvp+Kratrqv/yHRjpOhLwXC+2vTAYB5Zg+Ug1PSvDRjF8Yf/sytmxv6zZRXu 8yGxCwPsPyOgqBsdyh3vi7Ky1uwG5G9LRZVxV0jI= Received: from mailman-core.alsa-project.org (mailman-core.alsa-project.org [10.254.200.10]) by alsa1.perex.cz (Postfix) with ESMTP id 0EFB8F80155; Thu, 20 Apr 2023 14:54:30 +0200 (CEST) Received: by alsa1.perex.cz (Postfix, from userid 50401) id 346B8F80155; Thu, 20 Apr 2023 14:54:26 +0200 (CEST) Received: from smtp-out1.suse.de (smtp-out1.suse.de [195.135.220.28]) (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 alsa1.perex.cz (Postfix) with ESMTPS id 1C129F800F8 for ; Thu, 20 Apr 2023 14:54:19 +0200 (CEST) DKIM-Filter: OpenDKIM Filter v2.11.0 alsa1.perex.cz 1C129F800F8 Authentication-Results: alsa1.perex.cz; dkim=pass (1024-bit key, unprotected) header.d=suse.de header.i=@suse.de header.a=rsa-sha256 header.s=susede2_rsa header.b=qUJR1Gpw; dkim=pass header.d=suse.de header.i=@suse.de header.a=ed25519-sha256 header.s=susede2_ed25519 header.b=f0caSjFs Received: from imap2.suse-dmz.suse.de (imap2.suse-dmz.suse.de [192.168.254.74]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (P-521) server-digest SHA512) (No client certificate requested) by smtp-out1.suse.de (Postfix) with ESMTPS id A8470219BC; Thu, 20 Apr 2023 12:54:19 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=suse.de; s=susede2_rsa; t=1681995259; h=from:from:reply-to:date:date:message-id:message-id:to:to:cc:cc: mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=c/nYEKMkip4wPKXa+7ERNGgpmrR3nTG514VMjPOwfq0=; b=qUJR1Gpwi0cpA7XhpNMKfEzovae9dBY5BKVASy8a58FYQgiU+ZymlT5SI+mqGUYkC8CA/z NAsDeSR6aoCIBsldmBO0AoNPq/picYvqQguchMeF+x75Sy/HmhrvUR5KPz9PAzfLsv2sOC CX9BIAmFlVhtH26ZhIKABTIGh9dFwQg= DKIM-Signature: v=1; a=ed25519-sha256; c=relaxed/relaxed; d=suse.de; s=susede2_ed25519; t=1681995259; h=from:from:reply-to:date:date:message-id:message-id:to:to:cc:cc: mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=c/nYEKMkip4wPKXa+7ERNGgpmrR3nTG514VMjPOwfq0=; b=f0caSjFs8X8/Lw1HOwc54MYajduIgHRWLo0HX80APSnTZUS9ygVcgqJ8UCm5O6Xf9OlWfW 5ETlamhJBrV5ImAw== Received: from imap2.suse-dmz.suse.de (imap2.suse-dmz.suse.de [192.168.254.74]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (P-521) server-digest SHA512) (No client certificate requested) by imap2.suse-dmz.suse.de (Postfix) with ESMTPS id 896CB1333C; Thu, 20 Apr 2023 12:54:19 +0000 (UTC) Received: from dovecot-director2.suse.de ([192.168.254.65]) by imap2.suse-dmz.suse.de with ESMTPSA id Il+lIPs1QWR5CQAAMHmgww (envelope-from ); Thu, 20 Apr 2023 12:54:19 +0000 Date: Thu, 20 Apr 2023 14:54:19 +0200 Message-ID: <87wn26u32c.wl-tiwai@suse.de> From: Takashi Iwai To: Oswald Buddenhagen Subject: Re: [RFC PATCH] docs: sound: kernel-api: writing-an-alsa-driver.rst: add FIXMEs In-Reply-To: References: <20230405201220.2197878-1-oswald.buddenhagen@gmx.de> <87sfddv7e4.wl-tiwai@suse.de> User-Agent: Wanderlust/2.15.9 (Almost Unreal) Emacs/27.2 Mule/6.0 MIME-Version: 1.0 (generated by SEMI-EPG 1.14.7 - "Harue") Content-Type: text/plain; charset=US-ASCII Message-ID-Hash: 3WCTII72MTJAMW3MHJMK2TLDRODR7VYQ X-Message-ID-Hash: 3WCTII72MTJAMW3MHJMK2TLDRODR7VYQ X-MailFrom: tiwai@suse.de 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 CC: alsa-devel@alsa-project.org X-Mailman-Version: 3.3.8 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: On Thu, 20 Apr 2023 14:47:11 +0200, Oswald Buddenhagen wrote: > > On Thu, Apr 06, 2023 at 08:42:27AM +0200, Takashi Iwai wrote: > > On Wed, 05 Apr 2023 22:12:20 +0200, Oswald Buddenhagen wrote: > >> The ``name`` is the name identifier string. Since ALSA 0.9.x, the > >> control name is very important, because its role is classified from > >> its name. There are pre-defined standard control names. The details > >> are described in the `Control Names`_ subsection. > >> +// This is a questionable design, IMO. Why user-space heuristics when > >> +// the driver could set the roles/capabilities? This would avoid > >> +// problems like the Tone Control sliders (unlike the switch?!) being > >> +// misclassified as applying also to capture. > > > > Why this has to be discussed here and now...? > > > why not? Because it is the already defined rule, and you're complaining the documentation. You are free to start a new discussion, but not it shouldn't be along with the documentation patch at all. > > It's the thing that was *defined* over two decades ago. > > > that may be so, but this doesn't explain anything. > it's a somewhat surprising choice, and it does in fact sometimes cause > problems. so at least it should be thoroughly explained. Again, you're barking at a wrong place. The whole control name ruling is explained in another document; there is another document covering control name rules. Takashi