summaryrefslogtreecommitdiff
path: root/tools/perf/scripts/python/export-to-postgresql.py
diff options
context:
space:
mode:
authorVille Syrjälä <ville.syrjala@linux.intel.com>2023-06-06 22:14:57 +0300
committerVille Syrjälä <ville.syrjala@linux.intel.com>2023-09-27 18:40:58 +0300
commit5ae0da3fc78d3fdef278a22e874d6d5c305d1e03 (patch)
treee9efae584003c7a72f93ab0300526af85eb0fdc7 /tools/perf/scripts/python/export-to-postgresql.py
parentdd1c3eae5855ad36134ea415d84e567d2b55e6c7 (diff)
downloadlinux-5ae0da3fc78d3fdef278a22e874d6d5c305d1e03.tar.xz
drm/i915/dsb: Load LUTs using the DSB during vblank
Loading LUTs with the DSB outside of vblank doesn't really work due to the palette anti-collision logic. Apparently the DSB register writes don't get stalled like CPU mmio writes do and instead we end up corrupting the LUT entries. Disabling the anti-collision logic would allow us to successfully load the LUT outside of vblank, but presumably that risks the LUT reads from the scanout (temporarily) getting corrupted data from the LUT instead. The anti-collision logic isn't active during vblank so that is when we can successfully load the LUT with the DSB. That is what we want to do anyway to avoid tearing. Signed-off-by: Ville Syrjälä <ville.syrjala@linux.intel.com> Link: https://patchwork.freedesktop.org/patch/msgid/20230606191504.18099-13-ville.syrjala@linux.intel.com Reviewed-by: Uma Shankar <uma.shankar@intel.com>
Diffstat (limited to 'tools/perf/scripts/python/export-to-postgresql.py')
0 files changed, 0 insertions, 0 deletions