Lines Matching +full:platform +full:- +full:name
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
27 const char *name;
35 Platform drivers
37 Platform drivers follow the standard driver model convention, where
55 actually exists; sometimes platform setup code can't be sure. The probing
58 Platform drivers register themselves the normal way::
62 Or, in common situations where the device is known not to be hot-pluggable,
69 Kernel modules can be composed of several platform drivers. The platform core
86 As a rule, platform specific (and often board-specific) setup code will
87 register platform devices::
102 a kernel for a specific target board. Such board-specific kernels are
105 In many cases, the memory and IRQ resources associated with the platform
110 Embedded systems frequently need one or more clocks for platform devices,
113 calls to clk_get(&pdev->dev, clock_name) return them as needed.
119 on a non-driver role: the driver registers its platform device, rather than
125 original IBM PCs, rely on error-prone "probe-the-hardware" models for hardware
127 bus-level support for dynamic configuration (PCI, USB), or device tables
136 were created by PNP or by platform device setup.
139 using these calls except with such hotplug-deficient drivers::
142 const char *name, int id);
149 const char *name, int id,
152 You can use platform_device_register_simple() as a one-step call to allocate
158 The platform_device.dev.bus_id is the canonical name for the devices.
161 * platform_device.name ... which is also used to for driver matching.
163 * platform_device.id ... the device instance number, or else "-1"
166 These are concatenated, so name/id "serial"/0 indicates bus_id "serial.0", and
168 named "serial". While "my_rtc"/-1 would be bus_id "my_rtc" (no instance id)
176 - Whenever a device is registered, the drivers for that bus are
177 checked for matches. Platform devices should be registered very
180 - When a driver is registered using platform_driver_register(), all
184 - Registering a driver using platform_driver_probe() works just like
187 this interface is only for use with non-hotpluggable devices.)
190 Early Platform Devices and Drivers
192 The early platform interfaces provide platform data to platform device
198 1. Registering early platform device data
200 The architecture code registers platform device data using the function
203 at this point will later on be matched against early platform drivers.
209 User specified early platform devices will be registered at this point.
212 the class string, "serial" is the name of the platform driver and
213 0 is the platform device id. If the id is -1 then the dot and the
216 3. Installing early platform drivers belonging to a certain class
219 platform drivers belonging to a certain class using the function
225 4. Early platform driver registration
227 Compiled-in platform drivers making use of early_platform_init() are
231 5. Probing of early platform drivers belonging to a certain class
234 registered early platform devices associated with a certain class with
235 registered early platform drivers. Matched devices will get probed().
239 6. Inside the early platform driver probe()
244 it is called at early platform device or at the regular platform device