Re: [RFC] Timestamps and V4L2

Hi, all.

On 10/15/2012 11:45 AM, Laurent Pinchart wrote:

Hi Sakari,

On Monday 15 October 2012 19:05:49 Sakari Ailus wrote:

quoted

Hi all,

As a summar from the discussion, I think we have reached the following
conclusion. Please say if you agree or disagree with what's below. :-)

- The drivers will be moved to use monotonic timestamps for video buffers.
- The user space will learn about the type of the timestamp through buffer
flags.
- The timestamp source may be made selectable in the future, but buffer
flags won't be the means for this, primarily since they're not available on
subdevs. Possible way to do this include a new V4L2 control or a new IOCTL.

That's my understanding as well. For the concept,

Acked-by: Laurent Pinchart <laurent.pinchart@ideasonboard.com>

I wasn't able to participate in the discussion that led to this, but I'd 
like to suggest and request now that an explicit requirement (of 
whatever scheme is selected) be that a userspace app have a reasonable 
and straightforward way to translate the timestamps to real wall-clock 
time, ideally with enough precision to allow synchronization of cameras 
across multiple computers.

In the systems I work on, for instance, we are recording real-world 
biological processes, some of which vary based on the time of day, and 
it is important to know when a given frame was captured so that 
information can be stored with the raw frame and the data derived from 
it. For many such purposes, an accuracy measured in multiple seconds (or 
even minutes) is fine.

However, when we are using multiple cameras on multiple computers (e.g., 
two or more BeagleBoard xM's, each with a camera connected), we would 
want to synchronize with an accuracy of less than 1 frame time - e.g. 10 
ms or less.

Thanks very much,
Chris MacGregor