From cd581af95621ebdc458affc457c86585973cdef9 Mon Sep 17 00:00:00 2001
From: Bruno BELANYI <ambroisie@google.com>
Date: Thu, 6 Apr 2023 15:19:48 +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 https://googleplex-android-review.googlesource.com/q/commit:aa5b1036db7f53d253d533cded53654974f773c2)
Merged-In: Id168e9ce380eb6d3657a83e74ec8afd52bbd584e
Change-Id: Id168e9ce380eb6d3657a83e74ec8afd52bbd584e
---
 device.mk | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/device.mk b/device.mk
index e71b9951..7bc49203 100644
--- a/device.mk
+++ b/device.mk
@@ -236,6 +236,8 @@ PRODUCT_VENDOR_PROPERTIES += \
 # 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