Home
last modified time | relevance | path

Searched refs:triggers (Results 1 – 5 of 5) sorted by relevance

/system/core/init/
Daction.cpp193 std::vector<std::string> triggers; in BuildTriggersString() local
196 triggers.emplace_back(trigger_name + '=' + trigger_value); in BuildTriggersString()
199 triggers.emplace_back(event_trigger_); in BuildTriggersString()
202 return Join(triggers, " && "); in BuildTriggersString()
Daction_parser.cpp115 std::vector<std::string> triggers(args.begin() + 1, args.end()); in ParseSection() local
116 if (triggers.size() < 1) { in ParseSection()
133 … if (auto result = ParseTriggers(triggers, action_subcontext, &event_trigger, &property_triggers); in ParseSection()
DREADME.md303 Triggers are subdivided into event triggers and property triggers.
305 Event triggers are strings triggered by the 'trigger' command or by
309 Property triggers are strings triggered when a named property changes
312 'property:<name>=\*' respectively. Property triggers are additionally
316 An Action can have multiple property triggers but may only have one
/system/core/rootdir/
Dinit.usb.rc14 # adbd is controlled via property triggers in init.<platform>.usb.rc
/system/bt/doc/
Dpower_management.md148 triggers `bta_dm_pm_btm_status`, with the timeout field set to TRUE. HCI