aboutsummaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorRafael J. Wysocki <rafael.j.wysocki@intel.com>2017-02-20 09:28:13 -0500
committerJonathan Corbet <corbet@lwn.net>2017-02-20 18:40:46 -0500
commitbd8562626c8e170691d6457fe4e8dfb45607a48d (patch)
tree7f1dbbdeb0debd863a12f0292933c7feed9e1eb6
parente3941cd9f59d1d5508c29eb1712a732722885ee7 (diff)
docs / driver-api: Fix structure references in device_link.rst
The format of the structure references in device_link.rst is incorrect, because it doesn't cause proper references to the struct data types to be generated (for struct dev_pm_domain in particular). Fix that by using the :c:type:`struct name <name>` convention for encoding references to struct data types. Fixes: aad800403a87 (Documentation/core-api/device_link: Add initial documentation) Signed-off-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com> Signed-off-by: Jonathan Corbet <corbet@lwn.net>
-rw-r--r--Documentation/driver-api/device_link.rst18
1 files changed, 10 insertions, 8 deletions
diff --git a/Documentation/driver-api/device_link.rst b/Documentation/driver-api/device_link.rst
index 5f5713448703..70e328e16aad 100644
--- a/Documentation/driver-api/device_link.rst
+++ b/Documentation/driver-api/device_link.rst
@@ -1,3 +1,6 @@
1.. |struct dev_pm_domain| replace:: :c:type:`struct dev_pm_domain <dev_pm_domain>`
2.. |struct generic_pm_domain| replace:: :c:type:`struct generic_pm_domain <generic_pm_domain>`
3
1============ 4============
2Device links 5Device links
3============ 6============
@@ -120,12 +123,11 @@ Examples
120 is the same as if the MMU was the parent of the master device. 123 is the same as if the MMU was the parent of the master device.
121 124
122 The fact that both devices share the same power domain would normally 125 The fact that both devices share the same power domain would normally
123 suggest usage of a :c:type:`struct dev_pm_domain` or :c:type:`struct 126 suggest usage of a |struct dev_pm_domain| or |struct generic_pm_domain|,
124 generic_pm_domain`, however these are not independent devices that 127 however these are not independent devices that happen to share a power
125 happen to share a power switch, but rather the MMU device serves the 128 switch, but rather the MMU device serves the busmaster device and is
126 busmaster device and is useless without it. A device link creates a 129 useless without it. A device link creates a synthetic hierarchical
127 synthetic hierarchical relationship between the devices and is thus 130 relationship between the devices and is thus more apt.
128 more apt.
129 131
130* A Thunderbolt host controller comprises a number of PCIe hotplug ports 132* A Thunderbolt host controller comprises a number of PCIe hotplug ports
131 and an NHI device to manage the PCIe switch. On resume from system sleep, 133 and an NHI device to manage the PCIe switch. On resume from system sleep,
@@ -157,7 +159,7 @@ Examples
157Alternatives 159Alternatives
158============ 160============
159 161
160* A :c:type:`struct dev_pm_domain` can be used to override the bus, 162* A |struct dev_pm_domain| can be used to override the bus,
161 class or device type callbacks. It is intended for devices sharing 163 class or device type callbacks. It is intended for devices sharing
162 a single on/off switch, however it does not guarantee a specific 164 a single on/off switch, however it does not guarantee a specific
163 suspend/resume ordering, this needs to be implemented separately. 165 suspend/resume ordering, this needs to be implemented separately.
@@ -166,7 +168,7 @@ Alternatives
166 suspended. Furthermore it cannot be used to enforce a specific shutdown 168 suspended. Furthermore it cannot be used to enforce a specific shutdown
167 ordering or a driver presence dependency. 169 ordering or a driver presence dependency.
168 170
169* A :c:type:`struct generic_pm_domain` is a lot more heavyweight than a 171* A |struct generic_pm_domain| is a lot more heavyweight than a
170 device link and does not allow for shutdown ordering or driver presence 172 device link and does not allow for shutdown ordering or driver presence
171 dependencies. It also cannot be used on ACPI systems. 173 dependencies. It also cannot be used on ACPI systems.
172 174