DocBook/drm: Refer to the domain-setting function as a device-specific ioctl

Signed-off-by: Michael Witten <mfwitten@gmail.com>
Acked-by: Jesse Barnes <jbarnes@virtuousgeek.org>
Signed-off-by: Randy Dunlap <rdunlap@xenotime.net>

diff --git a/Documentation/DocBook/drm.tmpl b/Documentation/DocBook/drm.tmpl
index ba20f9fbb62b7febe33bc5fc55205d1793acadaf..9ae328aa1dd3b9b7169c66a1d2e11f86548c631c 100644 (file)
--- a/Documentation/DocBook/drm.tmpl
+++ b/Documentation/DocBook/drm.tmpl
@@ -724,11 +724,11 @@ void intel_crt_init(struct drm_device *dev)
        has finished rendering to the object, then the object must be made
        coherent with the CPU's view
        of memory, usually involving GPU cache flushing of various kinds.
-       This core CPU<->GPU coherency management is provided by the GEM
-       set domain function, which evaluates an object's current domain and
+       This core CPU<->GPU coherency management is provided by a
+       device-specific ioctl, which evaluates an object's current domain and
        performs any necessary flushing or synchronization to put the object
        into the desired coherency domain (note that the object may be busy,
-       i.e. an active render target; in that case, the set domain function
+       i.e. an active render target; in that case, setting the domain
        blocks the client and waits for rendering to complete before
        performing any necessary flushing operations).
       </para>