Linux设备模型(文档翻译)_(整理文档).docxVIP

Linux 内核文档翻译 - driver-model/bus.txtBus Types 总线类型Definition定义~~~~~~~~~~See the kerneldoc for the struct bus_type.intbus_register(struct bus_type * bus);Declaration声明~~~~~~~~~~~Each bus type in the kernel (PCI, USB, etc) should declare one static object of this type. They must initialize the name field, and may optionally initialize the match callback.内核中每个总线类型（PCI、USB 等等）都应该声明一个此类型的静态对象。它们必须初始化该对象的name 字段，然后可选的初始化match 回调函数。structbus_typepci_bus_type = { .name = pci, .match = pci_bus_match,};The structure should be exported to drivers in a header file:这个结构体应该在头文件中向驱动程序导出：extern struct bus_typepci_bus_type;Registration注册~~~~~~~~~~~~When a bus driver is initialized, it calls bus_register. This initializes the rest of the fields in the bus object and inserts it into a global list of bus types. Once the bus object is registered, the fields in it are usable by the bus driver. 当初始化一个总线驱动时，将会调用bus_register。这时这个总线对象剩下的字段将被初始化，然后这个对象会被插入到总线类型的一个全局列表里去。一旦完成一个总线对象的注册，那么对于总线驱动来说它里面的字段就已经可用了。Callbacks回调函数~~~~~~~~~match(): Attaching Drivers to Devicesmatch()：给设备加载驱动~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~The format of device ID structures and the semantics for comparing them are inherently bus-specific. Drivers typically declare an array of device IDs of devices they support that reside in a bus-specific driver structure. 设备 ID 的结构和比较这些 ID 的语义本质上讲都是总线定制的。驱动通常会定义一个它所支持的设备 ID 的数组，并将这个数组驻留在总线定制的驱动结构中。The purpose of the match callback is provide the bus an opportunity to determine if a particular driver supports a particular device by comparing the device IDs the driver supports with the device ID of a particular device, without sacrificing bus-specific functionality or type-safety. 回调函数 match 的目的就是在不牺牲总线定制功能或类型安全的情况下，通过比较驱动所支持的 ID 与特定设备的 ID，给总线提供一个确定特定驱动是否支持特定设备的机会。When a driver is registered with the bus, the buss list of devices is iterated over, and the match callback is called for each device that does not have a driver associated with it. 当一个驱动注册到总线后，将会遍历总线的设备列表，然后会为每个还没有和任何