summaryrefslogtreecommitdiff
path: root/Documentation/gpu/drm-uapi.rst
diff options
context:
space:
mode:
authorJani Nikula <jani.nikula@intel.com>2016-06-21 14:49:00 +0300
committerDaniel Vetter <daniel.vetter@ffwll.ch>2016-06-21 15:15:18 +0300
commit22554020409f6febcce2790380e46cd483ae04bb (patch)
tree355dfc9c00ced4b9d312457e6c80beb470e159d7 /Documentation/gpu/drm-uapi.rst
parent621c5474744ce780a5485284273de77b66f4cae2 (diff)
downloadlinux-22554020409f6febcce2790380e46cd483ae04bb.tar.xz
Documentation/gpu: use recommended order of heading markers
While splitting the document up, the headings "shifted" from what pandoc generated. Use the following order for headings for consistency: ============== Document title ============== First ===== Second ------ Third ~~~~~ Leave the lower level headings as they are; I think those are less important. Although RST doesn't mandate a specific order ("Rather than imposing a fixed number and order of section title adornment styles, the order enforced will be the order as encountered."), having the higher levels the same overall makes it easier to follow the documents. [I'm sort of kind of writing the recommendation for docs-next in the mean time, but this order seems sensible, and is what I'm proposing.] Signed-off-by: Jani Nikula <jani.nikula@intel.com> Signed-off-by: Daniel Vetter <daniel.vetter@ffwll.ch> Link: http://patchwork.freedesktop.org/patch/msgid/126f42734defac6cbb8496a481d58db7b38461dd.1466506505.git.jani.nikula@intel.com
Diffstat (limited to 'Documentation/gpu/drm-uapi.rst')
-rw-r--r--Documentation/gpu/drm-uapi.rst5
1 files changed, 3 insertions, 2 deletions
diff --git a/Documentation/gpu/drm-uapi.rst b/Documentation/gpu/drm-uapi.rst
index 3b667b1992e5..6da1e77e55fa 100644
--- a/Documentation/gpu/drm-uapi.rst
+++ b/Documentation/gpu/drm-uapi.rst
@@ -1,3 +1,4 @@
+===================
Userland interfaces
===================
@@ -14,7 +15,7 @@ Cover generic ioctls and sysfs layout here. We only need high-level
info, since man pages should cover the rest.
Render nodes
-------------
+============
DRM core provides multiple character-devices for user-space to use.
Depending on which device is opened, user-space can perform a different
@@ -67,7 +68,7 @@ visible to user-space and accessible beyond open-file boundaries, they
cannot support render nodes.
VBlank event handling
----------------------
+=====================
The DRM core exposes two vertical blank related ioctls: