The contruct on qti_haptics_upload_effect()
rem = hrtimer_get_remaining(&chip->hap_disable_timer);
time_us = ktime_to_us(rem);
leads to negative values. If the followed usleep is called with this value
it wait's an uncomfortable range of time...
Guard this call by an check. After that, multiple runs of the
CtsOsTestCases - android.os.cts.VibratorTest ran without issues.
Change-Id: Ife8f55c3b3ceb8bb35d30fe1448a51ab32e0b904
2c99b08e05