Initialize TID to dummy value correctly
Previously the code in the quickstep latency measurement script
assumes a dummy value of -1 was put into the current TID, but that
was not the case. It turns out it was actually a 0, which is a
perfectly legal value. This didn't cause problems because usually
the first event immediately overwrites that value. I've been
using a device where that is not the case (from a new vendor) and
this script now fails.
This CL simply changes the value to be initialized to -1 like it
was supposed to, and it seems to fix the problem.
BUG=none
TEST=manually tested
Change-Id: I87790b2a0dfac39ffdfba22777deb1bdc6d7e3a6
Signed-off-by: Charlie Mooney <charliemooney@chromium.org>
Reviewed-on: https://chromium-review.googlesource.com/298870
Reviewed-by: Shyh-In Hwang <josephsih@chromium.org>
1 file changed
