Sakari Ailus c6c092135d [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>		2014-03-05 16:20:28 -03:00
..
media	[media] v4l: Document timestamp behaviour to correspond to reality	2014-03-05 16:20:28 -03:00
.gitignore
80211.tmpl
alsa-driver-api.tmpl
debugobjects.tmpl
device-drivers.tmpl
deviceiobook.tmpl
drm.tmpl
filesystems.tmpl
gadget.tmpl
genericirq.tmpl
kernel-api.tmpl
kernel-hacking.tmpl
kernel-locking.tmpl
kgdb.tmpl
libata.tmpl
librs.tmpl
lsm.tmpl
Makefile
media_api.tmpl
mtdnand.tmpl
networking.tmpl
rapidio.tmpl
regulator.tmpl
s390-drivers.tmpl
scsi.tmpl
sh.tmpl
stylesheet.xsl
tracepoint.tmpl
uio-howto.tmpl
usb.tmpl
writing_usb_driver.tmpl
writing-an-alsa-driver.tmpl
z8530book.tmpl