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 4F12BC4332F for ; Mon, 26 Dec 2022 08:10:36 +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 7F26F6001; Mon, 26 Dec 2022 09:09:44 +0100 (CET) DKIM-Filter: OpenDKIM Filter v2.11.0 alsa0.perex.cz 7F26F6001 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=alsa-project.org; s=default; t=1672042234; bh=+hJ4I0IWNy6HSG+nQd/CJwLM1xohcZgmIA6n+xX9UeU=; h=Date:From:To:Subject:In-Reply-To:References:List-Id: List-Unsubscribe:List-Archive:List-Post:List-Help:List-Subscribe: Cc:From; b=IKm1MBp2c890HmpgGmzg7hRLXPKfSJHiMwLshgXcZIYfYJ9McLAhiLdkQfXC2IwXD MlSbX/RYPKXsiClXq3JwGfYWRjan5BBwYpHxzWfiaN+5Q15EUxZzLmv3JwDGPCJ5A0 VbzU+N7s8PTC16WvSOwnAyrnBYImCUaC9olbxJPg= Received: from alsa1.perex.cz (localhost.localdomain [127.0.0.1]) by alsa1.perex.cz (Postfix) with ESMTP id E23B4F802A0; Mon, 26 Dec 2022 09:09:43 +0100 (CET) Received: by alsa1.perex.cz (Postfix, from userid 50401) id 8EE4CF80310; Mon, 26 Dec 2022 09:09:36 +0100 (CET) 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 19801F80134 for ; Mon, 26 Dec 2022 09:09:29 +0100 (CET) DKIM-Filter: OpenDKIM Filter v2.11.0 alsa1.perex.cz 19801F80134 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=TubNC310; dkim=pass header.d=suse.de header.i=@suse.de header.a=ed25519-sha256 header.s=susede2_ed25519 header.b=ZSpxnfzZ 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 0979F33FCD; Mon, 26 Dec 2022 08:09:29 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=suse.de; s=susede2_rsa; t=1672042169; 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=P8ft7F/KT+lvr+2pYmbIZYoFyftWJwwWXEH04QR9uy8=; b=TubNC310Gz/8DEdxSO6HQfOEPGNEMFZMTI0WRoenCcFnDm1FIIs/Ix7T1ZFNZPznVVF710 w1/itmVZu6Cd+2p0nDk7Y1ST/tkP6gL0SN9WaLlEnR4G12100KVJAanma0xaPK8D2zsdBF KZaieoEutR5wzHHGEHLDNUHsF2ddUOs= DKIM-Signature: v=1; a=ed25519-sha256; c=relaxed/relaxed; d=suse.de; s=susede2_ed25519; t=1672042169; 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=P8ft7F/KT+lvr+2pYmbIZYoFyftWJwwWXEH04QR9uy8=; b=ZSpxnfzZ1CFuemMmRT2eirreCCGaxTjBiXeCrSfCZRETH3YKvqWcn5TnhYoDZFKXDr+Aed Ti9FUW1CbbcFnfBA== 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 D2D9813456; Mon, 26 Dec 2022 08:09:28 +0000 (UTC) Received: from dovecot-director2.suse.de ([192.168.254.65]) by imap2.suse-dmz.suse.de with ESMTPSA id JKqKMrhWqWMvcwAAMHmgww (envelope-from ); Mon, 26 Dec 2022 08:09:28 +0000 Date: Mon, 26 Dec 2022 09:09:28 +0100 Message-ID: <878riuy4av.wl-tiwai@suse.de> From: Takashi Iwai To: Artem Egorkine Subject: Re: [PATCH 1/2] ALSA: line6: correct midi status byte when receiving data from podxt In-Reply-To: <20221225105728.1153989-1-arteme@gmail.com> References: <20221225105728.1153989-1-arteme@gmail.com> 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 X-BeenThere: alsa-devel@alsa-project.org X-Mailman-Version: 2.1.29 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: , Cc: alsa-devel@alsa-project.org, tiwai@suse.com Errors-To: alsa-devel-bounces@alsa-project.org Sender: "Alsa-devel" On Sun, 25 Dec 2022 11:57:27 +0100, Artem Egorkine wrote: > > A PODxt device sends 0xb2, 0xc2 or 0xf2 as a status byte for MIDI > messages over USB that should otherwise have a 0xb0, 0xc0 or 0xf0 > status byte. This is usually corrected by the driver on other OSes. > > This fixes MIDI sysex messages sent by PODxt. > > Signed-off-by: Artem Egorkine Applied both patches now. Thanks! Takashi