Yes,
I added the next_sched_frame to track the next uframe that there is
anything to do in the periodic schedule. The SOF interrupt is then
disabled until that uframe (although the FIQ still runs each uframe to
decide whether to trigger the USB interrupt)
Gordon
On 21/08/2013 22:24, "Matthijs K
Hi Paul,
> > > @@ -365,6 +366,7 @@ struct dwc2_hsotg {
> > > u8 otg_port;
> > > u32 *frame_list;
> > > dma_addr_t frame_list_dma;
> > > + int next_sched_frame;
> >
> > This variable is still not really used, I think. Most of the mentions in
> > the patch are assignments, except for these tw
org; Dom
> Cobley
> Subject: Re: [PATCH 2/3] staging: dwc2: add NAK holdoff patch from downstream
> Pi kernel
>
> Hi Paul,
>
> > Add the NAK holdoff patch from the downstream Raspberry Pi kernel.
> > This allows the transfer scheduler to better handle &
Hi Paul,
> Add the NAK holdoff patch from the downstream Raspberry Pi kernel.
> This allows the transfer scheduler to better handle "cheeky devices
> that just hold off using NAKs".
> @@ -365,6 +366,7 @@ struct dwc2_hsotg {
> u8 otg_port;
> u32 *frame_list;
> dma_addr_t frame_li
From: Dom Cobley
Add the NAK holdoff patch from the downstream Raspberry Pi kernel.
This allows the transfer scheduler to better handle "cheeky devices
that just hold off using NAKs".
[original patch from Dom Cobley]
Signed-off-by: Dom Cobley
[adapted to dwc2 driver by Paul Zimmerman]
Signed-of
