On Mon, Jan 16, 2017 at 12:40:06PM +0200, Felipe Balbi wrote: > > Hi, > > Peter Chen <peter.chen@xxxxxxx> writes: > > There are only two requests for uac2, it may not be enough at high > > loading system which usb interrupt handler can't be serviced on > > time, then the data will be lost since it is isoc transfer for audio. > > > > In this patch, we introduce a parameter for the number for usb request, > > and the user can override it if current number for request is not enough > > for his/her use case. > > > > Besides, update this parameter for legacy audio gadget and documentation. > > I would rather just drop pre-allocation of requests. Every time Audio > wants transmit data you allocate and queue a request there and free() > the request on completion. > > All of these functions already have a ton of parameters :-s > At high loading system, how can we make sure the interrupt can be serviced in one isoc time slice? We ran out this problem at one customer project, and even at default mainline, the aplay will meet underrun using UAC2. -- Best Regards, Peter Chen -- To unsubscribe from this list: send the line "unsubscribe linux-usb" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
