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
18 lines
646 B
Text
18 lines
646 B
Text
type persist_block_device, dev_type;
|
|
type tee_persist_block_device, dev_type;
|
|
type custom_ab_block_device, dev_type;
|
|
type devinfo_block_device, dev_type;
|
|
type mfg_data_block_device, dev_type;
|
|
type ufs_internal_block_device, dev_type;
|
|
type logbuffer_device, dev_type;
|
|
type gxp_device, dev_type, mlstrustedobject;
|
|
type fingerprint_device, dev_type;
|
|
type uci_device, dev_type;
|
|
|
|
# Dmabuf heaps
|
|
type sensor_direct_heap_device, dmabuf_heap_device_type, dev_type;
|
|
type faceauth_heap_device, dmabuf_heap_device_type, dev_type;
|
|
type vscaler_secure_heap_device, dmabuf_heap_device_type, dev_type;
|
|
|
|
# SecureElement SPI device
|
|
type st54spi_device, dev_type;
|