Hi everybody, These patches implement support for the media controller API in the uvcvideo driver. UVC devices report their internal topology to the host through USB descriptors, and the topology is then further exported to userspace through the MC API. Note that all links are immutable, as UVC doesn't allow runtime links configuration. Furthermore the V4L2 subdev pad-level API isn't used, formats are controlled through V4L2 device nodes only. The MC API is thus totally optional, non MC-aware applications won't notice any change in the driver behaviour. As the MC API is marked as experimental, should I make MC support conditionally compilable, and add a configuration menu entry to enable/disable it ? Laurent Pinchart (4): uvcvideo: Register a v4l2_device uvcvideo: Register subdevices for each entity uvcvideo: Connect video devices to media entities v4l: Release module if subdev registration fails drivers/media/video/uvc/Makefile | 2 +- drivers/media/video/uvc/uvc_driver.c | 58 +++++++++++++++-- drivers/media/video/uvc/uvc_entity.c | 118 ++++++++++++++++++++++++++++++++++ drivers/media/video/uvc/uvcvideo.h | 18 +++++ drivers/media/video/v4l2-device.c | 5 +- 5 files changed, 192 insertions(+), 9 deletions(-) create mode 100644 drivers/media/video/uvc/uvc_entity.c -- Regards, Laurent Pinchart -- To unsubscribe from this list: send the line "unsubscribe linux-media" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
