struct_bus_type(9) [centos man page]

STRUCT 
BUS_TYPE(9)					   Device drivers infrastructure					STRUCT BUS_TYPE(9)

NAME

       struct_bus_type - The bus type of the device

SYNOPSIS

       struct bus_type {
	 const char * name;
	 const char * dev_name;
	 struct device * dev_root;
	 struct bus_attribute * bus_attrs;
	 struct device_attribute * dev_attrs;
	 struct driver_attribute * drv_attrs;
	 const struct attribute_group ** bus_groups;
	 const struct attribute_group ** dev_groups;
	 const struct attribute_group ** drv_groups;
	 int (* match) (struct device *dev, struct device_driver *drv);
	 int (* uevent) (struct device *dev, struct kobj_uevent_env *env);
	 int (* probe) (struct device *dev);
	 int (* remove) (struct device *dev);
	 void (* shutdown) (struct device *dev);
	 int (* online) (struct device *dev);
	 int (* offline) (struct device *dev);
	 int (* suspend) (struct device *dev, pm_message_t state);
	 int (* resume) (struct device *dev);
	 const struct dev_pm_ops * pm;
	 struct iommu_ops * iommu_ops;
	 struct subsys_private * p;
       };

MEMBERS

       name
	   The name of the bus.

       dev_name
	   Used for subsystems to enumerate devices like ("foou", dev->id).

       dev_root
	   Default device to use as the parent.

       bus_attrs
	   Default attributes of the bus.

       dev_attrs
	   Default attributes of the devices on the bus.

       drv_attrs
	   Default attributes of the device drivers on the bus.

       bus_groups
	   Default attributes of the bus.

       dev_groups
	   Default attributes of the devices on the bus.

       drv_groups
	   Default attributes of the device drivers on the bus.

       match
	   Called, perhaps multiple times, whenever a new device or driver is added for this bus. It should return a nonzero value if the given
	   device can be handled by the given driver.

       uevent
	   Called when a device is added, removed, or a few other things that generate uevents to add the environment variables.

       probe
	   Called when a new device or driver add to this bus, and callback the specific driver's probe to initial the matched device.

       remove
	   Called when a device removed from this bus.

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

       online
	   Called to put the device back online (after offlining it).

       offline
	   Called to put the device offline for hot-removal. May fail.

       suspend
	   Called when a device on this bus wants to go to sleep mode.

       resume
	   Called to bring a device on this bus out of sleep mode.

       pm
	   Power management operations of this bus, callback the specific device driver's pm-ops.

       iommu_ops
	   IOMMU specific operations for this bus, used to attach IOMMU driver implementations to a bus and allow the driver to do bus-specific
	   setup

       p
	   The private data of the driver core, only the driver core can touch this.

DESCRIPTION

       A bus is a channel between the processor and one or more devices. For the purposes of the device model, all devices are connected via a
       bus, even if it is an internal, virtual, "platform" bus. Buses can plug into each other. A USB controller is usually a PCI device, for
       example. The device model represents the actual connections between buses and the devices they control. A bus is represented by the
       bus_type structure. It contains the name, the default attributes, the bus' methods, PM operations, and the driver core's private data.

COPYRIGHT

Kernel Hackers Manual 3.10					     June 2014							STRUCT BUS_TYPE(9)

Check Out this Related Man Page

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)

Linux and UNIX Man Pages

struct_bus_type(9) [centos man page]

Check Out this Related Man Page