linux内核部件分析(九)——设备驱动模型之device-driver.docx

前面我们分析了device、driver、bus三种类型，主要是三者的注册与注销，在sysfs中的目录与属性文件创建等内容。本节就来详细分析下，在设备注册到总线上时，总线是如何为其寻找对应的驱动的；在驱动注册到总线上时，总线又是如何为其寻找对应的设备的。?本节的实现代码集中在drivers/base/bus.c和drivers/base/dd.c中。先来回忆下，在device_register()-device_add()中，先是调用bus_add_device()添加device与bus间的联系，并添加bus为device定义的属性，然后会调用bus_probe_device()。bus_probe_device()会试图为已挂在总线上的该设备寻找对应的驱动。我们的故事就从这里开始。[cpp]?/qb_2008/article/details/6854086view plain/qb_2008/article/details/6854086copy/qb_2008/article/details/6854086print/qb_2008/article/details/6854086?/**??*?bus_probe_device?-?probe?drivers?for?a?new?device??*?@dev:?device?to?probe??*??*?-?Automatically?probe?for?a?driver?if?the?bus?allows?it.??*/?void?bus_probe_device(struct?device?*dev)??{???struct?bus_type?*bus?=?dev-bus;???int?ret;????if?(bus??bus-p-drivers_autoprobe)?{???ret?=?device_attach(dev);???WARN_ON(ret??0);???}??}??bus_probe_device()为总线上的设备寻找驱动。它先是检查bus-p-drivers_autoprobe，看是否允许自动探测。允许了才会调用device_attach()进行实际的寻找工作。说到bus-p-drivers_autoprobe这个变量，它是在bus_type_private中的，在调用bus_register()前都初始化不了，在bus_register()中自动定为1。所以，除非是用户空间通过drivers_autoprobe属性文件主动禁止，bus总是允许自动探测的，所有的bus都是如此。[cpp]?/qb_2008/article/details/6854086view plain/qb_2008/article/details/6854086copy/qb_2008/article/details/6854086print/qb_2008/article/details/6854086?/**??*?device_attach?-?try?to?attach?device?to?a?driver.??*?@dev:?device.??*??*?Walk?the?list?of?drivers?that?the?bus?has?and?call??*?driver_probe_device()?for?each?pair.?If?a?compatible??*?pair?is?found,?break?out?and?return.??*??*?Returns?1?if?the?device?was?bound?to?a?driver;??*?0?if?no?matching?driver?was?found;??*?-ENODEV?if?the?device?is?not?registered.??*??*?When?called?for?a?USB?interface,?@dev-parent-sem?must?be?held.??*/?int?device_attach(struct?device?*dev)??{???int?ret?=?0;????down(dev-sem);???if?(dev-driver)?{???ret?=?device_bind_driver(dev);???if?(ret?==?0)???ret?=?1;???else?{???dev-driver?=?NULL;???ret?=?0;???}???}?else?{???pm_runtime_get_noresume(dev);???ret?=?bus_for_each_drv(dev-bus,?NULL,?dev,?__device_attach);???pm_runti