| 96ec7d2a6632d0757e2b83bd75c5784d4cc4a456 |
|
02-Sep-2014 |
Mauro Carvalho Chehab <m.chehab@samsung.com> |
[media] vivid: add some missing headers
That remove a few warnings:
drivers/media/platform/vivid/vivid-kthread-out.c:226:5: warning: no previous prototype for 'vivid_start_generating_vid_out' [-Wmissing-prototypes]
int vivid_start_generating_vid_out(struct vivid_dev *dev, bool *pstreaming)
^
drivers/media/platform/vivid/vivid-kthread-out.c:260:6: warning: no previous prototype for 'vivid_stop_generating_vid_out' [-Wmissing-prototypes]
void vivid_stop_generating_vid_out(struct vivid_dev *dev, bool *pstreaming)
^
drivers/media/platform/vivid/vivid-kthread-cap.c:806:5: warning: no previous prototype for 'vivid_start_generating_vid_cap' [-Wmissing-prototypes]
int vivid_start_generating_vid_cap(struct vivid_dev *dev, bool *pstreaming)
^
drivers/media/platform/vivid/vivid-kthread-cap.c:841:6: warning: no previous prototype for 'vivid_stop_generating_vid_cap' [-Wmissing-prototypes]
void vivid_stop_generating_vid_cap(struct vivid_dev *dev, bool *pstreaming)
^
Signed-off-by: Mauro Carvalho Chehab <m.chehab@samsung.com>
|
| 3f682ffcf957b556a7868decd5593d765ed3455d |
|
25-Aug-2014 |
Hans Verkuil <hans.verkuil@cisco.com> |
[media] vivid: add the kthread code that controls the video rate
Add the kthread handlers for video/vbi capture and video/vbi output.
These carefully control the rate at which frames are generated (video
capture) and accepted (video output). While the short-term jitter is
around the order of a jiffie, in the long term the rate matches the
configured framerate exactly.
The capture thread handler also takes care of the video looping and
of capture and overlay support. This is probably the most complex part
of this driver due to the many combinations of crop, compose and scaling
on the input and output, and the blending that has to be done if
overlay support is enabled as well.
Signed-off-by: Hans Verkuil <hans.verkuil@cisco.com>
Signed-off-by: Mauro Carvalho Chehab <m.chehab@samsung.com>
|