summaryrefslogtreecommitdiffstats
path: root/drivers/gpu/drm/i915/intel_atomic.c
diff options
context:
space:
mode:
authorMaarten Lankhorst <maarten.lankhorst@linux.intel.com>2018-10-18 13:51:30 +0200
committerMaarten Lankhorst <maarten.lankhorst@linux.intel.com>2018-10-24 10:30:14 +0200
commitb048a00b3d9635141c7b1d4eabf6cff869a92238 (patch)
tree15b1f84f7f8bae0bb523e449355c479b4b838f40 /drivers/gpu/drm/i915/intel_atomic.c
parent1ab554b0099b655141c47ec5cd05d126eaed4868 (diff)
downloadtalos-op-linux-b048a00b3d9635141c7b1d4eabf6cff869a92238.tar.gz
talos-op-linux-b048a00b3d9635141c7b1d4eabf6cff869a92238.zip
drm/i915/gen11: Handle watermarks correctly for separate Y/UV planes, v2.
Skylake style watermarks program the UV parameters into wm->uv_wm, and have a separate DDB allocation for UV blocks into the same plane. Gen11 watermarks have a separate plane for Y and UV, with separate mechanisms. The simplest way to make it work is to keep the current way of programming watermarks and calculate the Y and UV plane watermarks from the master plane. Changes since v1: - Constify crtc_state where possible. - Make separate paths for planar formats in skl_build_pipe_wm() (Matt) - Make separate paths for calculating total data rate. (Matt) - Make sure UV watermarks are unused on gen11+ by adding a WARN. (Matt) Signed-off-by: Maarten Lankhorst <maarten.lankhorst@linux.intel.com> Reviewed-by: Ville Syrjälä <ville.syrjala@linux.intel.com> Link: https://patchwork.freedesktop.org/patch/msgid/20181018115134.9061-5-maarten.lankhorst@linux.intel.com
Diffstat (limited to 'drivers/gpu/drm/i915/intel_atomic.c')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud