[linux-dvb] mdelay() vs. schedule_timeout() in ves1820.c and skystar2.c

[Michael Hunold <hunold@convergence.de>]

Hello,

skystar2.c contains 3 mdelay(20), one mdelay(10) and two mdelay(16) calls.

ves1820.c contains two mdelay(50) calls.

Can the driver authors please check if it's possible to change these 
multiple-ten-milliseconds busyloops for example with

> set_current_state(TASK_INTERRUPTIBLE);
> schedule_timeout ((HZ*ms)/1000);

Can mdelay(16) safely be increased to mdelay(20)?

CU
Michael.


--
Info:
To unsubscribe send a mail to ecartis@linuxtv.org with "unsubscribe linux-dvb" as subject.