Received: by 10.192.165.148 with SMTP id m20csp1803200imm; Thu, 26 Apr 2018 02:28:01 -0700 (PDT) X-Google-Smtp-Source: AIpwx49ug7YPsXcqzFeVFs4zB2opdLQhmZhuzkPW8a+DgHlaFHhz8v2uiP3oEqJ93rfW/2NM5jFD X-Received: by 10.99.121.69 with SMTP id u66mr18274076pgc.376.1524734880949; Thu, 26 Apr 2018 02:28:00 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1524734880; cv=none; d=google.com; s=arc-20160816; b=wq0/FBZGaOLMsLUn+UM65iZBsGqaQ4e1FamtCHoJRMqVNI9jmAV+jTvrDwO09ZJZSD r0BUg79PFELkXu7mECBBwUpkpb4pZBwwxmTwawgXCaPLqZnbmMOJF63GEKMS3twOCtJq QDReUXtuYZzxP44JB/VpDY97XbxbDHyGq4R2R+APU9UIDUoDUv8p+UL/aKztRNQ6ctPR RgG291EiqtEgpXgjMz63UfUfbUdm3ZtcRsREbk+LKln+LxZYPUneSTPnH0IL9YP/X186 bWhcpY1go25QfWvjWJg1/hM5CMMd/XsobDHRTlDiZBT0J0d2SIVLCbAayskowObWl1Ca cQGQ== 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=ClZt5Zn/d+kMfuWdOlwPS5jYcdRb6ywL01OywEYIoOQ=; b=OPGzgeA+mHReNPmWzafzgJEZp+bkQii8eL62Xt45OTglOZ+zK8gZON500n5tHcXDrA 5yVjXeqQ5O0poVx2WyUEZZkW90NrA/JJuKLdb7v7U3fxQo/A3+WEyXXCeGXmBSC2K59C Tii3e88/hErSAZDskS55DCG+5FmvbxfePttYVR1bVc8VVGiCNWUBVpUL7PX7xu9LLq/d Cf2xhQgxb03mZJ+i5w0RXXLqKgC6dVs7Pe6VAsq86usf5QoRfSwomUVN71CQd/flCmGV L3WZMNnVG1IgCaz8X7lBIAyOYCU6isarBXbPDzCd0BAKWkWeibiwob9ohv/uGhIWue8e BXaQ== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@gmail.com header.s=20161025 header.b=GRg0IOrw; 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 y13si15369825pge.491.2018.04.26.02.27.46; Thu, 26 Apr 2018 02:28:00 -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=GRg0IOrw; 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 S1754817AbeDZJ0Q (ORCPT + 99 others); Thu, 26 Apr 2018 05:26:16 -0400 Received: from mail-oi0-f67.google.com ([209.85.218.67]:47067 "EHLO mail-oi0-f67.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753403AbeDZJ0L (ORCPT ); Thu, 26 Apr 2018 05:26:11 -0400 Received: by mail-oi0-f67.google.com with SMTP id y15-v6so15520793oia.13 for ; Thu, 26 Apr 2018 02:26:11 -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=ClZt5Zn/d+kMfuWdOlwPS5jYcdRb6ywL01OywEYIoOQ=; b=GRg0IOrwq4AWJL0LSFSanvk4yv7o1BI7xhZlqkYIQpKVOK8w61aXzAgRzvuKXP7v/g 6UgZu2YHS/UKpIFsZ6yWR5WxsvowB4V3Txi6PHvUzVmnAsGw8NOlF1AiYwV/mmlvOAqH Vh1zyTiMd+8kdYJriQfinLDCzioE3E1BP82VU1virMeVbdxItboZ4kXj0bdc2N4pAKNr bliNOMbNM8VFlhtobXm26Kk4wjggU8efLJOinqZFL4MAEQes2Aki1ahZZbpJkG6ebpoE 2oOsB+JnUJDZKDIpZhIFU1xPurNNkdcTgnlJKUjQUn2QDJ3msdlMYpGUBzF3oht7yP+G EB/A== 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=ClZt5Zn/d+kMfuWdOlwPS5jYcdRb6ywL01OywEYIoOQ=; b=uRMhxtAyCwj6L0fBHpeP0zjd2qOB17QHf7vrWuhOENS4dZ+AXT8Q3T3/hH0PCW9kQt R30b2V6xeMA15mMneU77o/QfSZrSj0jcIcl9aquGhuMGzINqWjfCF99OQOON/h9r6V9f DmAfo1gutyJNfIfHoFBSPbg/yvrMEzQE/s3/oh2O68sqxE9S5dO53f0/z1YspvlSRyX/ +VNn28h+qO7w/X0UAuy8DGmPRiAm7ZBn60aj1l935/FETDE1Kj5itLbSJpGYwyAU7Hrl D4PqDByaJUMKDOHOq3t1dwENPfDx1XX30eK9WebjoBDDvrtW6hqY/zgT6xVmy4CoDpLT sJrg== X-Gm-Message-State: ALQs6tDjSStSYa7nEHmgbwLImYvPROAmyspJFBN5bVWK8uwJGIARFX/7 YtG5hSUTfcuPr9Lib+BrFsADp+6GmKnwAhsqDKo= X-Received: by 2002:aca:6a41:: with SMTP id f62-v6mr20838185oic.159.1524734771083; Thu, 26 Apr 2018 02:26:11 -0700 (PDT) MIME-Version: 1.0 Received: by 2002:a9d:2c03:0:0:0:0:0 with HTTP; Thu, 26 Apr 2018 02:26:10 -0700 (PDT) In-Reply-To: References: <20180420170327.31569-1-jorge.sanjuan@codethink.co.uk> <20180424172445.31928-1-jorge.sanjuan@codethink.co.uk> From: Ruslan Bilovol Date: Thu, 26 Apr 2018 12:26:10 +0300 Message-ID: Subject: Re: [alsa-devel] [PATCH v2 0/4] ALSA: usb: UAC3 new features. To: Takashi Iwai , Jorge Sanjuan Cc: Greg Kroah-Hartman , alsa-devel@alsa-project.org, 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 Tue, Apr 24, 2018 at 9:02 PM, Takashi Iwai wrote: > On Tue, 24 Apr 2018 19:24:41 +0200, > Jorge Sanjuan wrote: >> >> v2 fixes: >> - If/else statements braces style fixes. >> - Add wrapping function to mixer unit code. >> - Make connectors control kctl struct const. >> - Little endian to cpu conversion in several places. >> - Sing off and add Fixes tag to fixup commit. >> - Remove flex-array for a struct that is used statically. >> >> Now that the UAC3 patch [1] has made it to linux-next I have some extra >> features to make a UAC3 device fully work in Linux. Including Jack >> insertion control that I have put on top of this other patch [2] for >> UAC2. Also adding support for the UAC3 Mixer Unit which is most likely >> to appear in most headset type devices. Thanks for adding these improvements! > > These patches look reasonable, I'm OK to merge. But I'll wait for > Ruslan's comments (or at best with test results). I reviewed first 3 patches and will review jack detection patch later, and I'm going to test this patchset in a next few days. > >> UAC3 devices also require to have a Basic Audio Device (BADD) in a separate >> config for which both Ruslan Bilovol and myself have submited different >> approaches[3][4] but I don't know what the final merge will be. Once there >> is official support for BADD, we'll need to test it with an actual UAC3 >> device to confirm it all wokrs. > > Could you guys try to get agreement which approach should we take? > > I have no big preference. Currently Ruslan's patch series look > easier, just because its addition is a bit smaller, though. The BADD devices are quite simple, so direct initialization internal ALSA structures looks easy and straightforward, comparing to generation of missing descriptors. I'm currently improving the patch series so it will look even more smaller and easier, let's see how it goes Thanks, Ruslan > > > Thanks! > > Takashi > >> All this features are tested with an actual UAC3 device that is still in >> development. For this patch series, only the legacy config (#1. UAC1/UAC2) >> and the UAC3 config have been tested. The BADD config is only tested using >> and updated verison of [4]. >> >> [1]: https://patchwork.kernel.org/patch/10298179/ >> [2]: https://patchwork.kernel.org/patch/10305847/ >> [3]: https://patchwork.kernel.org/patch/10340851/ >> [4]: https://www.spinics.net/lists/alsa-devel/msg71617.html >> >> Based on linux-next tag: next-20180420 >> >> Jorge Sanjuan (3): >> ALSA: usb-audio: UAC3. Add support for mixer unit. >> ALSA: usb-audio: Use Class Specific EP for UAC3 devices. >> ALSA: usb-audio: UAC3 Add support for connector insertion. >> >> Michael Drake (1): >> ALSA: usb-audio: ADC3: Fix channel mapping conversion for ADC3. >> >> include/linux/usb/audio-v2.h | 7 ++ >> include/linux/usb/audio-v3.h | 14 +++ >> include/uapi/linux/usb/audio.h | 13 ++- >> sound/usb/mixer.c | 195 +++++++++++++++++++++++++++++++++++++---- >> sound/usb/stream.c | 11 ++- >> 5 files changed, 217 insertions(+), 23 deletions(-) >> >> -- >> 2.11.0 >> >> > _______________________________________________ > Alsa-devel mailing list > Alsa-devel@alsa-project.org > http://mailman.alsa-project.org/mailman/listinfo/alsa-devel