On 11/2/26 10:13 PM, Val Packett wrote:
The initialization sequence for a680 differs from a640 in a few places.
Match downstream by using this a680 specific one.
Signed-off-by: Val Packett <[email protected]>
---
drivers/gpu/drm/msm/adreno/a6xx_catalog.c | 56 ++++++++++++++++++++++-
1 file changed, 55 insertions(+), 1 deletion(-)
diff --git a/drivers/gpu/drm/msm/adreno/a6xx_catalog.c
b/drivers/gpu/drm/msm/adreno/a6xx_catalog.c
index 6c154792cb07..48197a54984c 100644
--- a/drivers/gpu/drm/msm/adreno/a6xx_catalog.c
+++ b/drivers/gpu/drm/msm/adreno/a6xx_catalog.c
@@ -9,6 +9,7 @@
#include "adreno_gpu.h"
#include "a6xx_gpu.h"
#include "a6xx.xml.h"
+#include "a6xx_gmu.xml.h"
[..]
(As sashiko confirms it's not a good idea to try to write the gmu regs
from here, shouldn't've gotten lazy and assumed it would work anyway..)
I can make the gmu driver write these on init, but would like to know if
they even do anything interesting, and whether the entire hwcg sequence
is worth it…
