From: Takashi Iwai <tiwai@suse.de>
To: "Ruslan Bilovol" <ruslan.bilovol@gmail.com>
Cc: <alsa-devel@alsa-project.org>,
"Jorge" <jorge.sanjuan@codethink.co.uk>,
"Pierre-Louis Bossart" <pierre-louis.bossart@linux.intel.com>,
"Greg Kroah-Hartman" <gregkh@linuxfoundation.org>,
<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2 2/2] ALSA: usb: initial USB Audio Device Class 3.0 support
Date: Mon, 19 Mar 2018 17:28:56 +0100 [thread overview]
Message-ID: <s5h1sggvxkn.wl-tiwai@suse.de> (raw)
In-Reply-To: <1521423963-24677-3-git-send-email-ruslan.bilovol@gmail.com>
On Mon, 19 Mar 2018 02:46:03 +0100,
Ruslan Bilovol wrote:
>
> Recently released USB Audio Class 3.0 specification
> introduces many significant changes comparing to
> previous versions, like
> - new Power Domains, support for LPM/L1
> - new Cluster descriptor
> - changed layout of all class-specific descriptors
> - new High Capability descriptors
> - New class-specific String descriptors
> - new and removed units
> - additional sources for interrupts
> - removed Type II Audio Data Formats
> - ... and many other things (check spec)
>
> It also provides backward compatibility through
> multiple configurations, as well as requires
> mandatory support for BADD (Basic Audio Device
> Definition) on each ADC3.0 compliant device
>
> This patch adds initial support of UAC3 specification
> that is enough for Generic I/O Profile (BAOF, BAIF)
> device support from BADD document.
>
> Signed-off-by: Ruslan Bilovol <ruslan.bilovol@gmail.com>
Most code changes look fairly straightforward, and not breaking the
UAC1/UAC2 stuff. So the stuff is good enough through a quick glance.
I suppose it's better to merge via sound git tree.
Greg, could you check include/linux/usb/* (and uapi) stuff and give an
ack if it's OK?
In anyway, I'll check the specs and compare with the definitions in
this patch.
And, just minor nitpicking regarding the code change:
it's better to drop the parentheses in a line like below
> + if ((protocol == UAC_VERSION_1) || (protocol == UAC_VERSION_2)) {
that is,
if (protocol == UAC_VERSION_1 || protocol == UAC_VERSION_2) {
The indentation became so deep in some functions, and it's better to
refactor, but this can be done later once after all implementations
are finished.
thanks,
Takashi
next prev parent reply other threads:[~2018-03-19 16:28 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-19 1:46 [PATCH v2 0/2] USB Audio Device Class 3.0 support Ruslan Bilovol
2018-03-19 1:46 ` [PATCH v2 1/2] ALSA: usb-audio: move audioformat quirks to quirks.c Ruslan Bilovol
2018-03-19 16:00 ` Takashi Iwai
2018-03-19 23:42 ` Ruslan Bilovol
2018-03-19 1:46 ` [PATCH v2 2/2] ALSA: usb: initial USB Audio Device Class 3.0 support Ruslan Bilovol
2018-03-19 13:43 ` kbuild test robot
2018-03-19 16:20 ` Takashi Iwai
2018-03-19 16:28 ` Takashi Iwai [this message]
2018-03-19 17:14 ` Greg Kroah-Hartman
2018-03-19 23:57 ` Ruslan Bilovol
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=s5h1sggvxkn.wl-tiwai@suse.de \
--to=tiwai@suse.de \
--cc=alsa-devel@alsa-project.org \
--cc=gregkh@linuxfoundation.org \
--cc=jorge.sanjuan@codethink.co.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=pierre-louis.bossart@linux.intel.com \
--cc=ruslan.bilovol@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox