16 Dec
2013
16 Dec
'13
8:59 a.m.
On Fri, Dec 13, 2013 at 08:48:46PM -0700, Stephen Warren wrote:
My original intention was to have a 100ms timeout. However, the timer operations used return values in ms not us, so we ended up with a 100s timeout instead. Fixing this exposes that some operations need longer to operate than 100ms, so bump the timeout up to a whole second.
Reported-by: Andre Heider a.heider@gmail.com Signed-off-by: Stephen Warren swarren@wwwdotorg.org
Reviewed-by: Andre Heider a.heider@gmail.com
Btw, the "get timing" mbox call I mentioned the other day is not what I thought it is. I tried it and it doesn't describe how long the "power on" call would take. I get "1" for every device except UART, for which 40000 was returned iirc.
Thanks, Andre