Hi Michael, On 5/6/2024 4:06 PM, Michael Grzeschik wrote:
This patch is splitting up the interrupt event handling from one interrupt thread to separate per endpoint interrupt threads.
I assume that the incentive from doing this is to improve overall throughput numbers. Would you be able to share some data on the benefits of moving to per EP event management?
To achieve this we create a new dwc3 interrupt domain in which we map all claimed interrupts to individual interrupt threads. Although the gadget layer is preparing the claimed parameter of each usb_ep which could be checked if the endpoint is to used or not, the claimed value was 0 for each ep in gadget_start. This was tested when describing some composite gadget using configfs.
yeah... the claimed flag is cleared by the USB gadget, ie USB configfs (not sure if you're using this) whenever it adds a USB config. This is to handle multi config situations, so subsequent USB configs can be assigned (resuse) endpoints, since only one config is active at a time for a USB device.
This was a struggle for me as well when adding the TXFIFO resizing logic. We won't actually know which EPs are going to be used until the host issues the set configuration packet to select a config, and the set_alt() callback issues usb_ep_enable(). So the implementation (TXFIFO resizing) is currently based on the maximum potential endpoints used by any USB configuration.
Not sure if having 31 (potentially) different IRQ entries would be ok, but maybe it would be simpler to just to request IRQ for dwc->num_eps always?
Have you tried this on a multi config device? Thanks Wesley Cheng
