device_add(9) [centos man page]

DEVICE_ADD(9)						   Device drivers infrastructure					     DEVICE_ADD(9)

NAME

       device_add - add device to device hierarchy.

SYNOPSIS

       int device_add(struct device * dev);

ARGUMENTS

       dev
	   device.

DESCRIPTION

       This is part 2 of device_register, though may be called separately _iff_ device_initialize has been called separately.

       This adds dev to the kobject hierarchy via kobject_add, adds it to the global and sibling lists for the device, then adds it to the other
       relevant subsystems of the driver model.

       Do not call this routine or device_register more than once for any device structure. The driver model core is not designed to work with
       devices that get unregistered and then spring back to life. (Among other things, it's very hard to guarantee that all references to the
       previous incarnation of dev have been dropped.) Allocate and register a fresh new struct device instead.

NOTE

       _Never_ directly free dev after calling this function, even if it returned an error! Always use put_device to give up your reference
       instead.

COPYRIGHT

Kernel Hackers Manual 3.10					     June 2014							     DEVICE_ADD(9)

STRUCT 
DEVICE_DRIVER(9) 				   Device drivers infrastructure				   STRUCT DEVICE_DRIVER(9)

NAME

       struct_device_driver - The basic device driver structure

SYNOPSIS

       struct device_driver {
	 const char * name;
	 struct bus_type * bus;
	 struct module * owner;
	 const char * mod_name;
	 bool suppress_bind_attrs;
	 const struct of_device_id * of_match_table;
	 const struct acpi_device_id * acpi_match_table;
	 int (* probe) (struct device *dev);
	 int (* remove) (struct device *dev);
	 void (* shutdown) (struct device *dev);
	 int (* suspend) (struct device *dev, pm_message_t state);
	 int (* resume) (struct device *dev);
	 const struct attribute_group ** groups;
	 const struct dev_pm_ops * pm;
	 struct driver_private * p;
       };

MEMBERS

       name
	   Name of the device driver.

       bus
	   The bus which the device of this driver belongs to.

       owner
	   The module owner.

       mod_name
	   Used for built-in modules.

       suppress_bind_attrs
	   Disables bind/unbind via sysfs.

       of_match_table
	   The open firmware table.

       acpi_match_table
	   The ACPI match table.

       probe
	   Called to query the existence of a specific device, whether this driver can work with it, and bind the driver to a specific device.

       remove
	   Called when the device is removed from the system to unbind a device from this driver.

       shutdown
	   Called at shut-down time to quiesce the device.

       suspend
	   Called to put the device to sleep mode. Usually to a low power state.

       resume
	   Called to bring a device from sleep mode.

       groups
	   Default attributes that get created by the driver core automatically.

       pm
	   Power management operations of the device which matched this driver.

       p
	   Driver core's private data, no one other than the driver core can touch this.

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.

COPYRIGHT

Kernel Hackers Manual 3.10					     June 2014						   STRUCT DEVICE_DRIVER(9)