[RFC,1/5] drm/doc: Remove TODO about drm_vblank_pre/post_modeset()
diff mbox

Message ID b40474fecb47ff19d7ae9a4ec0f9daa1e962c32c.1444655697.git.lukas@wunner.de
State New
Headers show

Commit Message

Lukas Wunner Oct. 10, 2015, 8:22 a.m. UTC
Necessary for Daniel's rename commit to apply cleanly.

Signed-off-by: Lukas Wunner <lukas@wunner.de>
---
 Documentation/DocBook/drm.tmpl | 2 --
 1 file changed, 2 deletions(-)

Patch
diff mbox

diff --git a/Documentation/DocBook/drm.tmpl b/Documentation/DocBook/drm.tmpl
index 308b141..da1060c 100644
--- a/Documentation/DocBook/drm.tmpl
+++ b/Documentation/DocBook/drm.tmpl
@@ -3810,8 +3810,6 @@  int num_ioctls;</synopsis>
   drm_helper_connector_dpms() in reaction to fbdev blanking events. Do drivers
   that don't implement (or just don't use) fbcon compatibility need to call
   those functions themselves?
-- KMS drivers must call drm_vblank_pre_modeset() and drm_vblank_post_modeset()
-  around mode setting. Should this be done in the DRM core?
 - vblank_disable_allowed is set to 1 in the first drm_vblank_post_modeset()
   call and never set back to 0. It seems to be safe to permanently set it to 1
   in drm_vblank_init() for KMS driver, and it might be safe for UMS drivers as