From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: Hans Verkuil <hverkuil@xs4all.nl>
Cc: linux-media@vger.kernel.org, linux-usb@vger.kernel.org,
linux-kernel@vger.kernel.org,
Fengguang Wu <fengguang.wu@intel.com>,
Sebastian Andrzej Siewior <bigeasy@linutronix.de>,
Roland Scheidegger <rscheidegger_lists@hispeed.ch>
Subject: Re: [PATCH 1/2] usb: gadget: uvc: Switch to monotonic clock for buffer timestamps
Date: Fri, 28 Mar 2014 12:18:12 +0100 [thread overview]
Message-ID: <1650089.1kJ4DQOsm3@avalon> (raw)
In-Reply-To: <533537E2.9020904@xs4all.nl>
Hi Hans,
On Friday 28 March 2014 09:50:42 Hans Verkuil wrote:
> On 03/23/2014 04:32 PM, Laurent Pinchart wrote:
> > The wall time clock isn't useful for applications as it can jump around
> > due to time adjustement. Switch to the monotonic clock.
> >
> > Signed-off-by: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
> > ---
> >
> > drivers/usb/gadget/uvc_queue.c | 12 +++++-------
> > 1 file changed, 5 insertions(+), 7 deletions(-)
> >
> > diff --git a/drivers/usb/gadget/uvc_queue.c
> > b/drivers/usb/gadget/uvc_queue.c index 0bb5d50..d4561ba 100644
> > --- a/drivers/usb/gadget/uvc_queue.c
> > +++ b/drivers/usb/gadget/uvc_queue.c
> > @@ -364,6 +364,7 @@ static struct uvc_buffer *uvc_queue_next_buffer(struct
> > uvc_video_queue *queue,
> > struct uvc_buffer *buf)
> > {
> > struct uvc_buffer *nextbuf;
> > + struct timespec ts;
> >
> > if ((queue->flags & UVC_QUEUE_DROP_INCOMPLETE) &&
> > buf->length != buf->bytesused) {
> > @@ -379,14 +380,11 @@ static struct uvc_buffer
> > *uvc_queue_next_buffer(struct uvc_video_queue *queue,>
> > else
> > nextbuf = NULL;
> >
> > - /*
> > - * FIXME: with videobuf2, the sequence number or timestamp fields
> > - * are valid only for video capture devices and the UVC gadget
> > usually
> > - * is a video output device. Keeping these until the specs are clear
> > on
> > - * this aspect.
> > - */
> > + ktime_get_ts(&ts);
>
> Why not use the v4l2-common.c helper v4l2_get_timestamp()?
No reason at all. I'll fix that.
> > +
> > buf->buf.v4l2_buf.sequence = queue->sequence++;
> >
> > - do_gettimeofday(&buf->buf.v4l2_buf.timestamp);
> > + buf->buf.v4l2_buf.timestamp.tv_sec = ts.tv_sec;
> > + buf->buf.v4l2_buf.timestamp.tv_usec = ts.tv_nsec / NSEC_PER_USEC;
>
> You should also add:
>
> buf->buf.v4l2_buf.field = V4L2_FIELD_NONE;
>
> I noticed that that was never set, which is wrong.
Good point. Will be fixed in v2.
> > vb2_set_plane_payload(&buf->buf, 0, buf->bytesused);
> > vb2_buffer_done(&buf->buf, VB2_BUF_STATE_DONE);
--
Regards,
Laurent Pinchart
next prev parent reply other threads:[~2014-03-28 11:16 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-23 0:10 [webcam] WARNING: CPU: 0 PID: 1 at drivers/media/v4l2-core/videobuf2-core.c:2207 vb2_queue_init() Fengguang Wu
2014-03-23 15:32 ` [PATCH 0/2] Clock fixes for UVC gadget driver Laurent Pinchart
2014-03-23 15:32 ` [PATCH 1/2] usb: gadget: uvc: Switch to monotonic clock for buffer timestamps Laurent Pinchart
2014-03-28 8:50 ` Hans Verkuil
2014-03-28 11:18 ` Laurent Pinchart [this message]
2014-03-23 15:32 ` [PATCH 2/2] usb: gadget: uvc: Set the vb2 queue timestamp flags Laurent Pinchart
2014-03-28 8:51 ` Hans Verkuil
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1650089.1kJ4DQOsm3@avalon \
--to=laurent.pinchart@ideasonboard.com \
--cc=bigeasy@linutronix.de \
--cc=fengguang.wu@intel.com \
--cc=hverkuil@xs4all.nl \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=rscheidegger_lists@hispeed.ch \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).