From: Pavel Hofman <pavel.hofman@ivitera.com>
To: Minas Harutyunyan <Minas.Harutyunyan@synopsys.com>,
"linux-usb@vger.kernel.org" <linux-usb@vger.kernel.org>
Subject: usb: dwc2: gadget: high-bandwidth (mc > 1) status?
Date: Wed, 24 Nov 2021 08:39:59 +0100 [thread overview]
Message-ID: <ea4697fd-8911-3f79-540b-a03214678ccd@ivitera.com> (raw)
Hi Minas at all,
Please does dwc2 (specifically in BCM2835/RPi) support HS ISOC multiple
transactions mc > 1 reliably? I found this condition
https://elixir.bootlin.com/linux/v5.16-rc2/source/drivers/usb/dwc2/gadget.c#L4041
/* High bandwidth ISOC OUT in DDMA not supported */
if (using_desc_dma(hsotg) && ep_type == USB_ENDPOINT_XFER_ISOC &&
!dir_in && mc > 1) {
dev_err(hsotg->dev,
"%s: ISOC OUT, DDMA: HB not supported!\n", __func__);
return -EINVAL;
}
But I do not know how the Descriptor DMA is critical and whether
disabling it will affect gadget performance seriously.
I know about the RX FIFO sizing requirement (and TX FIFO too I guess),
the current default values can be increased for that particular use case
if needed.
I am trying to learn if it made sense to spend time on adding support
for high-bandwidth to the UAC2 audio gadget to allow using larger
bInterval and mc=2,3 at high samplerates/channel counts (sort of "burst
mode" similar to UAC3). When doing some CPU-demanding DSP it would help
to avoid the time-critical handling every 125us microframe. Both OUT and
IN are important.
Thanks a lot for your expert advice.
Best regards,
Pavel.
next reply other threads:[~2021-11-24 7:40 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-24 7:39 Pavel Hofman [this message]
2021-11-24 14:04 ` usb: dwc2: gadget: high-bandwidth (mc > 1) status? Minas Harutyunyan
2021-11-25 8:47 ` Pavel Hofman
2021-11-26 6:35 ` Minas Harutyunyan
2021-11-26 8:53 ` Pavel Hofman
2021-11-26 9:49 ` Minas Harutyunyan
2021-11-26 11:01 ` 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=ea4697fd-8911-3f79-540b-a03214678ccd@ivitera.com \
--to=pavel.hofman@ivitera.com \
--cc=Minas.Harutyunyan@synopsys.com \
--cc=linux-usb@vger.kernel.org \
/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