struct_bus_type - The bus type of the device
2. SYNOPSIS ▲
*dev, pm_message_t state);
3. MEMBERS ▲
The name of the bus.
Used for subsystems to enumerate devices like (« foou », dev->id).
Default device to use as the parent.
Default attributes of the bus.
Default attributes of the devices on the bus.
Default attributes of the device drivers on the bus.
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.
Called when a device is added, removed, or a few other things that generate uevents to add the environment variables.
Called when a new device or driver add to this bus, and callback the specific driverAqs probe to initial the matched device.
Called when a device removed from this bus.
Called at shut-down time to quiesce the device.
Called when a device on this bus wants to go to sleep mode.
Called to bring a device on this bus out of sleep mode.
Power management operations of this bus, callback the specific device driverAqs pm-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
The private data of the driver core, only the driver core can touch this.
4. 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 busAq methods, PM operations, and the driver coreAqs private data.
5. COPYRIGHT ▲