Received: by 2002:ad5:474a:0:0:0:0:0 with SMTP id i10csp916137imu; Fri, 4 Jan 2019 09:25:49 -0800 (PST) X-Google-Smtp-Source: ALg8bN5/oWoW692kjGeN6mOsATLmgXWILuSjrnESDgquuVFyTMjPFjgCzvV897F0jbF7nLKroNaf X-Received: by 2002:a17:902:9a98:: with SMTP id w24mr51888387plp.213.1546622749220; Fri, 04 Jan 2019 09:25:49 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1546622749; cv=none; d=google.com; s=arc-20160816; b=ueIOlbIN970j2H95PLxdKpWlGkRzordMtpO5h7SnE8kcVhN7XXo3EzH05/XHXc4Yik twMAIU4w2qx+Y+k/Zv246DpyBo3OH54Z9DC7r1QgQkUFJSzSDRXx3Ny6a1bHZI2KOwGr osVwnyME64/r3qI4AtqXshgG33jpmaXOWNi2+fr1bLNjxlMX6pvqCDFpagLaVextH/3X p9ORU4ChptB8GV+lcXw+Iu3UXRQj+IcjrVBUz5BzNZvn4/9Mti4V057PE3tnNKuhBmak gGyNY+2HNCkB/YsWDPUxXm669Rq/7YIYNGHk5LOynvRE3PHI8nPVFgW4wZ+Y1AM3xiYT Wynw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-language :content-transfer-encoding:in-reply-to:mime-version:user-agent:date :message-id:from:references:cc:to:subject; bh=Fnr0RF2eWXiHhb/yozU3kTzebRawuLVKp6xgyeSQJiE=; b=ukbdSXBOGqZi7E5VA1IqLtPD7+h+Y1yr/1Vg+6U7Rx1Tx27ZB7M+zJcnrSmO3Sfi4y EM60X5+WD4ZWd8Y6PRf6/7zvCl1Qlfwy/BzcmliS0ObVX6WWN5KPJptNJnn9PfwHKn1n uLZWPhnpUKRICNsFpUblOLKnBg2vFcK16EFkk1Vu5lFFCoGP3A5UOY9yEXqqSfQoj6SN aCBfqHhwz6xmecHpydMdfB5oJYaxEx1iK0UlAdpGXO4gVaqjd6zTCMzt0/l0QOwErMgV fGd9PgY3oTaNJlXl/gXRoKyZPLG3GSCyrMdrgCPnBVSvWmgGNLAJNwXT/3wS9xbFMt5B PW/Q== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=intel.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id e13si2202447pfi.271.2019.01.04.09.25.33; Fri, 04 Jan 2019 09:25:49 -0800 (PST) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=intel.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1727465AbfADPXn (ORCPT + 99 others); Fri, 4 Jan 2019 10:23:43 -0500 Received: from mga05.intel.com ([192.55.52.43]:39055 "EHLO mga05.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1727202AbfADPXk (ORCPT ); Fri, 4 Jan 2019 10:23:40 -0500 X-Amp-Result: SKIPPED(no attachment in message) X-Amp-File-Uploaded: False Received: from orsmga008.jf.intel.com ([10.7.209.65]) by fmsmga105.fm.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 04 Jan 2019 07:23:40 -0800 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.56,439,1539673200"; d="scan'208";a="106972027" Received: from lculbert-x1y7.amr.corp.intel.com (HELO [10.252.194.2]) ([10.252.194.2]) by orsmga008.jf.intel.com with ESMTP; 04 Jan 2019 07:23:39 -0800 Subject: Re: [alsa-devel] ALSA:usb audio Higher sample rates on usb audio no longer working. To: Takashi Iwai , Con Kolivas Cc: saranya.gopal@intel.com, alsa-devel@alsa-project.org, linux-usb@vger.kernel.org, linux-kernel , felipe.balbi@linux.intel.com References: From: Pierre-Louis Bossart Message-ID: <5c7b2c6b-5dcc-7170-f6e1-bf6021bbb72a@linux.intel.com> Date: Fri, 4 Jan 2019 09:23:38 -0600 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.2.1 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit Content-Language: en-US Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org > [ Adding linux-usb ML to Cc, as it's a core USB issue ] > > So the device seems incorrectly advertising as if it were supporting > UAC3 -- assuming the device is still not UAC3-capable. > > IOW, it's a buggy firmware. We need some blacklisting, or revert the > commit for now, unless any real UAC3 device comes up to the market. IIRC an UAC3-capable device is required to expose a backwards-compatible configuration (either UAC1 or UAC2). Maybe an additional test can be done to harden the detection so that UAC3 is only chosen if indeed a second audio configuration is present as well. I also vaguely recall there was talk about adding information in the BOS descriptor, but I don't know if this was ever published. -Pierre