From df90f6f80125b416ba3d5d2d0cb3df10c1f51360 Mon Sep 17 00:00:00 2001
From: Bruno BELANYI <ambroisie@google.com>
Date: Thu, 6 Apr 2023 15:18:28 +0000
Subject: [PATCH] Define mali configuration path explicitly

This avoids mali trying to read `/data/data/com.mali.testjava` for its
debug config.

Bug: 205779871
Bug: 264489188
Test: manual - reboot device and check the absence of AVC denials
(cherry picked from commit 7038bae086b572038ddb3d7b203b34b9519dd0fe)
Merged-In: I42051ae2c10c6d4fa7c1f9d5f485ff5471e6a287
Change-Id: I42051ae2c10c6d4fa7c1f9d5f485ff5471e6a287
---
 device.mk | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/device.mk b/device.mk
index d36b2fd6..c4107d42 100644
--- a/device.mk
+++ b/device.mk
@@ -251,6 +251,8 @@ endif
 # Mali Configuration Properties
 # b/221255664 prevents setting PROTECTED_MAX_CORE_COUNT=2
 PRODUCT_VENDOR_PROPERTIES += \
+	vendor.mali.platform.config=/vendor/etc/mali/platform.config \
+	vendor.mali.debug.config=/vendor/etc/mali/debug.config \
       	vendor.mali.base_protected_max_core_count=1 \
 	vendor.mali.base_protected_tls_max=67108864 \
 	vendor.mali.platform_agt_frequency_khz=24576