diff options
author | Konrad Dybcio <[email protected]> | 2023-06-16 01:20:43 +0200 |
---|---|---|
committer | Rob Clark <[email protected]> | 2023-06-18 11:34:28 -0700 |
commit | 63204be2806b09ab75e03e42c477f69bfd050efc (patch) | |
tree | a4b94262b301ac172942d0b04082235ffa9c1a00 /lib/test_fortify/write_overflow-strlcpy-src.c | |
parent | a770dc6105fbd27a8c08557c8ef720c6aa878b4d (diff) |
dt-bindings: display/msm/gmu: Add GMU wrapper
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.
To sum it all up, the GMU wrapper is essentially a register space within
the GPU, which Linux sees as a dumbed-down regular GMU: there's no clocks,
interrupts, multiple reg spaces, iommus and OPP. Document it.
Reviewed-by: Krzysztof Kozlowski <[email protected]>
Signed-off-by: Konrad Dybcio <[email protected]>
Patchwork: https://patchwork.freedesktop.org/patch/542750/
Signed-off-by: Rob Clark <[email protected]>
Diffstat (limited to 'lib/test_fortify/write_overflow-strlcpy-src.c')
0 files changed, 0 insertions, 0 deletions