Board tree for Google Tensor G1 devices

Sean Callanan 77432c5015 whitechapel: make vframe-secure a system heap ... 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		2021-06-04 18:01:34 +00:00
display	Allowed PowerHAL service access Display node	2021-05-11 10:23:58 +00:00
private	Update avc error on ROM 7358093	2021-05-14 14:23:22 +08:00
system_ext	Create sepolicy for the fingerprint GHBM sysprop	2021-04-08 23:21:22 +00:00
tracking_denials	Update avc error on ROM 7395282	2021-05-26 11:11:03 +08:00
usf	Merge "Add sepolicy for sensor HAL accessing AOC sysfs node." into sc-dev	2021-05-03 07:42:00 +00:00
whitechapel/vendor/google	whitechapel: make vframe-secure a system heap	2021-06-04 18:01:34 +00:00
gs101-sepolicy.mk	Add sepolicy for wlan logger and sniffer logger	2021-04-27 19:37:28 +08:00
OWNERS	Move slider-sepolicy into gs101-sepolicy	2021-03-06 16:15:39 +08:00