diff options
| author | Daniel Vetter <daniel.vetter@ffwll.ch> | 2016-05-24 14:45:15 +0200 |
|---|---|---|
| committer | Daniel Vetter <daniel.vetter@ffwll.ch> | 2016-05-24 23:25:43 +0200 |
| commit | 14fe29e8ef44a175db2d803a0b7f0aa6c372631a (patch) | |
| tree | ad89487d35ce5223266314c4f56de5cff03e6503 | |
| parent | drm: use seqlock for vblank time/count (diff) | |
| download | linux-14fe29e8ef44a175db2d803a0b7f0aa6c372631a.tar.xz linux-14fe29e8ef44a175db2d803a0b7f0aa6c372631a.zip | |
drm/doc: Drop vblank_disable_allow wording
Forgot to update the docs when nuking that. Oops.
Fixes: fcee59065e58 ("drm: Nuke ->vblank_disable_allowed")
Signed-off-by: Daniel Vetter <daniel.vetter@intel.com>
Reviewed-by: Alex Deucher <alexander.deucher@amd.com>
Signed-off-by: Daniel Vetter <daniel.vetter@ffwll.ch>
Link: http://patchwork.freedesktop.org/patch/msgid/1464093915-3935-1-git-send-email-daniel.vetter@ffwll.ch
| -rw-r--r-- | Documentation/DocBook/gpu.tmpl | 9 |
1 files changed, 1 insertions, 8 deletions
diff --git a/Documentation/DocBook/gpu.tmpl b/Documentation/DocBook/gpu.tmpl index 4a0c599b6a6d..90dbdb5087c4 100644 --- a/Documentation/DocBook/gpu.tmpl +++ b/Documentation/DocBook/gpu.tmpl @@ -2839,14 +2839,7 @@ void (*disable_vblank) (struct drm_device *dev, int crtc);</synopsis> <para> Drivers must initialize the vertical blanking handling core with a call to <function>drm_vblank_init</function> in their - <methodname>load</methodname> operation. The function will set the struct - <structname>drm_device</structname> - <structfield>vblank_disable_allowed</structfield> field to 0. This will - keep vertical blanking interrupts enabled permanently until the first mode - set operation, where <structfield>vblank_disable_allowed</structfield> is - set to 1. The reason behind this is not clear. Drivers can set the field - to 1 after <function>calling drm_vblank_init</function> to make vertical - blanking interrupts dynamically managed from the beginning. + <methodname>load</methodname> operation. </para> <para> Vertical blanking interrupts can be enabled by the DRM core or by drivers |