Lines Matching refs:drivers

33 Platform drivers
35 Platform drivers follow the standard driver model convention, where
36 discovery/enumeration is handled outside the drivers, and drivers
55 Platform drivers register themselves the normal way:
66 Kernel modules can be composed of several platform drivers. The platform core
67 provides helpers to register and unregister an array of drivers:
69 	int __platform_register_drivers(struct platform_driver * const *drivers,
71 	void platform_unregister_drivers(struct platform_driver * const *drivers,
74 If one of the drivers fails to register, all drivers registered up to that
78 	#define platform_register_driver(drivers, count)
115 Some drivers are not fully converted to the driver model, because they take
117 leaving that for system infrastructure.  Such drivers can't be hotplugged
131 outside the driver.  This will usually be cleanup, since such drivers
135 None the less, there are some APIs to support such legacy drivers.  Avoid
136 using these calls except with such hotplug-deficient drivers.
173     - Whenever a device is registered, the drivers for that bus are
190 drivers early on during the system boot. The code is built on top of the
200 at this point will later on be matched against early platform drivers.
213 3. Installing early platform drivers belonging to a certain class
216 platform drivers belonging to a certain class using the function
224 Compiled-in platform drivers making use of early_platform_init() are
228 5. Probing of early platform drivers belonging to a certain class
232 registered early platform drivers. Matched devices will get probed().