diff options
author | Konrad Dybcio <konrad.dybcio@linaro.org> | 2023-06-16 02:20:42 +0300 |
---|---|---|
committer | Rob Clark <robdclark@chromium.org> | 2023-06-18 21:34:28 +0300 |
commit | a770dc6105fbd27a8c08557c8ef720c6aa878b4d (patch) | |
tree | 4ba1053c357b47dfb97556c2cd031982e4d07231 /scripts/gdb/linux/utils.py | |
parent | 452c46ccf603ab181e7d0866f3137e3ae62b5f49 (diff) | |
download | linux-a770dc6105fbd27a8c08557c8ef720c6aa878b4d.tar.xz |
dt-bindings: display/msm: gpu: Document GMU wrapper-equipped A6xx
The "GMU Wrapper" is Qualcomm's name for "let's treat the GPU blocks
we'd normally assign to the GMU as if they were a part of the GMU, even
though they are not". It's a (good) software representation of the GMU_CX
and GMU_GX register spaces within the GPUSS that helps us programatically
treat these de-facto GMU-less parts in a way that's very similar to their
GMU-equipped cousins, massively saving up on code duplication.
The "wrapper" register space was specifically designed to mimic the layout
of a real GMU, though it rather obviously does not have the M3 core et al.
GMU wrapper-equipped A6xx GPUs require clocks and clock-names to be
specified under the GPU node, just like their older cousins. Account
for that.
Acked-by: Rob Herring <robh@kernel.org>
Reviewed-by: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
Signed-off-by: Konrad Dybcio <konrad.dybcio@linaro.org>
Patchwork: https://patchwork.freedesktop.org/patch/542748/
Signed-off-by: Rob Clark <robdclark@chromium.org>
Diffstat (limited to 'scripts/gdb/linux/utils.py')
0 files changed, 0 insertions, 0 deletions