Loading...
- The Frame Interval Monitor could be exported to v4l2-core for general use. - The CSI subdevice parses its nearest upstream neighbor's device-tree bus config in order to setup the CSI. Laurent Pinchart argues that instead the CSI subdev should call its neighbor's g_mbus_config op (which should be propagated if necessary) to get this info. However Hans Verkuil is planning to remove the g_mbus_config op. For now this driver uses the parsed DT bus config method until this issue is resolved. 2020-06: g_mbus has been removed in favour of the get_mbus_config pad operation which should be used to avoid parsing the remote endpoint configuration. - This media driver supports inheriting V4L2 controls to the video capture devices, from the subdevices in the capture device's pipeline. The controls for each capture device are updated in the link_notify callback when the pipeline is modified. This feature should be removed, userspace should use the subdev-based userspace API instead. - Similarly to the legacy control handling, legacy format handling where formats on the video nodes are influenced by the active format of the connected subdev should be removed. - i.MX7: all of the above, since it uses the imx media core - i.MX7: use Frame Interval Monitor |