[media] exynos4-is: use monotonic timestamps as advertized
authorArnd Bergmann <arnd@arndb.de>
Thu, 17 Sep 2015 21:19:35 +0000 (18:19 -0300)
committerMauro Carvalho Chehab <mchehab@osg.samsung.com>
Thu, 1 Oct 2015 11:27:59 +0000 (08:27 -0300)
The exynos4 fimc capture driver claims to use monotonic
timestamps but calls ktime_get_real_ts(). This is both
an incorrect API use, and a bad idea because of the y2038
problem and the fact that the wall clock time is not reliable
for timestamps across suspend or settimeofday().

This changes the driver to use the normal v4l2_get_timestamp()
function like all other drivers.

Signed-off-by: Arnd Bergmann <arnd@arndb.de>
Acked-by: Sylwester Nawrocki <s.nawrocki@samsung.com>
Signed-off-by: Hans Verkuil <hans.verkuil@cisco.com>
Signed-off-by: Mauro Carvalho Chehab <mchehab@osg.samsung.com>
drivers/media/platform/exynos4-is/fimc-capture.c

index cfebf292e15a9290b6130b9881760180163f7e0f..776ea6d78d0347c80064df6fd560113414023450 100644 (file)
@@ -183,8 +183,6 @@ void fimc_capture_irq_handler(struct fimc_dev *fimc, int deq_buf)
        struct v4l2_subdev *csis = p->subdevs[IDX_CSIS];
        struct fimc_frame *f = &cap->ctx->d_frame;
        struct fimc_vid_buffer *v_buf;
-       struct timeval *tv;
-       struct timespec ts;
 
        if (test_and_clear_bit(ST_CAPT_SHUT, &fimc->state)) {
                wake_up(&fimc->irq_queue);
@@ -193,13 +191,9 @@ void fimc_capture_irq_handler(struct fimc_dev *fimc, int deq_buf)
 
        if (!list_empty(&cap->active_buf_q) &&
            test_bit(ST_CAPT_RUN, &fimc->state) && deq_buf) {
-               ktime_get_real_ts(&ts);
-
                v_buf = fimc_active_queue_pop(cap);
 
-               tv = &v_buf->vb.v4l2_buf.timestamp;
-               tv->tv_sec = ts.tv_sec;
-               tv->tv_usec = ts.tv_nsec / NSEC_PER_USEC;
+               v4l2_get_timestamp(&v_buf->vb.v4l2_buf.timestamp);
                v_buf->vb.v4l2_buf.sequence = cap->frame_count++;
 
                vb2_buffer_done(&v_buf->vb, VB2_BUF_STATE_DONE);