| Alex Klyubin | f5446eb | 2017-03-23 14:27:32 -0700 | [diff] [blame] | 1 | typeattribute bufferhubd coredomain; |
| 2 | |
| Nick Bray | 084faf0 | 2017-02-09 15:15:11 -0800 | [diff] [blame] | 3 | init_daemon_domain(bufferhubd) |
| Inseob Kim | 75806ef | 2024-03-27 17:18:41 +0900 | [diff] [blame] | 4 | |
| 5 | hal_client_domain(bufferhubd, hal_graphics_allocator) |
| 6 | |
| 7 | # TODO(b/112338294): remove these after migrate to Binder |
| 8 | pdx_server(bufferhubd, bufferhub_client) |
| 9 | pdx_client(bufferhubd, performance_client) |
| 10 | |
| 11 | # Access the GPU. |
| 12 | allow bufferhubd gpu_device:chr_file rw_file_perms; |
| 13 | |
| 14 | # Access /dev/ion |
| 15 | allow bufferhubd ion_device:chr_file r_file_perms; |
| 16 | |
| 17 | # Receive sync fence FDs from hal_omx_server. Note that hal_omx_server never directly |
| 18 | # connects to bufferhubd via PDX. Instead, a VR app acts as a bridge between |
| 19 | # those two: it talks to hal_omx_server via Binder and talks to bufferhubd via PDX. |
| 20 | # Thus, there is no need to use pdx_client macro. |
| 21 | allow bufferhubd hal_omx_server:fd use; |
| 22 | |
| 23 | # Codec2 is similar to OMX |
| 24 | allow bufferhubd hal_codec2_server:fd use; |