Received: by 2002:a05:6a10:5bc5:0:0:0:0 with SMTP id os5csp4480006pxb; Thu, 14 Oct 2021 06:06:47 -0700 (PDT) X-Google-Smtp-Source: ABdhPJx5WdvM9D1wwg9YnITfo3lYtvRYr0e4r1P23s0+deEwX+vdrY6qNP1QFWBy3TwTCTEDXhbv X-Received: by 2002:a17:906:b208:: with SMTP id p8mr3750954ejz.477.1634216806816; Thu, 14 Oct 2021 06:06:46 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1634216806; cv=none; d=google.com; s=arc-20160816; b=H7wY9+WvniryRb/c8Kfh5YQF8BBh4I2FQ/zzUuUJniW7otNffgr9IjDp61MYRR/9mM 2KijaI9booJzqKmfAWFlihTiygA4i9657/179su6hs9lXdyDOH2TzpC3msLNog3PDekL 4lLUapPdsWiXyfYtapteEIGaPW33l/0G32TKKDO+p1AxS1Juca56bMUaTfgCjxsF0KsZ U+xXCd2ziEtW6jyPITM1Efx+dZRfmIlSHOFTLfKlw8kp4PA61b0wGmG0ONDHPzpMFwPE f8iBA6ZKIRkWn+YP+oXwUYcCGxFN3atkYkwtSbIViFSQgy0FpYFUkaY+Gh7XTrGuSzEE o+NA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:mime-version:user-agent:references:in-reply-to :subject:cc:to:from:message-id:date:dkim-signature:dkim-signature; bh=tL+SOKDX3hkNa5BvmV5TRBLsoF/YWzQI6GrS/Q70rrw=; b=OjJZtyypVTtzlox9UG7yQIlbwm6a1y1JpEzUhnLp8y00fKN0uVD2ytzkp0BqePLWn8 scCeaxVJ8s0sDLvtIRgX43qPvSTSHVcC9pH//YebhgN302WoARW2OBGD1vSQIgg+buzF nYAMtE4TeUtjYOrbpKMc2eNzmhTmHjUGX687cFuoLyUrd8eQn2rXWb0yRlbR3h3G1A8G hFHmOk/eCFa/QqkSumDmp0vx1+9Jrz57JqJmb3zFeEN9N1ee3yhoo9eB9gL5r2GdSpek 3bsFrGKvBcmHq5B5TlZkWOcg9d9ei8Okp1BQe/cR37eWRBqrJQxZ+OL/4MH1xolNXHSS nwww== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@suse.de header.s=susede2_rsa header.b=MDpVaXdS; dkim=neutral (no key) header.i=@suse.de header.s=susede2_ed25519 header.b=N7z33a5R; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=suse.de Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id bs11si3392528ejb.438.2021.10.14.06.06.22; Thu, 14 Oct 2021 06:06:46 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; dkim=pass header.i=@suse.de header.s=susede2_rsa header.b=MDpVaXdS; dkim=neutral (no key) header.i=@suse.de header.s=susede2_ed25519 header.b=N7z33a5R; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=suse.de Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S231149AbhJNLki (ORCPT + 99 others); Thu, 14 Oct 2021 07:40:38 -0400 Received: from smtp-out1.suse.de ([195.135.220.28]:55676 "EHLO smtp-out1.suse.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S230229AbhJNLkh (ORCPT ); Thu, 14 Oct 2021 07:40:37 -0400 Received: from relay2.suse.de (relay2.suse.de [149.44.160.134]) by smtp-out1.suse.de (Postfix) with ESMTP id 69E6921A74; Thu, 14 Oct 2021 11:38:32 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=suse.de; s=susede2_rsa; t=1634211512; 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=tL+SOKDX3hkNa5BvmV5TRBLsoF/YWzQI6GrS/Q70rrw=; b=MDpVaXdSQFeihigd0+QU19BVWmxHJKcEhciHmxRs/NSwHNxj3kQJUaVY9vVZXCtw+O0FHL qbDHv2FxjnogajxPeaZj3bKRbuIIkGkgCrSX2hGhQvRzLB6L13aodNujGSV5Vj0IIlp0bs +0i6lr3xSYeq9ndRlpd6tsZ9wH7I5vg= DKIM-Signature: v=1; a=ed25519-sha256; c=relaxed/relaxed; d=suse.de; s=susede2_ed25519; t=1634211512; 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=tL+SOKDX3hkNa5BvmV5TRBLsoF/YWzQI6GrS/Q70rrw=; b=N7z33a5RoXkZAV7wfPa5HmybVVpm+w07v42Laf3Po300BCX5TUn1+BF6CNe8I+9lca8H2l gF4AewzZ5qavoGAQ== Received: from alsa1.suse.de (alsa1.suse.de [10.160.4.42]) by relay2.suse.de (Postfix) with ESMTP id 3BEFDA3B84; Thu, 14 Oct 2021 11:38:32 +0000 (UTC) Date: Thu, 14 Oct 2021 13:38:32 +0200 Message-ID: From: Takashi Iwai To: Greg Kroah-Hartman Cc: Jaroslav Kysela , Takashi Iwai , alsa-devel@alsa-project.org, linux-usb@vger.kernel.org, linux-kernel@vger.kernel.org Subject: Re: [PATCH] ALSA: usb-audio: allow -EPIPE errors for some v2 messages In-Reply-To: References: User-Agent: Wanderlust/2.15.9 (Almost Unreal) SEMI/1.14.6 (Maruoka) FLIM/1.14.9 (=?UTF-8?B?R29qxY0=?=) APEL/10.8 Emacs/25.3 (x86_64-suse-linux-gnu) MULE/6.0 (HANACHIRUSATO) MIME-Version: 1.0 (generated by SEMI 1.14.6 - "Maruoka") Content-Type: text/plain; charset=US-ASCII Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thu, 14 Oct 2021 12:56:26 +0200, Greg Kroah-Hartman wrote: > > On Tue, Oct 12, 2021 at 03:24:04PM +0200, Takashi Iwai wrote: > > On Tue, 12 Oct 2021 14:41:44 +0200, > > Greg Kroah-Hartman wrote: > > > > > > On Tue, Oct 12, 2021 at 09:35:16AM +0200, Takashi Iwai wrote: > > > > On Mon, 11 Oct 2021 19:23:05 +0200, > > > > Greg Kroah-Hartman wrote: > > > > > > > > > > On Mon, Oct 11, 2021 at 06:07:01PM +0200, Takashi Iwai wrote: > > > > > > Could you also post the contents of /proc/asound/card*/usbmixer (only > > > > > > for the corresponding device), too? > > > > > > > > > > Sure, here it is: > > > > > > > > > > USB Mixer: usb_id=0x30be0101, ctrlif=0, ctlerr=0 > > > > > Card: Schiit Audio Schiit Hel at usb-0000:47:00.1-2.2, high speed > > > > > Unit: 5 > > > > > Control: name="Mic - Input Jack", index=0 > > > > > Info: id=5, control=2, cmask=0x0, channels=1, type="BOOLEAN" > > > > > Volume: min=0, max=1, dBmin=0, dBmax=0 > > > > > Unit: 7 > > > > > Control: name="Speaker - Output Jack", index=0 > > > > > Info: id=7, control=2, cmask=0x0, channels=1, type="BOOLEAN" > > > > > Volume: min=0, max=1, dBmin=0, dBmax=0 > > > > > Unit: 13 > > > > > Control: name="PCM Playback Switch", index=0 > > > > > Info: id=13, control=1, cmask=0x0, channels=1, type="INV_BOOLEAN" > > > > > Volume: min=0, max=1, dBmin=0, dBmax=0 > > > > > Unit: 17 > > > > > Control: name="Mic Capture Switch", index=0 > > > > > Info: id=17, control=1, cmask=0x0, channels=1, type="INV_BOOLEAN" > > > > > Volume: min=0, max=1, dBmin=0, dBmax=0 > > > > > Unit: 18 > > > > > Control: name="Clock Source 18 Validity", index=0 > > > > > Info: id=18, control=2, cmask=0x0, channels=1, type="BOOLEAN" > > > > > Volume: min=0, max=1, dBmin=0, dBmax=0 > > > > > Unit: 22 > > > > > Control: name="Clock Source 22 Validity", index=0 > > > > > Info: id=22, control=2, cmask=0x0, channels=1, type="BOOLEAN" > > > > > Volume: min=0, max=1, dBmin=0, dBmax=0 > > > > > > > > Hm, I expected more exotic control that failed, but it was Mic Capture > > > > Switch, which should be treated normally. > > > > > > > > Could you try the patch below? This will still show other warning > > > > messages, but it'll forcibly initialize the mixer elements at probe > > > > time, and the rest should work. > > > > > > > > Once after it's confirmed to work, we may shut up the device warnings > > > > with a quirk. > > > > > > Only one warning message shows up, here's the dmesg with this patch > > > applied: > > > > > > > > > [Oct12 14:39] usb 7-2.2: new high-speed USB device number 10 using xhci_hcd > > > [ +0.123157] usb 7-2.2: New USB device found, idVendor=30be, idProduct=0101, bcdDevice= 1.02 > > > [ +0.000009] usb 7-2.2: New USB device strings: Mfr=1, Product=2, SerialNumber=0 > > > [ +0.000003] usb 7-2.2: Product: Schiit Hel > > > [ +0.000002] usb 7-2.2: Manufacturer: Schiit Audio > > > [ +0.339785] usb 7-2.2: 17:0: failed to get current value for ch 0 (-32) > > > [ +0.020373] input: Schiit Audio Schiit Hel as /devices/pci0000:40/0000:40:01.1/0000:41:00.0/0000:42:08.0/0000:47:00.1/usb7/7-2/7-2.2/7-2.2:1.3/0003:30BE:0101.000B/input/input24 > > > [ +0.056868] hid-generic 0003:30BE:0101.000B: input,hidraw6: USB HID v1.00 Device [Schiit Audio Schiit Hel] on usb-0000:47:00.1-2.2/input3 > > > > OK, then the problem is only about this unit and about the master > > channel. > > > > > I don't see a "mic capture switch" on this device, but maybe it triggers > > > when I plug a mic into the microphone port, which is currently empty? > > > > This should be persistent and visible; try to run "amixer -c1" (or the > > different card index for the device). > > > > So far, so good. The only remaining piece is how this -EPIPE error > > comes up. Is this a protocol stall error or such? Would it be > > avoided by adding the delay like done for some devices? > > > > With the 5.15-rc kernel, you can pass quirk_flags option to > > snd-usb-audio module for applying known quirks. > > e.g. quirk_flags=0x100 will set the 1msec delay at each control > > message. Please check whether it makes any difference. > > The option is an integer array for multiple devices, so if you have > > multiple USB-audio devices, put at the appropriate position in the > > array (e.g. quirk_flags=,,0x100 for the 3rd slot). > > This quirk did not work. Well, it caused the error to show up after a > delay, but the error is still there. > > > The quirk bit 0x4000 will shut up the control errors. If the above > > doesn't fix the warning and the device is working more or less, set > > this quirk to shut up the warning. It can be set statically in the > > table at the end in sound/usb/quirks.c. > > This quirk did work in that the error messages are still in the kernel > log, but the device seems to work properly now. > > Let me send a patch that adds this device to the quirk table. OK, thanks! The remaining error message should be suppressed with the patch in my previous mail. Or maybe we can add a patch to downgrade the error message to dev_dbg() at first for 5.15, then another one (initializing all controls at first) to 5.16. Takashi