RK3568平台 点亮imx586摄像头_imx586驱动

		};
	};
};

};

&csi2_dphy0_hw {
status = “okay”;
};

&mipi2_csi2 {
status = “okay”;

ports {
	#address-cells = <1>;
	#size-cells = <0>;

	port@0 {
		reg = <0>;
		#address-cells = <1>;
		#size-cells = <0>;

		mipi2_csi2_input: endpoint@1 {
			reg = <1>;
			remote-endpoint = <&csidphy0_out>;
		};
	};

	port@1 {
		reg = <1>;
		#address-cells = <1>;
		#size-cells = <0>;

		mipi2_csi2_output: endpoint@0 {
			reg = <0>;
			remote-endpoint = <&cif_mipi2_in0>;
		};
	};
};

};

&rkcif {
status = “okay”;
};

&rkcif_mipi_lvds2 {
status = “okay”;

port {
	cif_mipi2_in0: endpoint {
		remote-endpoint = <&mipi2_csi2_output>;
	};
};

};

&rkcif_mipi_lvds2_sditf {
status = “okay”;

port {
	mipi_lvds2_sditf: endpoint {
		remote-endpoint = <&isp0_vir0>;
	};
};

};

&rkcif_mmu {
status = “okay”;
};

&rkisp_unite {
status = “okay”;
};

&rkisp_unite_mmu {
status = “okay”;
};

&rkisp0_vir0 {
status = “okay”;
/* dual isp process image case
* other rkisp hw and virtual nodes should disabled
*/
rockchip,hw = <&rkisp_unite>;
port {
#address-cells = <1>;
#size-cells = <0>;

	isp0_vir0: endpoint@0 {
		reg = <0>;
		remote-endpoint = <&mipi_lvds2_sditf>;
	};
};

};

## 三.驱动调试


把驱动代码和设备树文件添加进去后就可以开始调试了。


使用i2ctool工具查看i2c5，发现有2个新的设别：0x10,0x50，猜测其中一个是senser，另一个可能是sensor的马达地址，尝试修改sensor的地址为0x10或者0x50看imx586能不能进probe函数。


![](https://img-blog.csdnimg.cn/470044189736432ba6798df46778eac2.png)


当修改imx586的地址为ox10的时候，看imx586已经进了probe函数了。


![](https://img-blog.csdnimg.cn/80e4f2b7ad804c6dac7214788e68740a.png)


从log可以看出imx586已经进了probe函数，但是并没有识别到sensor。


这时候，需要确认mipi摄像头上的供电是否正常，时钟是否正常。


经确认是sensor的一路供电没有，供电正常后可以设别到sensor。


![](https://img-blog.csdnimg.cn/ee4bd99e224145578420f8638926cff3.png)


到了这一步，可以确认，iic设备已经可以设别到sensor了，并挂载在iic5上面。


## 四.查看拓扑

rk3588_t:/ # media-ctl -d /dev/media0 -p
Opening media device /dev/media0
Enumerating entities
Found 14 entities
Enumerating pads and links
Media controller API version 0.0.177

Media device information

driver rkcif
model rkcif-mipi-lvds2
serial
bus info
hw revision 0x0
driver version 0.0.177

Device topology

• entity 1: stream_cif_mipi_id0 (1 pad, 11 links)
  type Node subtype V4L
  device node name /dev/video0