1 2- The Frame Interval Monitor could be exported to v4l2-core for 3 general use. 4 5- The CSI subdevice parses its nearest upstream neighbor's device-tree 6 bus config in order to setup the CSI. Laurent Pinchart argues that 7 instead the CSI subdev should call its neighbor's g_mbus_config op 8 (which should be propagated if necessary) to get this info. However 9 Hans Verkuil is planning to remove the g_mbus_config op. For now this 10 driver uses the parsed DT bus config method until this issue is 11 resolved. 12 13 2020-06: g_mbus has been removed in favour of the get_mbus_config pad 14 operation which should be used to avoid parsing the remote endpoint 15 configuration. 16 17- This media driver supports inheriting V4L2 controls to the 18 video capture devices, from the subdevices in the capture device's 19 pipeline. The controls for each capture device are updated in the 20 link_notify callback when the pipeline is modified. This feature should be 21 removed, userspace should use the subdev-based userspace API instead. 22 23- Similarly to the legacy control handling, legacy format handling where 24 formats on the video nodes are influenced by the active format of the 25 connected subdev should be removed. 26 27- i.MX7: all of the above, since it uses the imx media core 28 29- i.MX7: use Frame Interval Monitor 30 31- i.MX7: runtime testing with parallel sensor, links setup and streaming 32 33- i.MX7: runtime testing with different formats, for the time only 10-bit bayer 34 is tested 35