From: Pavel Hofman <pavel.hofman@ivitera.com>
To: harrison conroy <harrisonconroy@me.com>, ruslan.bilovol@gmail.com
Cc: linux-usb@vger.kernel.org
Subject: Re: usb:gadget:f_uac2: EP OUT is adaptive instead of async
Date: Sat, 25 Jul 2020 12:24:20 +0200 [thread overview]
Message-ID: <6194f859-aa61-90fa-043e-1df02b01bacb@ivitera.com> (raw)
In-Reply-To: <79D67DF9-2A12-40DE-AFF7-4FF68193AD1C@me.com>
Dne 22. 07. 20 v 17:25 harrison conroy napsal(a):
> Hi Ruslan,
>
> I am working on a project that involves using an RPi 4 as a USB Gadget
> and we have run into the feedback endpoint issue causing Windows 10 to
> not recognize it as a USB audio device. Do you have any updates on this
> patch for the community? Any help would be greatly appreciated.
As a temporary workaround you can change the EP OUT type from
USB_ENDPOINT_SYNC_ASYNC to USB_ENDPOINT_SYNC_ADAPTIVE.
Or you can add implicit feedback flag to the EP IN. Win10 should handle
implicit feedback OK, unlike Win7. Unfortunately linux still requires an
explicit quirk for the implicit feedback
https://www.spinics.net/lists/alsa-devel/msg111824.html . Yet it is
still a workaround because IMO the existing EP IN is in fact not async
but adaptive, clocked by the USB frames.
Pavel.
next parent reply other threads:[~2020-07-25 10:31 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <79D67DF9-2A12-40DE-AFF7-4FF68193AD1C@me.com>
2020-07-25 10:24 ` Pavel Hofman [this message]
2020-07-27 12:21 ` usb:gadget:f_uac2: EP OUT is adaptive instead of async Ruslan Bilovol
2020-02-06 13:22 Pavel Hofman
2020-02-06 15:41 ` Greg KH
2020-02-06 16:09 ` Pavel Hofman
2020-02-11 16:10 ` Ruslan Bilovol
2020-02-11 19:02 ` Pavel Hofman
2020-04-24 11:21 ` Pavel Hofman
2020-04-24 12:34 ` Ruslan Bilovol
2020-04-24 13:50 ` Pavel Hofman
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=6194f859-aa61-90fa-043e-1df02b01bacb@ivitera.com \
--to=pavel.hofman@ivitera.com \
--cc=harrisonconroy@me.com \
--cc=linux-usb@vger.kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).