Lines Matching +full:platform +full:- +full:specific

2 Platform Devices and Drivers
6 platform bus:  platform_device, and platform_driver.  This pseudo-bus
8 like those used to integrate peripherals on many system-on-chip
13 Platform devices
15 Platform devices are devices that typically appear as autonomous
16 entities in the system. This includes legacy port-based devices and
18 into system-on-chip platforms.  What they usually have in common
23 Platform devices are given a name, used in driver binding, and a
35 Platform drivers
37 Platform drivers follow the standard driver model convention, where
54 actually exists; sometimes platform setup code can't be sure.  The probing
57 Platform drivers register themselves the normal way::
61 Or, in common situations where the device is known not to be hot-pluggable,
68 Kernel modules can be composed of several platform drivers. The platform core
85 As a rule, platform specific (and often board-specific) setup code will
86 register platform devices::
101 a kernel for a specific target board.  Such board-specific kernels are
104 In many cases, the memory and IRQ resources associated with the platform
109 Embedded systems frequently need one or more clocks for platform devices,
112 calls to clk_get(&pdev->dev, clock_name) return them as needed.
118 on a non-driver role:  the driver registers its platform device, rather than
124 original IBM PCs, rely on error-prone "probe-the-hardware" models for hardware
126 bus-level support for dynamic configuration (PCI, USB), or device tables
135 were created by PNP or by platform device setup.
138 using these calls except with such hotplug-deficient drivers::
151 You can use platform_device_register_simple() as a one-step call to allocate
162     * platform_device.id ... the device instance number, or else "-1"
167 named "serial".  While "my_rtc"/-1 would be bus_id "my_rtc" (no instance id)
175     - Whenever a device is registered, the drivers for that bus are
176       checked for matches.  Platform devices should be registered very
179     - When a driver is registered using platform_driver_register(), all
183     - Registering a driver using platform_driver_probe() works just like
186       this interface is only for use with non-hotpluggable devices.)
189 Early Platform Devices and Drivers
191 The early platform interfaces provide platform data to platform device
197 1. Registering early platform device data
199 The architecture code registers platform device data using the function
202 at this point will later on be matched against early platform drivers.
208 User specified early platform devices will be registered at this point.
211 the class string, "serial" is the name of the platform driver and
212 0 is the platform device id. If the id is -1 then the dot and the
215 3. Installing early platform drivers belonging to a certain class
218 platform drivers belonging to a certain class using the function
224 4. Early platform driver registration
226 Compiled-in platform drivers making use of early_platform_init() are
230 5. Probing of early platform drivers belonging to a certain class
233 registered early platform devices associated with a certain class with
234 registered early platform drivers. Matched devices will get probed().
238 6. Inside the early platform driver probe()
243 it is called at early platform device or at the regular platform device