drm/i915/gen9: Propagate watermark calculation failures up the call chain
authorMatt Roper <matthew.d.roper@intel.com>
Thu, 12 May 2016 14:06:08 +0000 (07:06 -0700)
committerMatt Roper <matthew.d.roper@intel.com>
Fri, 13 May 2016 14:34:48 +0000 (07:34 -0700)
commit55994c2c38a1101f84cdf277b228f830af8a9c1b
tree707c03aac8ae589b8261607b7461fad888d944e3
parent2b4b9f35d94b1b533bc23110b040b04316480b28
drm/i915/gen9: Propagate watermark calculation failures up the call chain

Once we move watermark calculation to the atomic check phase, we'll want
to start rejecting display configurations that exceed out watermark
limits.  At the moment we just assume that there's always a valid set of
watermarks, even though this may not actually be true.  Let's prepare by
passing return codes up through the call stack in preparation.

Signed-off-by: Matt Roper <matthew.d.roper@intel.com>
Reviewed-by: Maarten Lankhorst <maarten.lankhorst@linux.intel.com>
Link: http://patchwork.freedesktop.org/patch/msgid/1463061971-19638-15-git-send-email-matthew.d.roper@intel.com
drivers/gpu/drm/i915/intel_display.c
drivers/gpu/drm/i915/intel_pm.c