Fix mali memory protection sysprop names
The previous patch did not use the `base_*` prefix, meaning the driver kept using the default configuration. Bug: b/272740524 Test: CtsDeqpTestCases (dEQP-VK.protected_memory.stack.stacksize_*) Change-Id: I71aee32590e3878ada69533daeb2b629eb4a42fc
This commit is contained in:
parent
d66d0876b9
commit
c223a49038
1 changed files with 2 additions and 2 deletions
|
@ -235,8 +235,8 @@ PRODUCT_VENDOR_PROPERTIES += \
|
||||||
# Mali Configuration Properties
|
# Mali Configuration Properties
|
||||||
# b/221255664 prevents setting PROTECTED_MAX_CORE_COUNT=2
|
# b/221255664 prevents setting PROTECTED_MAX_CORE_COUNT=2
|
||||||
PRODUCT_VENDOR_PROPERTIES += \
|
PRODUCT_VENDOR_PROPERTIES += \
|
||||||
vendor.mali.protected_max_core_count=1 \
|
vendor.mali.base_protected_max_core_count=1 \
|
||||||
vendor.mali.protected_tls_max=67108864 \
|
vendor.mali.base_protected_tls_max=67108864 \
|
||||||
vendor.mali.platform_agt_frequency_khz=24576
|
vendor.mali.platform_agt_frequency_khz=24576
|
||||||
|
|
||||||
ifeq ($(USE_SWIFTSHADER),true)
|
ifeq ($(USE_SWIFTSHADER),true)
|
||||||
|
|
Loading…
Add table
Add a link
Reference in a new issue