diff options
| author | Vinod Govindapillai <vinod.govindapillai@intel.com> | 2025-02-28 11:38:02 +0200 |
|---|---|---|
| committer | Mika Kahola <mika.kahola@intel.com> | 2025-03-03 14:45:45 +0200 |
| commit | af23476af8a9ee881bd7a6ef5c94b6f4049ad096 (patch) | |
| tree | fdd89413c8c6a60724a86da456a8ad7d8de6812b /tools/perf/scripts/python/export-to-sqlite.py | |
| parent | e2364a56ad47d3299b1bf2fdb854359d4a770230 (diff) | |
drm/i915/fbc: handle dirty rect coords for the first frame
During enabling FBC, for the very first frame, the prepare dirty
rect routine wouldnt have executed as at that time the plane
reference in the fbc_state would be NULL. So this could make
driver program some invalid entries as the damage area. Though
fbc hw ignores the dirty rect values programmed for the first
frame after enabling FBC, driver must ensure that valid dirty
rect coords are programmed. So ensure that for the first frame
correct dirty rect coords are updated to the HW.
Signed-off-by: Vinod Govindapillai <vinod.govindapillai@intel.com>
Reviewed-by: Ville Syrjälä <ville.syrjala@linux.intel.com>
Signed-off-by: Mika Kahola <mika.kahola@intel.com>
Link: https://patchwork.freedesktop.org/patch/msgid/20250228093802.27091-10-vinod.govindapillai@intel.com
Diffstat (limited to 'tools/perf/scripts/python/export-to-sqlite.py')
0 files changed, 0 insertions, 0 deletions