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 81640C7EE2E for ; Tue, 13 Jun 2023 12:54:44 +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 C65E6A4D; Tue, 13 Jun 2023 14:53:51 +0200 (CEST) DKIM-Filter: OpenDKIM Filter v2.11.0 alsa0.perex.cz C65E6A4D DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=alsa-project.org; s=default; t=1686660881; bh=6s4D68dn5Rkh35hEvQgkAU45p/aGXdJjyZezPElB/Vo=; h=Date:From:To:Cc:Subject:In-Reply-To:References:List-Id: List-Archive:List-Help:List-Owner:List-Post:List-Subscribe: List-Unsubscribe:From; b=JThwgA2KiqMkvUG4J5fLBGSm5oOgt1Tg1pTuBSfaDfpmHc9VUCB7BQ02fGRBtbktF G2QLtawP5O3iE8OgYsKVp2mD5iZQT32yXWLSOGLMBjaPAnJ0uxoueGDADdQm97qyPJ 1b7OENyAQjdto2xosUepN7IV1VGqR+yllRZHJ1IA= Received: by alsa1.perex.cz (Postfix, from userid 50401) id 4D046F80246; Tue, 13 Jun 2023 14:53:26 +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 A8F23F80149; Tue, 13 Jun 2023 14:53:25 +0200 (CEST) Received: by alsa1.perex.cz (Postfix, from userid 50401) id C1952F80149; Tue, 13 Jun 2023 14:53:21 +0200 (CEST) Received: from smtp-out2.suse.de (smtp-out2.suse.de [IPv6:2001:67c:2178:6::1d]) (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 CC35DF800ED for ; Tue, 13 Jun 2023 14:53:18 +0200 (CEST) DKIM-Filter: OpenDKIM Filter v2.11.0 alsa1.perex.cz CC35DF800ED 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=oa92r/3i; dkim=pass header.d=suse.de header.i=@suse.de header.a=ed25519-sha256 header.s=susede2_ed25519 header.b=fIzGSIMp 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-out2.suse.de (Postfix) with ESMTPS id 3056C1FD9C; Tue, 13 Jun 2023 12:53:18 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=suse.de; s=susede2_rsa; t=1686660798; 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=U41sQoAS4isUpIbfFlFmd+7y1701JtIEBGroQzz+tJI=; b=oa92r/3iKSM06B+Kxxzjc9YV4DYvdl4Q/LQ2fozVI2oJT68sPkTMPwQ9kjztX2E+s3umWS JBWLLg0SvQCmVNckfDjJ0UqMLhsIY2o1n7W67xQJXrzWZi6V6JHChZRiclqVkEjy5h8H2a BeKoTiPegBajfZDpusgIKtgSZyQ3LWo= DKIM-Signature: v=1; a=ed25519-sha256; c=relaxed/relaxed; d=suse.de; s=susede2_ed25519; t=1686660798; 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=U41sQoAS4isUpIbfFlFmd+7y1701JtIEBGroQzz+tJI=; b=fIzGSIMpFBKvZIWI0rB0U3acF+3Y4eeKqK7bq2kUqdffQSUY3hKTmAJFy/gwdY5XsdttWh 7SjTW1LvJrg4DWAQ== 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 0E9D413483; Tue, 13 Jun 2023 12:53:18 +0000 (UTC) Received: from dovecot-director2.suse.de ([192.168.254.65]) by imap2.suse-dmz.suse.de with ESMTPSA id pRV9Ar5miGTXQQAAMHmgww (envelope-from ); Tue, 13 Jun 2023 12:53:18 +0000 Date: Tue, 13 Jun 2023 14:53:17 +0200 Message-ID: <87o7ljplqa.wl-tiwai@suse.de> From: Takashi Iwai To: happy.debugging@gmail.com Cc: alsa-devel@alsa-project.org Subject: Re: [PATCH v2 00/37] ALSA: Add MIDI 2.0 support In-Reply-To: <168666006765.22.17667904471972537472@mailman-web.alsa-project.org> References: <20230523075358.9672-1-tiwai@suse.de> <168666006765.22.17667904471972537472@mailman-web.alsa-project.org> 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: TU7H7Q2VDEUJNNIXVNBMRMZUGQ3HE62X X-Message-ID-Hash: TU7H7Q2VDEUJNNIXVNBMRMZUGQ3HE62X 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 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 Tue, 13 Jun 2023 14:41:07 +0200, happy.debugging@gmail.com wrote: > > Hello I have a few questions: > > 1. As default, USB-audio driver will take the alternate setting for MIDI 2.0 interface: Does this mean that the ALSA driver will default to Alt Function 1 if it exists ? Yes. > 2. What happens when using a kernel that does not support Alt Function 1 (MIDI 2.0) and device with a (much longer) MIDI 2.0 descriptor is attached ? It falls back to MIDI 1.0 interface. > 3. " However, user may let the driver falling back to the old MIDI 1.0 interface by a module option, too." > Can or how it this done via the ALSA API ? You can't. Only via a module option or kconfig. > If the switch is made, does an ALSA client require to re-enumerate all the ports ? > 4. Is there a way to force a specific device (port) to Legacy MIDI 1.0 ? If demanded, we can implement a device-specific quirk for that. > 5. Is there a way , via ALSA, to select UMP MIDI 1.0 protocol instead of MIDI 2.0 UMP protocol. Use the UMP 1.1 Streaming command to switch the protocol. > 6. To which protocol does the driver default ? UMP MIDI 1.0 or UMP MIDI 2.0 ? Whatever the device sets as default. > 7. Does the driver do anything related to Jitter Reduction ? How/is this supported via the ALSA API ?a JRTS is sent as normal UMP packet (also as sequencer events). No particular API is provided for JRTS, so far. > 8. Does the driver do anything related to Bandwidth restriction ? How/is this supported via the ALSA API ? Currently no restriction is. The bandwidth is provided via the API, but it's only for information. > 9. Are/will UMP streaming messages be supported ? (new feature in MIDI 2.0 specification), if yes, how ? It was already implemented in kernel UMP core. See the recent posts. > 10. Is function block information supported via ALSA, i.e added in the ALSA Port information ? Ditto. Takashi