The FBC watermark doesn't depend on the latency value, so no point in
passing it in.
Note: It actually depends upon the latency, but only through priv_val
...
Signed-off-by: Ville Syrjälä <ville.syrjala@linux.intel.com>
Reviewed-by: Paulo Zanoni <paulo.r.zanoni@intel.com>
[danvet: Add review comment from Paulo to the commit message.]
Signed-off-by: Daniel Vetter <daniel.vetter@ffwll.ch>
 
 /* Only for WM_LP. */
 static uint32_t ilk_compute_fbc_wm(struct hsw_pipe_wm_parameters *params,
-                                  uint32_t pri_val,
-                                  uint32_t mem_value)
+                                  uint32_t pri_val)
 {
        if (!params->active)
                return 0;
                pri_val[pipe] = ilk_compute_pri_wm(p, mem_value, true);
                spr_val[pipe] = ilk_compute_spr_wm(p, mem_value);
                cur_val[pipe] = ilk_compute_cur_wm(p, mem_value);
-               fbc_val[pipe] = ilk_compute_fbc_wm(p, pri_val[pipe], mem_value);
+               fbc_val[pipe] = ilk_compute_fbc_wm(p, pri_val[pipe]);
        }
 
        result->pri_val = max3(pri_val[0], pri_val[1], pri_val[2]);