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- imx7-media-csi: Restrict the supported formats list to the SoC version. 32 33 The imx7 CSI bridge can be configured to sample pixel components from the Rx 34 queue in single (8bpp) or double (16bpp) component modes. Image format 35 variants with different sample sizes (ie YUYV_2X8 vs YUYV_1X16) determine the 36 pixel components sampling size per each clock cycle and their packing mode 37 (see imx7_csi_configure() for details). 38 39 As the imx7 CSI bridge can be interfaced with different IP blocks depending on 40 the SoC model it is integrated on, the Rx queue sampling size should match 41 the size of the samples transferred by the transmitting IP block. 42 43 To avoid mis-configurations of the capture pipeline, the enumeration of the 44 supported formats should be restricted to match the pixel source transmitting 45 mode. 46 47 Example: i.MX8MM SoC integrates the CSI bridge with the Samsung CSIS CSI-2 48 receiver which operates in dual pixel sampling mode. The CSI bridge should 49 only expose the 1X16 formats variant which instructs it to operate in dual 50 pixel sampling mode. When the CSI bridge is instead integrated on an i.MX7, 51 which supports both serial and parallel input, it should expose both variants. 52 53 This currently only applies to YUYV formats, but other formats might need 54 to be handled in the same way. 55