Lines Matching refs:platform

4 platform bus:  platform_device, and platform_driver.  This pseudo-bus
52 actually exists; sometimes platform setup code can't be sure.  The probing
66 Kernel modules can be composed of several platform drivers. The platform core
83 As a rule, platform specific (and often board-specific) setup code will
84 register platform devices:
102 In many cases, the memory and IRQ resources associated with the platform
107 Embedded systems frequently need one or more clocks for platform devices,
116 on a non-driver role:  the driver registers its platform device, rather than
133 were created by PNP or by platform device setup.
189 The early platform interfaces provide platform data to platform device
195 1. Registering early platform device data
197 The architecture code registers platform device data using the function
200 at this point will later on be matched against early platform drivers.
206 User specified early platform devices will be registered at this point.
209 the class string, "serial" is the name of the platform driver and
210 0 is the platform device id. If the id is -1 then the dot and the
213 3. Installing early platform drivers belonging to a certain class
216 platform drivers belonging to a certain class using the function
222 4. Early platform driver registration
224 Compiled-in platform drivers making use of early_platform_init() are
228 5. Probing of early platform drivers belonging to a certain class
231 registered early platform devices associated with a certain class with
232 registered early platform drivers. Matched devices will get probed().
236 6. Inside the early platform driver probe()
241 it is called at early platform device or at the regular platform device