2017-02-10 00:15:11 +01:00
|
|
|
# bufferhubd
|
|
|
|
type bufferhubd, domain, mlstrustedsubject;
|
|
|
|
type bufferhubd_exec, exec_type, file_type;
|
|
|
|
|
2017-03-22 17:16:49 +01:00
|
|
|
hal_client_domain(bufferhubd, hal_graphics_allocator)
|
|
|
|
|
2017-05-01 22:01:44 +02:00
|
|
|
pdx_server(bufferhubd, bufferhub_client)
|
|
|
|
pdx_client(bufferhubd, performance_client)
|
2017-02-10 00:15:11 +01:00
|
|
|
|
|
|
|
# Access the GPU.
|
|
|
|
allow bufferhubd gpu_device:chr_file rw_file_perms;
|
|
|
|
|
|
|
|
# Access /dev/ion
|
|
|
|
allow bufferhubd ion_device:chr_file r_file_perms;
|
2017-03-10 03:44:07 +01:00
|
|
|
|
2018-05-26 01:23:37 +02:00
|
|
|
# Receive sync fence FDs from hal_omx_server. Note that hal_omx_server never directly
|
2017-03-10 03:44:07 +01:00
|
|
|
# connects to bufferhubd via PDX. Instead, a VR app acts as a bridge between
|
2018-05-26 01:23:37 +02:00
|
|
|
# those two: it talks to hal_omx_server via Binder and talks to bufferhubd via PDX.
|
2017-05-01 22:01:44 +02:00
|
|
|
# Thus, there is no need to use pdx_client macro.
|
2018-05-26 01:23:37 +02:00
|
|
|
allow bufferhubd hal_omx_server:fd use;
|