| author | Nikhil Devshatwar <nikhil.nd@ti.com> | |
| Wed, 7 Sep 2016 06:47:19 +0000 (12:17 +0530) | ||
| committer | Nikhil Devshatwar <nikhil.nd@ti.com> | |
| Wed, 7 Sep 2016 06:53:49 +0000 (12:23 +0530) | ||
| commit | a30dd9a5fc1ae7cdfb8c17a4685efb7eaf693ddc | |
| tree | c80966f8da55551fdff982ff5f9b8702270fd5f2 | tree | snapshot (tar.xz tar.gz zip) |
| parent | 1120d2cad0858de45cc9ad636405a3d38613a051 | commit | diff |
dmabuftest: Fix latency profiling using monotonic time
V4L2 driver uses monotonic timestamp to report the frame capture
time. While the application is using system time to calculate the
latency.
Due to this, the latencies reported with '--debug' option are too high.
Fix this by using monotonic timestamp for comparison.
Signed-off-by: Nikhil Devshatwar <nikhil.nd@ti.com>
V4L2 driver uses monotonic timestamp to report the frame capture
time. While the application is using system time to calculate the
latency.
Due to this, the latencies reported with '--debug' option are too high.
Fix this by using monotonic timestamp for comparison.
Signed-off-by: Nikhil Devshatwar <nikhil.nd@ti.com>
| util/v4l2.c | diff | blob | history |