summaryrefslogtreecommitdiffstats
path: root/drivers/gpu/drm/i915/intel_fb.c
diff options
context:
space:
mode:
authorDaniel Vetter <daniel.vetter@ffwll.ch>2013-01-21 23:12:36 +0100
committerDaniel Vetter <daniel.vetter@ffwll.ch>2013-02-14 00:07:56 +0100
commit2180c3c7e76536ce8ff0fd957a11dbfaa1e93403 (patch)
treefc27793faacf7148337e78b9f7dcb8b3667039e9 /drivers/gpu/drm/i915/intel_fb.c
parent7e53f3a423146745a4e4bb93362d488dfad502a8 (diff)
drm/fb-helper: directly call set_par from the hotplug handler
The idea behind calling down into the driver's ->fb_probe function on each hotplug seems to be able to reallocate the backing storage (if e.g. a screen with higher resolution gets added). But that requires quite a bit of work in the fb helper itself, since currently we limit new screens to the currently allocated fb. An no kms driver supports fbdev fb resizing. So don't bother and start to simplify the code by calling drm_fb_helper_set_par directly from the fbdev hotplug function, since that's the only thing left in drm_fb_helper_single_fb_probe which does not concern itself with fb allocation and initial setup. Follow-on patches will streamline the initial setup code. Reviewed-by: Rob Clark <robdclark@gmail.com> Signed-off-by: Daniel Vetter <daniel.vetter@ffwll.ch>
Diffstat (limited to 'drivers/gpu/drm/i915/intel_fb.c')
0 files changed, 0 insertions, 0 deletions