总线设备驱动学习总结.docVIP

总线设备驱动学习总结 对于struct device 、struct device { struct klist klist_children; struct klist_node knode_parent; /* node in sibling list */ struct klist_node knode_driver; struct klist_node knode_bus; struct device *parent; struct kobject kobj; char bus_id[BUS_ID_SIZE]; /* position on parent bus */ unsigned uevent_suppress:1; const char *init_name; /* initial name of the device */ struct device_type *type; struct semaphore sem; /* semaphore to synchronize calls to * its driver. */ struct bus_type *bus; /* type of bus device is on */ struct device_driver *driver; /* which driver has allocated this device */ void *driver_data; /* data private to the driver */ void *platform_data; /* Platform specific data, device core doesnt touch it */ struct dev_pm_info power; #ifdef CONFIG_NUMA int numa_node; /* NUMA node this device is close to */ #endif u64 *dma_mask; /* dma mask (if dmaable device) */ u64 coherent_dma_mask;/* Like dma_mask, but for alloc_coherent mappings as not all hardware supports 64 bit addresses for consistent allocations such descriptors. */ struct device_dma_parameters *dma_parms; struct list_head dma_pools; /* dma pools (if dmable) */ struct dma_coherent_mem *dma_mem; /* internal for coherent mem override */ /* arch specific additions */ struct dev_archdata archdata; dev_t devt; /* dev_t, creates the sysfs dev */ spinlock_t devres_lock; struct list_head devres_head; struct klist_node knode_class; struct class *class; struct attribute_group **groups; /* optional groups */ void (*release)(struct device *dev); }; 当我们调用int device_register(struct device *dev)的时候便会在/sys/devices/目录下面生成一个对应的目录，例如图1我们注册我们的设备 图1：注册设备ldd0 然后我们看在/sys/devices/目录下有什么东西生成，见图2： 图2：ldd0目录 当我们把设备挂载到总线的时候，见图3： 图3 当加载模块以后我们察看目录/sys/device,见图4和图5： 图4 图5 再看看总线下面的设备，见图6： 图6 PS：我们注册设备其实就是在 /sys/devices下创建相应的设备目录，将设备挂载到总线上其实就是在总线的目录devices下创建相应的连接文件，连接到 /sys/devices下，而 /sys/drivers