v4l2: use opened device caps instead of physical device ones
authorReynaldo H. Verdejo Pinochet <reynaldo@osg.samsung.com>
Sat, 2 Jul 2016 08:56:07 +0000 (01:56 -0700)
committerNicolas Dufresne <nicolas.dufresne@collabora.com>
Thu, 7 Jul 2016 21:46:06 +0000 (17:46 -0400)
commit4b16b16aaf79c0556b06f04d192fe00a17ab2c24
tree308472d9a62042ddf4a92fb1dc8de5397689264c
parentf0ba7a5ca49840d07aebc539a3153894c4d66c3c
v4l2: use opened device caps instead of physical device ones

The same physical device can export multiple devices. In
this case, the capabilities field now contains a union of
all caps available from all exported V4L2 devices alongside
a V4L2_CAP_DEVICE_CAPS flag that should be used to decide
what capabilities to consider. In our case, we need the
ones from the exported device we are using.

https://bugzilla.gnome.org/show_bug.cgi?id=768195
sys/v4l2/gstv4l2.c
sys/v4l2/gstv4l2bufferpool.c
sys/v4l2/gstv4l2deviceprovider.c
sys/v4l2/gstv4l2object.c
sys/v4l2/gstv4l2object.h
sys/v4l2/gstv4l2radio.c
sys/v4l2/gstv4l2sink.c
sys/v4l2/v4l2_calls.c