Donate to e Foundation | Murena handsets with /e/OS | Own a part of Murena! Learn more

Commit 419269b8 authored by Jack Chen's avatar Jack Chen
Browse files

init: Supplement description to property action usage



Early set properties in DT or over the command-lines do not trigger
property-change events until boot stage.

Bug: 383738769
Test: After changing the action command line to tie to `early-boot`
event, the action is triggered earlier
Signed-off-by: default avatarJack Chen <zenghuchen@google.com>
Merged-In: I000fcbf09f35cbaccc7517a3962fa4889b1d90be
Change-Id: I000fcbf09f35cbaccc7517a3962fa4889b1d90be
parent 642252a4
Loading
Loading
Loading
Loading
+6 −0
Original line number Diff line number Diff line
@@ -486,6 +486,12 @@ at three times:
   2. Any time that property a transitions to value b, while property c already equals d.
   3. Any time that property c transitions to value d, while property a already equals b.

Note that, for bootloader-provided properties (ro.boot.*), their action cannot be
auto-triggered until `boot` stage. If they need to be triggered earlier, like at `early-boot`
stage, they should be tied to the `event`. For example:

`on early-boot && property:a=b`.


Trigger Sequence
----------------