Lines Matching refs:driver

11 be multiple devices in a system that a driver supports, struct
12 device_driver represents the driver as a whole (not a particular
18 The driver must initialize at least the name and bus fields. It should
28 driver. This declaration is hypothetical only; it relies on the driver
45 The most common example of this are device ID structures. A driver
52 the definition of the bus-specific driver. Like this:
56        struct device_driver	  driver;
60 (using the eepro100 driver again):
64        .driver	       = {
82 The driver registers the structure on startup. For drivers that have
83 no bus-specific fields (i.e. don't have a bus-specific driver
90 It is important that drivers register their driver structure as early as
94 used by the device model core or the bus driver.
107 information in the driver, the drivers must be modified anyway. Since
122 the driver. The LDM core provides a helper function to operate on all
123 the devices a driver controls. This helper locks the driver on each
131 When a driver is registered, a sysfs directory is created in its
132 bus's directory. In this directory, the driver can export an interface
133 to userspace to control operation of the driver on a global basis;
134 e.g. toggling debugging output in the driver.
148 and the driver partially bound to the device.  Drivers commonly use
152 addition to dev->platform_data to initialize the driver.
154 This callback holds the driver-specific logic to bind the driver to a
156 it's a version the driver can handle, that driver data structures can
159 When the driver has successfully bound itself to that device, then probe()
160 returns zero and the driver model code will finish its part of binding
161 the driver to that device.
163 A driver's probe() may return a negative errno value to indicate that
164 the driver did not bind to this device, in which case it should have
169 remove is called to unbind a driver from a device. This may be
171 driver module is being unloaded, during a reboot sequence, or
174 It is up to the driver to determine if the device is present or
194         ssize_t (*show)(struct device_driver *driver, char *buf);
211 driver's directory using: