Lines Matching full:driver

2 Driver Binding
5 Driver binding is the process of associating a device with a device
6 driver that can control it. Bus drivers have typically handled this
8 devices and the drivers. With generic device and device driver
19 for a driver, it is inserted at the end of this list. These are the
20 two events which trigger driver binding.
28 ID of the device must match one of the device IDs that the driver
31 algorithm, it is up to the bus driver to provide a callback to compare
32 a device against the IDs of a driver. The bus returns 1 if a match was
37 If a match is found, the device's driver field is set to the driver
38 and the driver's probe callback is called. This gives the driver a
47 class, and that is set in the driver's devclass field.
53 Driver  chapter
56 When a driver is attached to a device, the driver's probe() function is
57 called. Within probe(), the driver initializes the device and allocates
59 associated with the device object for as long as the driver remains bound
61 the device can be thought of as an instance of the driver.
69 A symlink is created in the driver's 'devices' directory that points
78 top-level directory. One can also be created to point to its driver's
85 The process is almost identical for when a new driver is added.
87 that already have a driver are skipped. All the devices are iterated
88 over, to bind as many devices as possible to the driver.
95 go to 0. When it does, the remove callback of the driver is called. It
96 is removed from the driver's list of devices and the reference count
97 of the driver is decremented. All symlinks between the two are removed.
99 When a driver is removed, the list of devices that it supports is
100 iterated over, and the driver's remove callback is called for each
104 Driver Override
107 Userspace may override the standard matching by writing a driver name to
108 a device's ``driver_override`` sysfs attribute.  When set, only a driver
114 does not automatically unbind the device from its current driver or
115 make any attempt to load the specified driver.
125 When the flag is set, the driver core automatically creates the
143 the given driver, 0 if the override is set but does not match, or < 0 if