Board tree for Google Tensor G4 devices
Find a file
Ankit Goyal 129741a269 Mark video secure devices as default dmabuf heaps
Mali driver (and codec HAL as well) require direct access to video
secure dmabuf devices. Mali driver being an SP-HAL cannot explicitly
write blanket rules for all the scontext. So, we piggyback on
dmabuf_system_secure_heap_device to allow all scontext to be able to use
these device nodes.

This is just as secure as dmabuf_system_secure_heap_device in that case.
There is no additional security impact. An app can still use gralloc to
allocate buffers from these heaps and disallowing access to these heaps
to the intended users.

Bug: 278513588
Test: Trusting result of ag/22743596 (no zumapro device yet)
Change-Id: I2fd77e6694cdd4d1e51c9f01f4ae2b9f9670cea0
2023-04-19 19:53:49 +00:00
legacy init zumapro from zuma sha 43d5907677d0f 2023-03-31 14:16:57 +00:00
private Sync with device/google/zuma-sepolicy cfa00dfc881e3 2023-04-11 10:30:07 +00:00
radio Sync with device/google/zuma-sepolicy cfa00dfc881e3 2023-04-11 10:30:07 +00:00
system_ext/private init zumapro from zuma sha 43d5907677d0f 2023-03-31 14:16:57 +00:00
tracking_denials Sync with device/google/zuma-sepolicy cfa00dfc881e3 2023-04-11 10:30:07 +00:00
vendor Mark video secure devices as default dmabuf heaps 2023-04-19 19:53:49 +00:00
widevine init zumapro from zuma sha 43d5907677d0f 2023-03-31 14:16:57 +00:00
bug_map init zumapro from zuma sha 43d5907677d0f 2023-03-31 14:16:57 +00:00
OWNERS init zumapro from zuma sha 43d5907677d0f 2023-03-31 14:16:57 +00:00
zumapro-sepolicy.mk init zumapro from zuma sha 43d5907677d0f 2023-03-31 14:16:57 +00:00