Checking OV5693's MIPI CSI-2 data in Jetson TX2 Do I need to communicate with I2C?

Hi.
I saw the image of the OV5693 sensor on Jetson TX2.
I am analyzing the principle of running the OV5693 on Jetson TX2.

Device-Tree: tegra186-camera-e3326-a00.dtsi
Driver: ov5693.c

I have confirmed that I2C communication is used in Device-Tree.

i2c@3180000 {
		ov5693_c@36 {
			compatible = "nvidia,ov5693";
			/* I2C device address */
			reg = <0x36>;

			/* V4L2 device node location */
			devnode = "video0";

			/* Physical dimensions of sensor */
			physical_w = "3.674";
			physical_h = "2.738";

			/* Define any required hw resources needed by driver */
			/* ie. clocks, io pins, power sources */
			avdd-reg = "vana";
			iovdd-reg = "vif";

			/* Sensor output flip settings */
			vertical-flip = "true";

                        ,,,,,
modules {
			module0 {
				badge = "e3326_front_P5V27C";
				position = "rear";
				orientation = "1";
				drivernode0 {
					/* Declare PCL support driver (classically known as guid)  */
					pcl_id = "v4l2_sensor";
					/* Driver v4l2 device name */
					devname = "ov5693 2-0036";
					/* Declare the device-tree hierarchy to driver instance */
					proc-device-tree = "/proc/device-tree/i2c@3180000/ov5693_c@36";
				};
				drivernode1 {
					/* Declare PCL support driver (classically known as guid)  */
					pcl_id = "v4l2_lens";
					proc-device-tree = "/proc/device-tree/e3326_lens_ov5693@P5V27C/";
				};
			};
		};

I want to check the OV5693’s MIPI CSI-2 image data without I2C communication by modifying Device-Tree or Dirver.

Is this possible?

@kangil86
What’s your use case for this.
For ov5693 it’s impossible to get image without i2c command.

@ShaneCCC

Hi.

I made MIPI CSI-2 data with an FPGA board.
I sent the MIPI CIS-2 data to the Jetson TX2 board.
But I did not get any data from Jetson TX2.
I tried to use Direct V4L2 Interface .

I think the problem is caused by not setting up the V4L2 sensor driver and Device Tree in the kernel.
I would like to modify the OV5693’s V4L2 sensor driver and Device Tree in the kernel, which is the onboard camera used in the Jetson TX2.

I made MIPI CSI-2 data with an FPGA board.
The MIPI CSI-2 data does not require I2C communication.

I tried to get the video by removing the I2C communication from the OV5693’s V4L2 sensor driver and Device Tree in the kernel.
I wanted to check the MIPI CSI-2 data on the FPGA board in the modified form.

ShaneCCC What do you mean if I do not use I2C communication in Jetson TX2, I can not check the OV5693’s MIPI CSI-2 data?

If so, I need to create a V4L2 sensor driver and a Device Tree in the kernel of the data I make with the FPGA. Can you tell me your opinion?

It’s ok without i2c communication if your device don’t need it. You still can declare it like ov5693 and make the i2c accessing as dummy function.

@ShaneCCC

I am still not able to modify the V4L2 sensor driver and Device Tree in the kernel.

For example, how can I modify the OV5693 to receive MIPI CSI-2 image data without i2C communication?

Is there a simple example for that?

@kangil86
There’s no this kind of sample code. As I said you can reference to ov5693 and remove all of the ic2 read/write code.

@ShaneCCC

Device-Tree: tegra186-camera-e3326-a00.dtsi
Driver: ov5693.c

modules {
			module0 {
				badge = "e3326_front_P5V27C";
				position = "rear";
				orientation = "1";
				drivernode0 {
					/* Declare PCL support driver (classically known as guid)  */
					pcl_id = "v4l2_sensor";
					/* Driver v4l2 device name */
					devname = "ov5693 2-0036";
					/* Declare the device-tree hierarchy to driver instance */
					proc-device-tree = "/proc/device-tree/i2c@3180000/ov5693_c@36";
				};
				drivernode1 {
					/* Declare PCL support driver (classically known as guid)  */
					pcl_id = "v4l2_lens";
					proc-device-tree = "/proc/device-tree/e3326_lens_ov5693@P5V27C/";
				};
			};
		};

I am reviewing the Device-Tree and Driver files above.

Is the proc-device-tree on i2c read / write code correct?
How do I delete this and make it a dummy?

Does the proc-device-tree above use only the GPIO pins of the OV5693?
Does MIPI CSI-2 data and proc-device-tree matter?

The i2c communication code is in the driver …/drivers/media/i2c/ov5693.c