summaryrefslogtreecommitdiff
path: root/tools/perf/scripts/python/call-graph-from-postgresql.py
diff options
context:
space:
mode:
authorMatt Roper <matthew.d.roper@intel.com>2015-09-25 01:53:13 +0300
committerDaniel Vetter <daniel.vetter@ffwll.ch>2015-09-30 18:15:47 +0300
commit47c99438b52d12df50e182583634a4cfede3c920 (patch)
treee9bea4f9c8d70c5c3f4f2fe30c03ea9980dfec06 /tools/perf/scripts/python/call-graph-from-postgresql.py
parent7809e5ae35b9d8d0710f0874b2e3f10be144e38b (diff)
downloadlinux-47c99438b52d12df50e182583634a4cfede3c920.tar.xz
drm/i915: Drop intel_update_sprite_watermarks
The only platform that still has an update_sprite_wm entrypoint is SKL; on SKL, intel_update_sprite_watermarks just updates intel_plane->wm and then performs a regular watermark update. However intel_plane->wm is only used to update a couple fields in intel_wm_config, and those fields are never used by the SKL code, so on SKL an update_sprite_wm is effectively identical to an update_wm call. Since we're already ensuring that the regular intel_update_wm is called any time we'd try to call intel_update_sprite_watermarks, the whole call is redundant and can be dropped. Signed-off-by: Matt Roper <matthew.d.roper@intel.com> Reviewed-by: Maarten Lankhorst <maarten.lankhorst@linux.intel.com> Signed-off-by: Daniel Vetter <daniel.vetter@ffwll.ch>
Diffstat (limited to 'tools/perf/scripts/python/call-graph-from-postgresql.py')
0 files changed, 0 insertions, 0 deletions