[media] v4l: Document timestamp behaviour to correspond to reality
authorSakari Ailus <sakari.ailus@iki.fi>
Fri, 25 Jan 2013 18:00:07 +0000 (15:00 -0300)
committerMauro Carvalho Chehab <m.chehab@samsung.com>
Wed, 5 Mar 2014 19:20:28 +0000 (16:20 -0300)
commitc6c092135d4f61b038a41685147c79e966c2399c
treed93179b278d936dacaec7178939465d2f16585b3
parentf1343281d829d920d4158827bb420a24afe905f7
[media] v4l: Document timestamp behaviour to correspond to reality

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
frame.

Remove the note on timestamp accuracy as it is fairly subjective what is
actually an unstable timestamp.

Also remove explanation that output buffer timestamps can be used to delay
outputting a frame.

Remove the footnote saying we always use realtime clock.

Signed-off-by: Sakari Ailus <sakari.ailus@iki.fi>
Acked-by: Hans Verkuil <hans.verkuil@cisco.com>
Signed-off-by: Mauro Carvalho Chehab <m.chehab@samsung.com>
Documentation/DocBook/media/v4l/io.xml