mirror of
https://github.com/Evolution-X/hardware_interfaces
synced 2026-02-01 11:36:00 +00:00
health: Update README.md for SELinux rule example am: d4ebad8aef am: a68e416fee
Original change: https://android-review.googlesource.com/c/platform/hardware/interfaces/+/1894882 Change-Id: I5acdc5ff5e82143242fd7c07584d2b77f46ec85a
This commit is contained in:
@@ -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
|
||||
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
|
||||
`hal_health_default`. The device-specific rules for it is likely at
|
||||
`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}
|
||||
|
||||
|
||||
Reference in New Issue
Block a user