bcl: Add brownout boot reason sepolicy

Lastmeal.txt may be generated from after device rebooted from IRQ
triggering.  By applying limit on the time when it generates,
lastmeal.txt will not be generated after device rebooted.

Bug: 246817058
Test: Confirm lastmeal.txt generation
Signed-off-by: George Lee <geolee@google.com>
Change-Id: I02515fc452dbfa5c8a40041cbb8731664dace62e
This commit is contained in:
George Lee 2022-10-10 09:40:51 -07:00
parent 2260099ad3
commit b72e47e1b0
4 changed files with 9 additions and 0 deletions

View file

@ -2,6 +2,7 @@ type battery_mitigation, domain;
type battery_mitigation_exec, exec_type, vendor_file_type, file_type;
init_daemon_domain(battery_mitigation)
get_prop(battery_mitigation, boot_status_prop)
get_prop(battery_mitigation, vendor_startup_bugreport_requested_prop)
set_prop(battery_mitigation, vendor_mitigation_ready_prop)
hal_client_domain(battery_mitigation, hal_thermal);

View file

@ -39,3 +39,5 @@ vendor_internal_prop(vendor_telephony_app_prop)
# Battery Mitigation
vendor_internal_prop(vendor_mitigation_ready_prop)
vendor_internal_prop(vendor_brownout_boot_reason_prop)
vendor_internal_prop(vendor_startup_bugreport_requested_prop)

View file

@ -109,3 +109,5 @@ vendor.config.debug. u:object_r:vendor_telephony_app_prop:
# Battery Mitigation
vendor.brownout.mitigation.ready u:object_r:vendor_mitigation_ready_prop:s0
vendor.brownout_boot_reason u:object_r:vendor_brownout_boot_reason_prop:s0
vendor.startup_bugreport_requested u:object_r:vendor_startup_bugreport_requested_prop:s0

View file

@ -35,3 +35,7 @@ set_prop(vendor_init, vendor_battery_defender_prop)
# Display
set_prop(vendor_init, vendor_display_prop)
# Battery Mitigation
set_prop(vendor_init, vendor_brownout_boot_reason_prop)
set_prop(vendor_init, vendor_startup_bugreport_requested_prop)