Hi!
What are the differences in the general pipeline of ISP between Genio 510/700 and Genio 520/720?
For example, consider this DTS for IMX258 for Genio 720:
https://gitlab.com/mediatek/aiot/rity/meta-mediatek-bsp/-/blob/scarthgap/recipes-kernel/dtbo/v6/genio-720-evk/camera-imx258-dual-std.dts?ref_type=heads
It uses the standard kernel driver.
Now, Genio 700 (with similar camera, IMX214):
https://gitlab.com/mediatek/aiot/rity/meta-mediatek-bsp/-/blob/scarthgap/recipes-kernel/dtbo/v6/genio-700-evk/camera-imx214-csi1.dts?ref_type=heads
It uses custom mtk-camisp-driver. There is DTS for a different pipeline, but if I understand correctly, ISP is disabled for it. To integrate a new camera, a custom sensor driver is required (per documentation).
So my question is - how ISP works in newer generation? Does it require the custom drivers/interfaces for cameras like mtk-camisp-driver, or there is a different mechanism?
Hi @Andrii_Sokolovskyi,
The IoT Yocto v25.1 release for Genio 520/720 introduces support for pure data output via the V4L2 driver. This feature is primarily designed for sensors that do not require SoC-side ISP processing, such as YUV sensors with internal processing.
It also supports capturing raw Bayer data directly to DRAM, which corresponds to the camera-imx258-*-std.dts configuration you mentioned. This pipeline only requires kernel drivers for the SoC hardware and the sensor. The in-tree SoC drivers are located at: drivers/media/platform/mediatek/isp/isp_6s.
Please note that SoC-side ISP processing for Bayer raw sensors on Genio 520/720 is not supported in the IoT Yocto v25.1 release.
Thanks