Lines Matching +full:keep +full:- +full:power +full:- +full:in +full:- +full:suspend

11 be multiple devices in a system that a driver supports, struct
37          .suspend		= eepro100_suspend,
42 model because the bus they belong to has a bus-specific structure with
43 bus-specific fields that cannot be generalized.
48 completely bus-specific. Defining them as bus-specific entities would
49 sacrifice type-safety, so we keep bus-specific structures around.
51 Bus-specific drivers should include a generic struct device_driver in
52 the definition of the bus-specific driver. Like this::
59 A definition that included bus-specific fields would look like
69 		.suspend	= eepro100_suspend,
85 no bus-specific fields (i.e. don't have a bus-specific driver
89 Most drivers, however, will have a bus-specific structure and will
93 possible. Registration with the core initializes several fields in the
104 let the bus wrapper fill in the fields. For the callbacks, the bus can
105 define generic callbacks that forward the call to the bus-specific
108 This solution is intended to be only temporary. In order to get class
109 information in the driver, the drivers must be modified anyway. Since
133 When a driver is registered, a sysfs directory is created in its
134 bus's directory. In this directory, the driver can export an interface
136 e.g. toggling debugging output in the driver.
151 The probe() entry is called in task context, with the bus's rwsem locked
153 container_of() to convert "dev" to a bus-specific type, both in probe()
155 as pci_dev.resource[] or platform_device.resources, which is used in
156 addition to dev->platform_data to initialize the driver.
158 This callback holds the driver-specific logic to bind the driver to a
168 the driver did not bind to this device, in which case it should have
171 Optionally, probe() may return -EPROBE_DEFER if the driver depends on
175 must defer, it should return -EPROBE_DEFER as early as possible to
180       -EPROBE_DEFER must not be returned if probe() has already created
182       in a cleanup path. If -EPROBE_DEFER is returned after a child
183       device has been registered, it may result in an infinite loop of
198 point in time have already probed successfully, sync_state() is called right
205 postponed and reattempted in the future only when one or more consumers of the
213 driver might need to keep the device in the boot configuration until all the
222 whose addresses are remapped by the IOMMU) might need to keep their mappings
236 in other cases.
240 device; i.e. anything in the device's driver_data field.
243 it into a supported low-power state.
247 	int	(*suspend)	(struct device *dev, pm_message_t state);
249 suspend is called to put the device in a low power state.
255 Resume is used to bring a device back from a low power state.