summaryrefslogtreecommitdiffstats
path: root/include/drm
diff options
context:
space:
mode:
authorDaniel Vetter <daniel.vetter@ffwll.ch>2013-08-08 15:41:15 +0200
committerDave Airlie <airlied@redhat.com>2013-08-19 14:28:46 +1000
commit7d14bb6b537414ffe6a8641cb14088465c28460d (patch)
treeda32f10856998e7c039a84e93a3cd5cf17f274ea /include/drm
parent0faa4a877765a4855dd570d6d391f77c5c37abc3 (diff)
downloadop-kernel-dev-7d14bb6b537414ffe6a8641cb14088465c28460d.zip
op-kernel-dev-7d14bb6b537414ffe6a8641cb14088465c28460d.tar.gz
drm: don't call ->firstopen for KMS drivers
It has way too much potential for driver writers to do stupid things like delayed hw setup because the load sequence is somehow racy (e.g. the imx driver in staging). So don't call it for modesetting drivers, which reduces the complexity of the drm core -> driver interface a notch. v2: Don't forget to update DocBook. v3: Go with Laurent's slightly more elaborate proposal for the DocBook update. Add a few words on top of his diff to elaborate a bit on what KMS drivers should and shouldn't do in lastclose. There was already a paragraph present talking about restoring properties, I've simply extended that one. Cc: Laurent Pinchart <laurent.pinchart@ideasonboard.com> Acked-by: Laurent Pinchart <laurent.pinchart@ideasonboard.com> Signed-off-by: Daniel Vetter <daniel.vetter@ffwll.ch> Signed-off-by: Dave Airlie <airlied@redhat.com>
Diffstat (limited to 'include/drm')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud