driver-api/driver-model/platform.rst

6 platform bus:  platform_device, and platform_driver.  This pseudo-bus
8 like those used to integrate peripherals on many system-on-chip
16 entities in the system. This includes legacy port-based devices and
18 into system-on-chip platforms.  What they usually have in common
39 provide probe() and remove() methods.  They support power management
61 Or, in common situations where the device is known not to be hot-pluggable,
85 As a rule, platform specific (and often board-specific) setup code will
101 a kernel for a specific target board.  Such board-specific kernels are
110 which are normally kept off until they're actively needed (to save power).
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
132 please try to move the device enumeration to a more appropriate location,
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
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.)
212 0 is the platform device id. If the id is -1 then the dot and the
226 Compiled-in platform drivers making use of early_platform_init() are