1 2- Clean up and move the ov5642 subdev driver to drivers/media/i2c, or 3 merge support for OV5642 into drivers/media/i2c/ov5640.c, and create 4 the binding docs for it. 5 6- The Frame Interval Monitor could be exported to v4l2-core for 7 general use. 8 9- At driver load time, the device-tree node that is the original source 10 (the "sensor"), is parsed to record its media bus configuration, and 11 this info is required in imx-media-csi.c to setup the CSI. 12 Laurent Pinchart argues that instead the CSI subdev should call its 13 neighbor's g_mbus_config op (which should be propagated if necessary) 14 to get this info. However Hans Verkuil is planning to remove the 15 g_mbus_config op. For now this driver uses the parsed DT mbus config 16 method until this issue is resolved. 17 18- This media driver supports inheriting V4L2 controls to the 19 video capture devices, from the subdevices in the capture device's 20 pipeline. The controls for each capture device are updated in the 21 link_notify callback when the pipeline is modified. It should be 22 decided whether this feature is useful enough to make it generally 23 available by exporting to v4l2-core. 24