Received: by 10.213.65.68 with SMTP id h4csp46128imn; Mon, 19 Mar 2018 19:03:58 -0700 (PDT) X-Google-Smtp-Source: AG47ELtnNnrhTDxMpZtIxEjA6ei8PswzbHnXKXiucYQLVeQtQ1CmtIZwXxtnxhSJxatYlbwsNkmW X-Received: by 2002:a17:902:850c:: with SMTP id bj12-v6mr14784246plb.110.1521511438916; Mon, 19 Mar 2018 19:03:58 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1521511438; cv=none; d=google.com; s=arc-20160816; b=gfcjfZjxxQQNIdtcdtBFCZA4XEsFOiuS1xkBUOaWi27BpobjUnkFWOUk1vph3am46Q T/5Np8eHhuG53fKyqr13xu5g4ChBeqt4IhHJaosRrBBJzq/gqXQcLfcpc5cTyYl8YKGb e4YKkJbTGUHaRFJMXDmSLJ89vRLGzVemYHDmo6mYtjka0p0sgEv9dDZ+ssZqBNDHGoZ2 QvNCps5B6KVTpeC192jjc/MA9ZsCVWkWf80nmk/wxE2dV1AipJC2Sy5SglZHMhBsscju ovpwdF1EXuESrfS4ITzBjAjSANvP28sthDCDKFdbIvOahtKEYqgHLIhyU2PUwSvN62G0 bjww== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:cc:to:subject:message-id:date:from :references:in-reply-to:mime-version:dkim-signature :arc-authentication-results; bh=EUVL9Bxc19Zmdf1zgW6RhsP68hL1N48Cb3dQSL+9eO0=; b=YSiG2RPNUFyd0WlwXNwfwec9bTk30XFR/S6ZoLkQFoxbRr0cbWByrmToB/07Fu9vYq rEhzZXJCRoNVRLpC6gQ0rHbemBkbUOzWk5ifpmrTp/Gd3v4t8Fx8jdJ0pJCHWljfzjrk HGCqyAisQRtaVmvdE9n8SNJAqImGyaPn+i7ruX5Tq2DQp1onKadlvnrtiHJfhv71XkW+ RvUN89e1fOxGLuWUeliDUMwf0K1YGW3WY9on++E65J7z1i95lI00TJeLd55zfsLAvFJy +3SEjSNLRUSypoUYDd6Jkyq2S1tBx2qzCQmk8jZztJFzGQm+pzCtH5QMh8vzmB7fatkc j8aA== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@gmail.com header.s=20161025 header.b=ONk3sTLD; 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=pass (p=NONE sp=QUARANTINE dis=NONE) header.from=gmail.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id m39-v6si554603plg.447.2018.03.19.19.03.44; Mon, 19 Mar 2018 19:03:58 -0700 (PDT) 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; dkim=pass header.i=@gmail.com header.s=20161025 header.b=ONk3sTLD; 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=pass (p=NONE sp=QUARANTINE dis=NONE) header.from=gmail.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S933052AbeCSXcU (ORCPT + 99 others); Mon, 19 Mar 2018 19:32:20 -0400 Received: from mail-oi0-f68.google.com ([209.85.218.68]:38842 "EHLO mail-oi0-f68.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S932534AbeCSXcR (ORCPT ); Mon, 19 Mar 2018 19:32:17 -0400 Received: by mail-oi0-f68.google.com with SMTP id c3so2765916oib.5 for ; Mon, 19 Mar 2018 16:32:17 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=EUVL9Bxc19Zmdf1zgW6RhsP68hL1N48Cb3dQSL+9eO0=; b=ONk3sTLDBD0DZKdPYu3VfsXiBVddJ5s5eFLigKiZseup4JJ2IXw5YMyrOOgmaLrH0E PB2QfjsZtPshaFe1lUOwTg+9h0UW7cSzQg5b5tGO1vtdH2SvWca7/3GWqmF7SVsTG4Ew dfSTB8KYuJUecUCmXoC7IwQh5glJAdvYH4gZN6/YuFdpx9W119Nrq522I29MmuP27fNz b3tVi6ec/eQrkkh+IOp8Xr3Xy0N6wwYEf1kfVHCMVipsnxgppWRsLD9YWTAuHmYr0K66 tmEA8+lUzi+48x6MthagF6lxrWuG00+XSlv6ei6ZhN7YAt0PVA+5OjC+z4YzVnHA8GdS 8Y0Q== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=EUVL9Bxc19Zmdf1zgW6RhsP68hL1N48Cb3dQSL+9eO0=; b=UiiKupOqDiS9U5lXxYm+rBa2kTR2EyHsuv+NDJDWRW7ExKpn1nRoeZcua0J2lVs7gU bhRhXUfJ2UQW0QGa3XqYUdSyxcrQQ25UxNxzZOHLiGbu+uqG16dq8oKhnjASPHMqxWXH nZ0+kwHF4dpN4XImAcoEDF+Lf3u1uxZytGSsCdtZLwEY1qC/QDLGKV6yyXuPu7YeDkBn TW+5sILBs4Az0B0wg+RvfRxAeU6rcKFL085Dnm/elMJDLGe4ZI8UDXrCc6YQgOHABL2w x7AE7gPt6hDbfrNOjeI7lWbDG5/7dukqQwtGCqO5hQQIls4P44JHkweYZjYRSbpTrNGV sd0w== X-Gm-Message-State: AElRT7EqT4nV0fKRyM42osXF939SwJo5zlyHJ62LYU6bNj45XAXMX/Gu KlD3G58QNgWgGDKc8/LWkF/ww9Tmy8DM2oWbH9U= X-Received: by 10.202.106.4 with SMTP id f4mr2750485oic.159.1521502336491; Mon, 19 Mar 2018 16:32:16 -0700 (PDT) MIME-Version: 1.0 Received: by 2002:a9d:2eac:0:0:0:0:0 with HTTP; Mon, 19 Mar 2018 16:32:16 -0700 (PDT) In-Reply-To: References: <20180319061108.24178-1-k.marinushkin@gmail.com> <20180319074019.GA30688@kroah.com> From: Ruslan Bilovol Date: Tue, 20 Mar 2018 01:32:16 +0200 Message-ID: Subject: Re: [PATCH] ALSA: usb-audio: Fix parsing descriptor of UAC2 processing unit To: Takashi Iwai Cc: Kirill Marinushkin , Greg Kroah-Hartman , alsa-devel@alsa-project.org, Mark Brown , Thomas Gleixner , Felipe Balbi , Philippe Ombredanne , Jaroslav Kysela , linux-kernel@vger.kernel.org Content-Type: text/plain; charset="UTF-8" Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Mon, Mar 19, 2018 at 5:45 PM, Takashi Iwai wrote: > On Mon, 19 Mar 2018 08:47:49 +0100, > Takashi Iwai wrote: >> >> On Mon, 19 Mar 2018 08:40:19 +0100, >> Greg Kroah-Hartman wrote: >> > >> > On Mon, Mar 19, 2018 at 07:11:08AM +0100, Kirill Marinushkin wrote: >> > > Currently, the offsets in the UAC2 processing unit descriptor are >> > > calculated incorrectly. It causes an issue when connecting the device which >> > > provides such a feature: >> > > >> > > ~~~~ >> > > [84126.724420] usb 1-1.3.1: invalid Processing Unit descriptor (id 18) >> > > ~~~~ >> > > >> > > After this patch is applied, the UAC2 processing unit inits w/o this error. >> > > >> > > Fixes: 5e1ddb481776 ("UAPI: (Scripted) Disintegrate include/linux/usb") >> > > Signed-off-by: Kirill Marinushkin >> > > Cc: Mark Brown >> > > Cc: Jaroslav Kysela >> > > Cc: Takashi Iwai >> > > Cc: Thomas Gleixner >> > > Cc: Felipe Balbi >> > > Cc: Philippe Ombredanne >> > > Cc: Greg Kroah-Hartman >> > > Cc: Ruslan Bilovol >> > > Cc: linux-kernel@vger.kernel.org >> > > Cc: alsa-devel@alsa-project.org >> > > --- >> > > include/uapi/linux/usb/audio.h | 4 ++-- >> > > 1 file changed, 2 insertions(+), 2 deletions(-) >> > >> > Cc: stable >> > perhaps? >> >> Yes, it deserves. But I'd need to double-check the UAC2 >> specification. It's interesting that such a basic thing hasn't hit >> until now. Maybe just because it's a fairly minor feature. > > ... and the patch looks correct, after confirming the UAC2 spec. > Now I applied it, with a minor correction of Fixes tag, which actually > was introduced by 23caaf19b11e ("ALSA: usb-mixer: Add support for > Audio Class v2.0"), and adding Cc to stable. > I also checked UAC1/UAC2 spec and the patch looks good. What's interesting it seems nobody faced this issue (after searching ower Internet can't find any mention) which was present from the beginning of UAC2 driver implementation. Thanks, Ruslan