Porting OV2735 to IMX8MM

[Sean_Zhang]

  Hi, I am currently carrying out the porting work of the OV2735 camera module on the IMX8MM platform. Since the official hasn't adapted it, I downloaded the code of kernel version 6.1 from another platform (RK). After some efforts, I debugged the I2C communication successfully, but when I tried to operate the camera for shooting, the device node couldn't be found, and When I used the tools provided by V4L2 for detection, the following was found:

  As shown in the figure, I didn't find the camera node. This confused me. When I went back to study the officially adapted OV5640 camera, I found that the official has built its own framework for camera capture of the imx series, which is located in the path linux-imx/drivers/media/platform/mxc/capture, as shown in the following figure.

  May I ask whether my next porting work should focus on what this directory does and May I ask if the above figure specifies the flow of MIPI data? Do I need to perform the same operations as in ov5640_mipi_v2.c ? I hope to get some suggestions for the next porting work.

Best wishes

[RutvijTrivedi207]

you may try upstream driver from siliconsignals 
https://web.git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/log/?qt=author&q=siliconsign...
https://web.git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?id=448e76433fb75e1f7...

This may help.

--
BR
info@siliconsignals.io

[francis_guindon]

Hi @Sean_Zhang,

Could you share your dmesg logs and device tree?

Regards,
Francis Guindon

Embedded SW Engineer at RidgeRun
Contact us: support@ridgerun.com
Developers wiki: https://developer.ridgerun.com/
Website: http://www.ridgerun.com/

[Sean_Zhang]

  Certainly, I'd be glad to. Below is my device tree configuration (imx8mm-evk.dtsi), which was adapted from the official OV5640 setup.

  Next is kernel print about 0v2735.

    Regarding my previous question, should I shift the focus of my research to the official framework: mxc?

Best wishes.

[francis_guindon]

From what I can see, your driver loads but it does not link with a media device (aka a /dev/videoX). I understand this linking does involve the mxc framework.

However before looking into implementing a change to the framework, I would look to see if there is a missing device tree configuration to help your driver link with a media device.

From your dmesg logs, I can see your driver's subdevice gets registered as m00__ov2735. Could you see what subdevices show up with ` ls /dev/* `?

Regards,
Francis Guindon

Embedded SW Engineer at RidgeRun
Contact us: support@ridgerun.com
Developers wiki: https://developer.ridgerun.com/
Website: http://www.ridgerun.com/