一、问题提出
i2c的设备树和驱动是如何匹配以及何时调用probe的?粉丝手里的I2C外设是ov5640,一个摄像头。
二、问题分析
设备树信息如下:
ov5640: ov5640@3c {
compatible = "ovti,ov5640";
reg = <0x3c>;
pinctrl-names = "default";
pinctrl-0 = &csi_pwn_rst>;
clocks = ;
clock-names = "csi_mclk";
pwn-gpios = 4 1>;
rst-gpios = 2 0>;
csi_id = <0>;
mclk = <24000000>;
mclk_source = <0>;
status = "okay";
port {
ov5640_ep: endpoint {
remote-endpoint = ;
};
};
};
驱动最重要的结构体如下:
要搞懂这个问题,我们需要有一些基础知识:
1.内核如何维护i2c总线
Linux内核维护很多总线,platform、usb、i2c、spi、pci等等,这个总线的架构在内核中都支持的很完善,内核通过以下结构体来维护总线:
struct bus_type {
const char *name;
const char *dev_name;
struct device *dev_root;
struct device_attribute *dev_attrs; /* use dev_groups instead */
const struct attribute_group **bus_groups;
const struct attribute_group **dev_groups;
const struct attribute_group **drv_groups;
int (*match)(struct device *dev, struct device_driver *drv);
int (*uevent)(struct device *dev, struct kobj_uevent_env *env);
int (*probe)(struct device *dev);
int (*remove)(struct device *dev);