Donate to e Foundation | Murena handsets with /e/OS | Own a part of Murena! Learn more

Commit 14fe29e8 authored by Daniel Vetter's avatar Daniel Vetter
Browse files

drm/doc: Drop vblank_disable_allow wording 



Forgot to update the docs when nuking that. Oops.

Fixes: fcee5906 ("drm: Nuke ->vblank_disable_allowed")
Signed-off-by: default avatarDaniel Vetter <daniel.vetter@intel.com>
Reviewed-by: default avatarAlex Deucher <alexander.deucher@amd.com>
Signed-off-by: default avatarDaniel Vetter <daniel.vetter@ffwll.ch>
Link: http://patchwork.freedesktop.org/patch/msgid/1464093915-3935-1-git-send-email-daniel.vetter@ffwll.ch
parent d4055a9b

Documentation/DocBook/gpu.tmpl

+1 −8
Original line number Diff line number Diff line
@@ -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