Lines Matching +full:pcs +full:- +full:handle

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
62 Or, in common situations where the device is known not to be hot-pluggable,
86 As a rule, platform specific (and often board-specific) setup code will
102 a kernel for a specific target board.  Such board-specific kernels are
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
124 The only "good" reason for this is to handle older system designs which, like
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
139 using these calls except with such hotplug-deficient drivers::
152 You can use platform_device_register_simple() as a one-step call to allocate
163     * platform_device.id ... the device instance number, or else "-1"
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
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.)
213 0 is the platform device id. If the id is -1 then the dot and the
227 Compiled-in platform drivers making use of early_platform_init() are