drm/i915: Handle cdclk limits on broadwell.

As the comment indicates this can only fail gracefully when
called from compute_config. Fortunately this is now what's happening,
so the fixme can be removed and the DRM_ERROR downgraded.

Link: http://patchwork.freedesktop.org/patch/msgid/1448360945-5723-3-git-send-email-maarten.lankhorst@linux.intel.com
Signed-off-by: Maarten Lankhorst <maarten.lankhorst@linux.intel.com>
Reviewed-by: Chris Wilson <chris@chris-wilson.co.uk>

1 files changed, 3 insertions, 7 deletions

diff --git a/drivers/gpu/drm/i915/intel_display.c b/drivers/gpu/drm/i915/intel_display.c
index 01aae086b532..3a13a498722a 100644
--- a/drivers/gpu/drm/i915/intel_display.c
+++ b/drivers/gpu/drm/i915/intel_display.c
@@ -9719,14 +9719,10 @@ static int broadwell_modeset_calc_cdclk(struct drm_atomic_state *state)
         else
                 cdclk = 337500;
 
-        /*
-         * FIXME move the cdclk caclulation to
-         * compute_config() so we can fail gracegully.
-         */
         if (cdclk > dev_priv->max_cdclk_freq) {
-                DRM_ERROR("requested cdclk (%d kHz) exceeds max (%d kHz)\n",
-                          cdclk, dev_priv->max_cdclk_freq);
-                cdclk = dev_priv->max_cdclk_freq;
+                DRM_DEBUG_KMS("requested cdclk (%d kHz) exceeds max (%d kHz)\n",
+                              cdclk, dev_priv->max_cdclk_freq);
+                return -EINVAL;
         }
 
         to_intel_atomic_state(state)->cdclk = cdclk;