Lines Matching full:drivers

2 Platform Devices and Drivers
35 Platform drivers
37 Platform drivers follow the standard driver model convention, where
38 discovery/enumeration is handled outside the drivers, and drivers
58 Platform drivers register themselves the normal way::
69 Kernel modules can be composed of several platform drivers. The platform core
70 provides helpers to register and unregister an array of drivers::
72 	int __platform_register_drivers(struct platform_driver * const *drivers,
74 	void platform_unregister_drivers(struct platform_driver * const *drivers,
77 If one of the drivers fails to register, all drivers registered up to that
81 	#define platform_register_drivers(drivers, count)
116 Legacy Drivers:  Device Probing
118 Some drivers are not fully converted to the driver model, because they take
120 leaving that for system infrastructure.  Such drivers can't be hotplugged
134 outside the driver.  This will usually be cleanup, since such drivers
138 None the less, there are some APIs to support such legacy drivers.  Avoid
139 using these calls except with such hotplug-deficient drivers::
176     - Whenever a device is registered, the drivers for that bus are
181       unbound devices on that bus are checked for matches.  Drivers
190 Early Platform Devices and Drivers
193 drivers early on during the system boot. The code is built on top of the
203 at this point will later on be matched against early platform drivers.
216 3. Installing early platform drivers belonging to a certain class
219 platform drivers belonging to a certain class using the function
227 Compiled-in platform drivers making use of early_platform_init() are
231 5. Probing of early platform drivers belonging to a certain class
235 registered early platform drivers. Matched devices will get probed().