Evolution-x/hardware_interfaces
1
0
Fork 0
mirror of https://github.com/Evolution-X/hardware_interfaces synced 2026-02-01 22:04:26 +00:00
Code Issues Packages Projects Releases Wiki Activity

health: Update README.md for SELinux rule example

Browse Source 
Test: none
Bug: 177269435
Change-Id: Ifd5ef99e7dd1c27fe9973daa65ad70714f86a46b
This commit is contained in:
Yifan Hong
2021-11-16 23:21:21 -08:00
parent f665b8fa86
commit d4ebad8aef
1 changed files with 17 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

17
health/aidl/README.md
View File

@@ -162,9 +162,26 @@ Add device specific permissions to the domain where the health HAL
process is executed, especially if a device-specific `libhealthd` is used process is executed, especially if a device-specific `libhealthd` is used
and/or device-specific storage related APIs are implemented. and/or device-specific storage related APIs are implemented.
Example (assuming that your health AIDL service runs in domain
`hal_health_tuna`:
```text
type hal_health_tuna, domain;
hal_server_domain(hal_health_tuna, hal_health)
type hal_health_tuna_exec, exec_type, vendor_file_type, file_type;
# allow hal_health_tuna ...;
```
If you did not define a separate domain, the domain is likely If you did not define a separate domain, the domain is likely
`hal_health_default`. The device-specific rules for it is likely at `hal_health_default`. The device-specific rules for it is likely at
`device/<manufacturer>/<device>/sepolicy/vendor/hal_health_default.te`. `device/<manufacturer>/<device>/sepolicy/vendor/hal_health_default.te`.
In this case, the aforementioned SELinux rules and types has already been
defined. You only need to add device-specific permissions.
```text
# allow hal_health_default ...;
```
### Implementing charger {#charger} ### Implementing charger {#charger}