Hi Hans,
Thanks for your comments.
On Mon, Jan 28, 2013 at 10:55:14AM +0100, Hans Verkuil wrote:
> On Fri January 25 2013 19:03:29 Sakari Ailus wrote:
> > Document that monotonic timestamps are taken after the corresponding frame
> > has been received, not when the reception has begun. This corre
Hi Sakari,
On Tuesday 29 January 2013 01:02:20 Sakari Ailus wrote:
> On Mon, Jan 28, 2013 at 08:56:21PM +0100, Laurent Pinchart wrote:
> > On Monday 28 January 2013 10:55:14 Hans Verkuil wrote:
> > > On Fri January 25 2013 19:03:29 Sakari Ailus wrote:
> > > > Document that monotonic timestamps are
Hi Laurent,
On Mon, Jan 28, 2013 at 08:56:21PM +0100, Laurent Pinchart wrote:
> On Monday 28 January 2013 10:55:14 Hans Verkuil wrote:
> > On Fri January 25 2013 19:03:29 Sakari Ailus wrote:
> > > Document that monotonic timestamps are taken after the corresponding frame
> > > has been received, n
On Monday 28 January 2013 10:55:14 Hans Verkuil wrote:
> On Fri January 25 2013 19:03:29 Sakari Ailus wrote:
> > Document that monotonic timestamps are taken after the corresponding frame
> > has been received, not when the reception has begun. This corresponds to
> > the reality of current drivers
On Fri January 25 2013 19:03:29 Sakari Ailus wrote:
> Document that monotonic timestamps are taken after the corresponding frame
> has been received, not when the reception has begun. This corresponds to the
> reality of current drivers: the timestamp is naturally taken when the
> hardware triggers
Document that monotonic timestamps are taken after the corresponding frame
has been received, not when the reception has begun. This corresponds to the
reality of current drivers: the timestamp is naturally taken when the
hardware triggers an interrupt to tell the driver to handle the received
fram
