aboutsummaryrefslogtreecommitdiffstats
path: root/Documentation/driver-model
diff options
context:
space:
mode:
Diffstat (limited to 'Documentation/driver-model')
-rw-r--r--Documentation/driver-model/platform.txt4
1 files changed, 2 insertions, 2 deletions
diff --git a/Documentation/driver-model/platform.txt b/Documentation/driver-model/platform.txt
index 9f0bc3bfd776..f7c9262b2dc8 100644
--- a/Documentation/driver-model/platform.txt
+++ b/Documentation/driver-model/platform.txt
@@ -66,7 +66,7 @@ runtime memory footprint:
66 66
67Device Enumeration 67Device Enumeration
68~~~~~~~~~~~~~~~~~~ 68~~~~~~~~~~~~~~~~~~
69As a rule, platform specific (and often board-specific) setup code wil 69As a rule, platform specific (and often board-specific) setup code will
70register platform devices: 70register platform devices:
71 71
72 int platform_device_register(struct platform_device *pdev); 72 int platform_device_register(struct platform_device *pdev);
@@ -106,7 +106,7 @@ It's built from two components:
106 * platform_device.id ... the device instance number, or else "-1" 106 * platform_device.id ... the device instance number, or else "-1"
107 to indicate there's only one. 107 to indicate there's only one.
108 108
109These are catenated, so name/id "serial"/0 indicates bus_id "serial.0", and 109These are concatenated, so name/id "serial"/0 indicates bus_id "serial.0", and
110"serial/3" indicates bus_id "serial.3"; both would use the platform_driver 110"serial/3" indicates bus_id "serial.3"; both would use the platform_driver
111named "serial". While "my_rtc"/-1 would be bus_id "my_rtc" (no instance id) 111named "serial". While "my_rtc"/-1 would be bus_id "my_rtc" (no instance id)
112and use the platform_driver called "my_rtc". 112and use the platform_driver called "my_rtc".