77432c5015
The GPU driver uses vframe-secure for secure allocations, so the corresponding DMA heap file should be visible to all processes so use the dmabuf_system_secure_heap_device type instead. In order for this type to be used, we need to ensure that the HAL Allocator has access to it, so update hal_graphics_allocator_default.te Finally, since there are no longer any buffer types associated with the vframe_heap_device type, remove it. Bug: 182090311 Test: run cts-dev -m CtsDeqpTestCases --module-arg CtsDeqpTestCases:include-filter:dEQP-VK.protected_memory.stack.stacksize_64 and ensure secure allocations succeed Test: Play DRM-protected video in ExoPlayer and ensure videos render correctly via MFC->DPU. Change-Id: Id341e52322a438974d4634a4274a7be2ddb4c9fe
9 lines
325 B
Text
9 lines
325 B
Text
userdebug_or_eng(`
|
|
set_prop(mediacodec, vendor_codec2_debug_prop)
|
|
')
|
|
|
|
add_service(mediacodec, eco_service)
|
|
allow mediacodec hal_camera_default:binder call;
|
|
allow mediacodec sysfs_video:file r_file_perms;
|
|
allow mediacodec sysfs_video:dir r_dir_perms;
|
|
allow mediacodec dmabuf_system_secure_heap_device:chr_file r_file_perms;
|