struct_device_driver - The basic device driver structure
2. SYNOPSIS ▲
*mod_name; bool suppress_bind_attrs;
*dev, pm_message_t state);
3. MEMBERS ▲
Name of the device driver.
The bus which the device of this driver belongs to.
The module owner.
Used for built-in modules.
Disables bind/unbind via sysfs.
The open firmware table.
The ACPI match table.
Called to query the existence of a specific device, whether this driver can work with it, and bind the driver to a specific device.
Called when the device is removed from the system to unbind a device from this driver.
Called at shut-down time to quiesce the device.
Called to put the device to sleep mode. Usually to a low power state.
Called to bring a device from sleep mode.
Default attributes that get created by the driver core automatically.
Power management operations of the device which matched this driver.
Driver coreAqs private data, no one other than the driver core can touch this.
4. DESCRIPTION ▲
The device driver-model tracks all of the drivers known to the system. The main reason for this tracking is to enable the driver core to match up drivers with new devices. Once drivers are known objects within the system, however, a number of other things become possible. Device drivers can export information and configuration variables that are independent of any specific device.
5. COPYRIGHT ▲