diff options
| author | 2015-12-23 18:28:11 -0200 | |
|---|---|---|
| committer | 2016-01-29 18:08:38 -0200 | |
| commit | b183b3f143959b8eea5d0970fd4ffe78df3a0210 (patch) | |
| tree | 3454f5cdc4deda6234eda2e5f627b90b69c103e2 /tools/perf/scripts/python | |
| parent | drm/i915/fbc: extract intel_fbc_can_enable() (diff) | |
drm/i915/fbc: introduce struct intel_fbc_reg_params
The early return inside __intel_fbc_update does not completely check
all the parameters that affect the FBC register values. For example,
we currently lack looking at crtc->adjusted_y (for the fence Y offset)
and all the parameters that affect the CFB size (for i8xx).
Instead of just adding the missing parameters to the check and hoping
that any changes to the fbc_activate functions also come with a
matching change to the __intel_fbc_update check, introduce a new
structure where we store these parameters and use the structure at the
fbc_activate function. Of course, it's still possible to access
everything from dev_priv in those functions, but IMHO the new code
will be harder to break.
v2: Rebase.
Reviewed-by: Maarten Lankhorst <maarten.lankhorst@linux.intel.com>
Signed-off-by: Paulo Zanoni <paulo.r.zanoni@intel.com>
Link: http://patchwork.freedesktop.org/patch/msgid/1453210558-7875-5-git-send-email-paulo.r.zanoni@intel.com
Diffstat (limited to 'tools/perf/scripts/python')
0 files changed, 0 insertions, 0 deletions
