[RPI-B] [HEADS UP] DWC OTG TX path optimisation for 11-current

[Hans Petter Selasky]

On 07/31/15 04:11, Hans Petter Selasky wrote:
> Anyhow, I think that I figured out why the system has so slow response
> time when it's triggered. In general, it's not good idea to not limit
> somehow interrupt filter execution time. If something wrong is
> happening, then such filter can halt all system. I can get back fast
> system response time with attached patch. Note that it's only a
> proof-of-concept patch and it does not remove the problem. There is
> still something what generates big load when it's triggered even if
> system is 99% idle after trigger was pulled.

Hi,

If you could figure out exactly which "goto repeat" is looping, it would 
be a great help to me understand the problem. Maybe you can increase the 
counter and when it reaches the limit you can print some kind of "int 
last_goto_from", which you set before the "goto repeat;" ?

--HPS