aboutsummaryrefslogtreecommitdiffstats
path: root/tools/perf/scripts/python/export-to-postgresql.py
diff options
context:
space:
mode:
authorJonathan Marek <[email protected]>2021-05-13 17:13:59 +0000
committerRob Clark <[email protected]>2021-06-08 18:26:45 +0000
commit408434036958699a7f50ddec984f7ba33e11a8f5 (patch)
tree0dde390f55c1cc16ecdc742c1d2b45c9b1e24ce8 /tools/perf/scripts/python/export-to-postgresql.py
parentdrm/msm: Init mm_list before accessing it for use_vram path (diff)
downloadkernel-408434036958699a7f50ddec984f7ba33e11a8f5.tar.gz
kernel-408434036958699a7f50ddec984f7ba33e11a8f5.zip
drm/msm/a6xx: update/fix CP_PROTECT initialization
Update CP_PROTECT register programming based on downstream. A6XX_PROTECT_RW is renamed to A6XX_PROTECT_NORDWR to make things aligned and also be more clear about what it does. Note that this required switching to use the CP_ALWAYS_ON_COUNTER as the GMU counter is not accessible from the cmdstream. Which also means using the CPU counter for the msm_gpu_submit_flush() tracepoint (as catapult depends on being able to compare this to the start/end values captured in cmdstream). This may need to be revisited when IFPC is enabled. Also, compared to downstream, this opens up CP_PERFCTR_CP_SEL as the userspace performance tooling (fdperf and pps-producer) expect to be able to configure the CP counters. Fixes: 4b565ca5a2cb ("drm/msm: Add A6XX device support") Signed-off-by: Jonathan Marek <[email protected]> Reviewed-by: Akhil P Oommen <[email protected]> Link: https://lore.kernel.org/r/[email protected] [switch to CP_ALWAYS_ON_COUNTER, open up CP_PERFCNTR_CP_SEL, and spiff up commit msg] Signed-off-by: Rob Clark <[email protected]>
Diffstat (limited to 'tools/perf/scripts/python/export-to-postgresql.py')
0 files changed, 0 insertions, 0 deletions