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
69 As a rule, platform specific (and often board-specific) setup code will
70 register platform devices:
88 In many cases, the memory and IRQ resources associated with the platform
93 Embedded systems frequently need one or more clocks for platform devices,
102 on a non-driver role:  the driver registers its platform device, rather than
119 were created by PNP or by platform device setup.
175 The early platform interfaces provide platform data to platform device
181 1. Registering early platform device data
183 The architecture code registers platform device data using the function
186 at this point will later on be matched against early platform drivers.
192 User specified early platform devices will be registered at this point.
195 the class string, "serial" is the name of the platform driver and
196 0 is the platform device id. If the id is -1 then the dot and the
199 3. Installing early platform drivers belonging to a certain class
202 platform drivers belonging to a certain class using the function
208 4. Early platform driver registration
210 Compiled-in platform drivers making use of early_platform_init() are
214 5. Probing of early platform drivers belonging to a certain class
217 registered early platform devices associated with a certain class with
218 registered early platform drivers. Matched devices will get probed().
222 6. Inside the early platform driver probe()
227 it is called at early platform device or at the regular platform device