Lines Matching refs:that

11 be multiple devices in a system that a driver supports, struct
43 bus-specific fields that cannot be generalized. 
46 typically defines an array of device IDs that it supports. The format
59 A definition that included bus-specific fields would look like
82 The driver registers the structure on startup. For drivers that have
90 It is important that drivers register their driver structure as early as
103 define generic callbacks that forward the call to the bus-specific
109 complexity and code size, it is recommended that they are converted as
121 The devices field is a list of all the devices that have been bound to
155 given device.  That includes verifying that the device is present, that
156 it's a version the driver can handle, that driver data structures can
157 be allocated and initialized, and that any hardware can be initialized.
159 When the driver has successfully bound itself to that device, then probe()
161 the driver to that device.
163 A driver's probe() may return a negative errno value to indicate that
199 Drivers can declare attributes using a DRIVER_ATTR macro that works