From: Clemens Ladisch <clemens@ladisch.de>
To: Peter Chen <hzpeterchen@gmail.com>,
Ruslan Bilovol <ruslan.bilovol@gmail.com>
Cc: Felipe Balbi <balbi@kernel.org>, Daniel Mack <zonque@gmail.com>,
Jassi Brar <jassisinghbrar@gmail.com>,
linux-usb@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 0/3] USB Audio Gadget refactoring
Date: Tue, 16 Aug 2016 11:32:55 +0200 [thread overview]
Message-ID: <f01d3823-e33f-118c-7221-cdc805254da7@ladisch.de> (raw)
In-Reply-To: <20160816091611.GA25819@shlinux2>
Peter Chen wrote:
> I find UAC2 (UAC1 is ok) support is not well with the latest mainline
> kernel w/o your patch set. The windows7 can't install the driver
> successfully
Windows does not have UAC2 support.
> and the playback shows underrun (using local codec)
> using Linux host.
> # arecord -f dat -t wav -D hw:1,0 | aplay -D hw:0,0 &
The clocks of the two devices are not synchronized.
In the ALSA API, a PCM device is assumed to have its own clock, so it is
not possible to synchronize the USB gadget to the actual sound device
without some separate mechanism (like the old uac1 gadget probably has).
Regards,
Clemens
next prev parent reply other threads:[~2016-08-16 9:33 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-13 22:21 Ruslan Bilovol
2016-08-13 22:21 ` [PATCH v2 1/3] usb: gadget: f_uac2: remove platform driver/device creation Ruslan Bilovol
2016-08-13 22:21 ` [PATCH v2 2/3] usb: gadget: f_uac2: split out audio core Ruslan Bilovol
2016-08-16 18:20 ` kbuild test robot
2016-08-16 20:46 ` Ruslan Bilovol
2016-08-13 22:21 ` [PATCH v2 3/3] usb: gadget: add f_uac1 variant based on new u_audio api Ruslan Bilovol
2016-08-16 2:52 ` Peter Chen
2016-08-16 20:24 ` Ruslan Bilovol
2016-08-16 9:16 ` [PATCH v2 0/3] USB Audio Gadget refactoring Peter Chen
2016-08-16 9:32 ` Clemens Ladisch [this message]
2016-08-16 9:49 ` Peter Chen
2016-08-16 10:13 ` Clemens Ladisch
2016-08-16 20:40 ` 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=f01d3823-e33f-118c-7221-cdc805254da7@ladisch.de \
--to=clemens@ladisch.de \
--cc=balbi@kernel.org \
--cc=hzpeterchen@gmail.com \
--cc=jassisinghbrar@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=ruslan.bilovol@gmail.com \
--cc=zonque@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
all inboxes | Powered by JetHome®