summaryrefslogtreecommitdiffstats
path: root/Documentation/DocBook
diff options
context:
space:
mode:
authorHans Verkuil <hans.verkuil@cisco.com>2014-02-24 14:44:50 -0300
committerMauro Carvalho Chehab <m.chehab@samsung.com>2014-03-05 16:18:59 -0300
commitf1343281d829d920d4158827bb420a24afe905f7 (patch)
treee921f26a18b0519017f59f3b28e570675aff3139 /Documentation/DocBook
parent80807fada4398d11ebd2bb28b3b49ca6a59e1260 (diff)
downloadop-kernel-dev-f1343281d829d920d4158827bb420a24afe905f7.zip
op-kernel-dev-f1343281d829d920d4158827bb420a24afe905f7.tar.gz
[media] vb2: fix timecode and flags handling for output buffers
When sending a buffer to a video output device some of the fields need to be copied so they arrive in the driver. These are the KEY/P/BFRAME flags and the TIMECODE flag, and, if that flag is set, the timecode field itself. There are a number of functions involved in this: the __fill_vb2_buffer() is called while preparing a buffer. For output buffers the buffer contains the video data, so any meta data associated with that (KEY/P/BFRAME and the field information) should be stored at that point. The timecode, timecode flag and timestamp information is not part of that, that information will have to be set when vb2_internal_qbuf() is called to actually queue the buffer to the driver. Usually VIDIOC_QBUF will do the prepare as well, but you can call PREPARE_BUF first and only later VIDIOC_QBUF. You most likely will want to set the timestamp and timecode when you actually queue the buffer, not when you prepare it. Finally, in buf_prepare() make sure the timestamp and sequence fields are actually cleared so that when you do a QUERYBUF of a prepared-but-not-yet-queued buffer you will not see stale timestamp/sequence data. Signed-off-by: Hans Verkuil <hans.verkuil@cisco.com> Signed-off-by: Sakari Ailus <sakari.ailus@iki.fi> Signed-off-by: Mauro Carvalho Chehab <m.chehab@samsung.com>
Diffstat (limited to 'Documentation/DocBook')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud