From: Ville Syrjälä <ville.syrj...@linux.intel.com> I recently realized that we can't really continue with loading the driver if we fail to initialize some of the crtcs or planes. So this series makes us fail the load in those cases. The failures would be due to kmalloc() failing anyway, so doesn't seem too drastic to abort entirely in that case.
I also reorder things so that we'll initialize the planes in an order that matches the new rules for handling zpos conflicts between the planes. We don't expose the zpos property yet, but I have some preliminary patches for that as well sitting around in a branch. Actually only VLV, CHV and pre-g4x can dynamically adjust the zpos of the planes, for the rest it's entirely fixed. And finally I do a bit of house cleaning in the sprite init code. Entire series available here: git://github.com/vsyrjala/linux.git plane_init_order Ville Syrjälä (4): drm/i915: Don't try to initialize sprite planes on pre-ilk drm/i915: Initialize planes in a reasonable order drm/i915: Bail if plane/crtc init fails drm/i915: Reorganize sprite init drivers/gpu/drm/i915/i915_drv.c | 4 +- drivers/gpu/drm/i915/i915_drv.h | 2 +- drivers/gpu/drm/i915/intel_device_info.c | 5 +- drivers/gpu/drm/i915/intel_display.c | 107 ++++++++++++++++++++----------- drivers/gpu/drm/i915/intel_drv.h | 3 +- drivers/gpu/drm/i915/intel_sprite.c | 81 ++++++++++------------- 6 files changed, 112 insertions(+), 90 deletions(-) -- 2.7.4 _______________________________________________ Intel-gfx mailing list Intel-gfx@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/intel-gfx
