jtag: clean up jtag_sleep, handle short sleeps correctly via usleep
short sleeps are handled via usleep, longer sleeps we round up to nearest ms. There was a bug in jtag_sleep() in that it would round *down* to nearest ms, thus making all <1ms sleeps 0. Found by inspection rather than symptom. Signed-off-by: Øyvind Harboe <oyvind.harboe@zylin.com>
This commit is contained in:
parent
689c244389
commit
bb0d11cba9
|
@ -871,9 +871,16 @@ static int jtag_reset_callback(enum jtag_event event, void *priv)
|
|||
return ERROR_OK;
|
||||
}
|
||||
|
||||
/* sleep at least us microseconds. When we sleep more than 1000ms we
|
||||
* do an alive sleep, i.e. keep GDB alive. Note that we could starve
|
||||
* GDB if we slept for <1000ms many times.
|
||||
*/
|
||||
void jtag_sleep(uint32_t us)
|
||||
{
|
||||
alive_sleep(us/1000);
|
||||
if (us < 1000)
|
||||
usleep(us);
|
||||
else
|
||||
alive_sleep((us+999)/1000);
|
||||
}
|
||||
|
||||
/* Maximum number of enabled JTAG devices we expect in the scan chain,
|
||||
|
|
Loading…
Reference in New Issue