2 - The Frame Interval Monitor could be exported to v4l2-core for
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
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
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. It should be
21 decided whether this feature is useful enough to make it generally
22 available by exporting to v4l2-core.
24 - i.MX7: all of the above, since it uses the imx media core
26 - i.MX7: use Frame Interval Monitor
28 - i.MX7: runtime testing with parallel sensor, links setup and streaming
30 - i.MX7: runtime testing with different formats, for the time only 10-bit bayer