Lines Matching refs:driver

5 driver that can control it. Bus drivers have typically handled this
7 devices and the drivers. With generic device and device driver
18 for a driver, it is inserted at the end of this list. These are the
19 two events which trigger driver binding.
27 ID of the device must match one of the device IDs that the driver
30 algorithm, it is up to the bus driver to provide a callback to compare
31 a device against the IDs of a driver. The bus returns 1 if a match was
36 If a match is found, the device's driver field is set to the driver
37 and the driver's probe callback is called. This gives the driver a
46 class, and that is set in the driver's devclass field. 
55 When a driver is attached to a device, the device is inserted into the
56 driver's list of devices. 
65 A symlink is created in the driver's 'devices' directory that points
74 top-level directory. One can also be created to point to its driver's
81 The process is almost identical for when a new driver is added. 
83 that already have a driver are skipped. All the devices are iterated
84 over, to bind as many devices as possible to the driver.
91 go to 0. When it does, the remove callback of the driver is called. It
92 is removed from the driver's list of devices and the reference count
93 of the driver is decremented. All symlinks between the two are removed.
95 When a driver is removed, the list of devices that it supports is
96 iterated over, and the driver's remove callback is called for each