gralloc: Use PROTECTED flag for L1 allocations
This is in keeping with the gralloc spec. Change-Id: Id796a55e2ea51d3abdf9274140dc0404a42e1cab CRs-fixed: 999994
This commit is contained in:
committed by
Gerrit - the friendly Code Review server
parent
abecb17c14
commit
934a4c33e3
@@ -446,7 +446,6 @@ int IonController::allocate(alloc_data& data, int usage)
|
||||
data.allocType = 0;
|
||||
|
||||
if(usage & GRALLOC_USAGE_PROTECTED) {
|
||||
if (usage & GRALLOC_USAGE_PRIVATE_MM_HEAP) {
|
||||
if (usage & GRALLOC_USAGE_PRIVATE_SECURE_DISPLAY) {
|
||||
ionHeapId = ION_HEAP(SD_HEAP_ID);
|
||||
/*
|
||||
@@ -458,12 +457,6 @@ int IonController::allocate(alloc_data& data, int usage)
|
||||
ionHeapId = ION_HEAP(CP_HEAP_ID);
|
||||
ionFlags |= ION_CP_FLAGS;
|
||||
}
|
||||
} else {
|
||||
// for targets/OEMs which do not need HW level protection
|
||||
// do not set ion secure flag & MM heap. Fallback to system heap.
|
||||
ionHeapId |= ION_HEAP(ION_SYSTEM_HEAP_ID);
|
||||
data.allocType |= private_handle_t::PRIV_FLAGS_PROTECTED_BUFFER;
|
||||
}
|
||||
} else if(usage & GRALLOC_USAGE_PRIVATE_MM_HEAP) {
|
||||
//MM Heap is exclusively a secure heap.
|
||||
//If it is used for non secure cases, fallback to IOMMU heap
|
||||
|
||||
Reference in New Issue
Block a user