Home
last modified time | relevance | path

Searched full:triggers (Results 1 – 25 of 1174) sorted by relevance

12345678910>>...47

/openbmc/bmcweb/redfish-core/schema/dmtf/csdl/
H A DTriggers_v1.xml4 <!--# Redfish Schema: Triggers v1.4.0 -->
34 <Schema xmlns="http://docs.oasis-open.org/odata/ns/edm" Namespace="Triggers">
38 <EntityType Name="Triggers" BaseType="Resource.v1_0_0.Resource" Abstract="true">
39 …<Annotation Term="OData.Description" String="The `Triggers` schema describes a trigger condition t…
49 … <Annotation Term="OData.Description" String="Triggers can be updated to configure them."/>
55 <Annotation Term="OData.Description" String="Triggers can be deleted."/>
60 <String>/redfish/v1/TelemetryService/Triggers/{TriggersId}</String>
66 <Schema xmlns="http://docs.oasis-open.org/odata/ns/edm" Namespace="Triggers.v1_0_0">
70 <EntityType Name="Triggers" BaseType="Triggers.Triggers">
71 <Property Name="MetricType" Type="Triggers.v1_0_0.MetricTypeEnum">
[all …]
H A DTriggersCollection_v1.xml27 <edmx:Include Namespace="Triggers"/>
37 … <Annotation Term="OData.Description" String="The collection of `Triggers` resource instances."/>
38 …iption" String="This resource shall represent a resource collection of `Triggers` instances for a …
42 …<Annotation Term="OData.Description" String="Create triggers through a `POST` to the trigger colle…
57 <String>/redfish/v1/TelemetryService/Triggers</String>
60 <NavigationProperty Name="Members" Type="Collection(Triggers.Triggers)">
/openbmc/bmcweb/redfish-core/schema/dmtf/installed/
H A DTriggers_v1.xml4 <!--# Redfish Schema: Triggers v1.4.0 -->
34 <Schema xmlns="http://docs.oasis-open.org/odata/ns/edm" Namespace="Triggers">
38 <EntityType Name="Triggers" BaseType="Resource.v1_0_0.Resource" Abstract="true">
39 …<Annotation Term="OData.Description" String="The `Triggers` schema describes a trigger condition t…
49 … <Annotation Term="OData.Description" String="Triggers can be updated to configure them."/>
55 <Annotation Term="OData.Description" String="Triggers can be deleted."/>
60 <String>/redfish/v1/TelemetryService/Triggers/{TriggersId}</String>
66 <Schema xmlns="http://docs.oasis-open.org/odata/ns/edm" Namespace="Triggers.v1_0_0">
70 <EntityType Name="Triggers" BaseType="Triggers.Triggers">
71 <Property Name="MetricType" Type="Triggers.v1_0_0.MetricTypeEnum">
[all …]
H A DTriggersCollection_v1.xml27 <edmx:Include Namespace="Triggers"/>
37 … <Annotation Term="OData.Description" String="The collection of `Triggers` resource instances."/>
38 …iption" String="This resource shall represent a resource collection of `Triggers` instances for a …
42 …<Annotation Term="OData.Description" String="Create triggers through a `POST` to the trigger colle…
57 <String>/redfish/v1/TelemetryService/Triggers</String>
60 <NavigationProperty Name="Members" Type="Collection(Triggers.Triggers)">
/openbmc/linux/Documentation/iio/
H A Diio_configfs.rst10 triggers).
30 3. Software triggers
33 One of the IIO default configfs groups is the "triggers" group. It is
35 under /config/iio/triggers.
37 IIO software triggers implementation offers support for creating multiple
76 Each trigger type has its own directory under /config/iio/triggers. Loading
78 /config/iio/triggers/trig-sample.
84 3.1 Hrtimer triggers creation and destruction
88 users to create hrtimer triggers under /config/iio/triggers/hrtimer.
92 $ mkdir /config/iio/triggers/hrtimer/instance1
[all …]
/openbmc/phosphor-fan-presence/control/
H A Dgen-fan-zone-defs.py176 if ("timer" in event["triggers"]) and (
177 event["triggers"]["timer"] is not None
180 e += "\t" + event["triggers"]["timer"]["interval"] + ",\n"
181 e += "\t" + event["triggers"]["timer"]["type"] + "\n"
184 if ("signals" in event["triggers"]) and (
185 event["triggers"]["signals"] is not None
187 for s in event["triggers"]["signals"]:
222 if "init" in event["triggers"]:
223 for i in event["triggers"]["init"]:
595 # Add event triggers
[all …]
H A Dmeson.build22 './json/triggers'
49 'json/triggers/init.cpp',
50 'json/triggers/parameter.cpp',
51 'json/triggers/signal.cpp',
52 'json/triggers/timer.cpp'
81 'triggers.cpp',
/openbmc/bmcweb/redfish-core/lib/
H A Dtrigger.hpp6 #include "generated/enums/triggers.hpp"
43 inline triggers::TriggerActionEnum
49 return triggers::TriggerActionEnum::RedfishMetricReport; in toRedfishTriggerAction()
54 return triggers::TriggerActionEnum::RedfishEvent; in toRedfishTriggerAction()
59 return triggers::TriggerActionEnum::LogToLogService; in toRedfishTriggerAction()
61 return triggers::TriggerActionEnum::Invalid; in toRedfishTriggerAction()
160 inline triggers::ThresholdActivation
165 return triggers::ThresholdActivation::Either; in toRedfishActivation()
171 return triggers::ThresholdActivation::Decreasing; in toRedfishActivation()
177 return triggers::ThresholdActivation::Increasing; in toRedfishActivation()
[all …]
/openbmc/phosphor-fan-presence/control/templates/
H A Ddefs.mako97 %if ('timer' in event['triggers']) and \
98 (event['triggers']['timer'] is not None):
100 ${event['triggers']['timer']['interval']},
101 ${event['triggers']['timer']['type']}
104 %if ('signals' in event['triggers']) and \
105 (event['triggers']['signals'] is not None):
106 %for s in event['triggers']['signals']:
128 %if ('init' in event['triggers']):
129 %for i in event['triggers']['init']:
H A Dfan_zone_defs.mako.cpp14 #include "triggers.hpp"
150 %if ('timer' in event['pc']['triggers']) and \
151 (event['pc']['triggers']['timer'] is not None):
153 ${event['pc']['triggers']['pctime']['interval']},
154 ${event['pc']['triggers']['pctime']['type']}
157 %if ('pcsigs' in event['pc']['triggers']) and \
158 (event['pc']['triggers']['pcsigs'] is not None):
159 %for s in event['pc']['triggers']['pcsigs']:
181 %if ('init' in event['pc']['triggers']):
182 %for i in event['pc']['triggers']['init']:
/openbmc/linux/Documentation/trace/coresight/
H A Dcoresight-ect.rst14 individual input and output hardware signals known as triggers to and from
30 The CTI driver enables the programming of the CTI to attach triggers to
34 activating connected output triggers there, unless filtered by the CTI
84 * ``nr_trigger_cons`` : total connections - triggers<N> directories.
88 * ``triggers<N>``: contains list of triggers for an individual connection.
97 triggers<N> directories
103 Each triggers directory has a set of parameters describing the triggers for
127 If a connection has zero signals in either the 'in' or 'out' triggers then
133 This provides an easy way to attach triggers to channels, without needing
180 * ``chan_xtrigs_in``: Read to show the input triggers attached to
[all …]
/openbmc/linux/tools/testing/selftests/powerpc/dexcr/
H A Ddexcr.c30 * If the SPR is not recognised by the hardware it triggers in dexcr_exists()
47 * Just test if a bad hashchk triggers a signal, without checking
53 volatile bool triggers; in hashchk_triggers() local
59 triggers = true; in hashchk_triggers()
61 triggers = false; in hashchk_triggers()
65 return triggers; in hashchk_triggers()
115 * If they differ, an interrupt triggers.
/openbmc/phosphor-fan-presence/control/config_files/p10bmc/com.ibm.Hardware.Chassis.Model.Everest/
H A Devents.json12 "triggers": [ array
56 "triggers": [ array
87 "triggers": [ array
116 "triggers": [ array
145 "triggers": [ array
174 "triggers": [ array
235 "triggers": [ array
305 "triggers": [ array
469 "triggers": [ array
506 "triggers": [ array
[all …]
/openbmc/linux/kernel/trace/
H A Dtrace_events_trigger.c3 * trace_events_trigger - trace event triggers
25 /* make sure current triggers exit before free */ in trigger_data_free()
32 * event_triggers_call - Call triggers associated with a trace event
66 if (list_empty(&file->triggers)) in event_triggers_call()
69 list_for_each_entry_rcu(data, &file->triggers, list) { in event_triggers_call()
121 list_for_each_entry_rcu(data, &file->triggers, list) { in event_triggers_post_call()
140 return seq_list_next(t, &event_file->triggers, pos); in trigger_next()
147 list_for_each_entry_rcu(data, &file->triggers, list, in check_user_trigger()
166 if (list_empty(&event_file->triggers) || !check_user_trigger(event_file)) in trigger_start()
169 return seq_list_start(&event_file->triggers, *pos); in trigger_start()
[all …]
/openbmc/telemetry/src/
H A Dtrigger_manager.cpp66 triggers.erase( in removeTrigger()
67 std::remove_if(triggers.begin(), triggers.end(), in removeTrigger()
69 triggers.end()); in removeTrigger()
110 if (triggers.size() >= maxTriggers) in verifyAddTrigger()
129 triggers, [](const auto& trigger) { return trigger->getId(); }); in addTrigger()
136 triggers.emplace_back(triggerFactory->make( in addTrigger()
140 return *triggers.back(); in addTrigger()
/openbmc/phosphor-fan-presence/control/config_files/p10bmc/com.ibm.Hardware.Chassis.Model.Rainier2U/
H A Devents.json12 "triggers": [ array
66 "triggers": [ array
97 "triggers": [ array
126 "triggers": [ array
155 "triggers": [ array
184 "triggers": [ array
213 "triggers": [ array
242 "triggers": [ array
308 "triggers": [ array
383 "triggers": [ array
[all …]
/openbmc/phosphor-fan-presence/control/config_files/p10bmc/com.ibm.Hardware.Chassis.Model.Rainier4U/
H A Devents.json12 "triggers": [ array
66 "triggers": [ array
126 "triggers": [ array
201 "triggers": [ array
324 "triggers": [ array
361 "triggers": [ array
403 "triggers": [ array
445 "triggers": [ array
487 "triggers": [ array
529 "triggers": [ array
[all …]
/openbmc/phosphor-fan-presence/control/json/
H A Devent.cpp63 // Don't call the powerOn or powerOff triggers in enable()
275 if (!jsonObj.contains("triggers")) in setTriggers()
277 log<level::ERR>("Missing required event triggers list", in setTriggers()
279 throw std::runtime_error("Missing required event triggers list"); in setTriggers()
281 for (const auto& jsonTrig : jsonObj["triggers"]) in setTriggers()
292 auto trigFunc = trigger::triggers.find(tClass); in setTriggers()
293 if (trigFunc != trigger::triggers.end()) in setTriggers()
301 // Construct list of available triggers in setTriggers()
303 std::next(trigger::triggers.begin()), trigger::triggers.end(), in setTriggers()
304 trigger::triggers.begin()->first, [](auto list, auto trig) { in setTriggers()
H A Devent.hpp42 * are made up of groups of sensors, triggers from those sensors, and actions
43 * to be run when a trigger occurs. The triggers and actions configured must be
77 * event triggers, etc...
82 * @brief Call any power on triggers
87 * @brief Call any power off triggers
183 * @brief Parse and set the event's triggers
187 * Sets the list of triggers for the event
/openbmc/linux/drivers/iio/
H A DKconfig30 (e.g. software triggers). For more info see
39 Provides IIO core support for triggers. Currently these
41 buffers. The triggers are effectively a 'capture
61 tristate "Enable software triggers support"
64 Provides IIO core support for software triggers. A software
/openbmc/openbmc/meta-ibm/recipes-phosphor/fans/phosphor-fan-control-events-config/witherspoon/
H A Devents.yaml324 triggers:
339 triggers:
357 triggers:
381 triggers:
433 triggers:
466 triggers:
500 triggers:
534 triggers:
568 triggers:
600 triggers:
[all …]
/openbmc/linux/Documentation/ABI/testing/
H A Dsysfs-bus-coresight-devices-cti23 Description: (Read) Number of devices connected to triggers on this CTI
25 What: /sys/bus/coresight/devices/<cti-name>/triggers<N>/name
31 What: /sys/bus/coresight/devices/<cti-name>/triggers<N>/in_signals
37 What: /sys/bus/coresight/devices/<cti-name>/triggers<N>/in_types
44 What: /sys/bus/coresight/devices/<cti-name>/triggers<N>/out_signals
50 What: /sys/bus/coresight/devices/<cti-name>/triggers<N>/out_types
196 Description: (Read) List of output triggers filtered across all connections.
227 Description: (Read) Read to see input triggers connected to selected view
234 Description: (Read) Read to see output triggers connected to selected view
/openbmc/linux/tools/testing/selftests/ftrace/test.d/ftrace/
H A Dfunc_traceonoff_triggers.tc3 # description: ftrace - test for function traceon/off triggers
6 # The triggers are set within the set_ftrace_filter file
9 # Ftrace allows to add triggers to functions, such as enabling or disabling
13 # This test is designed to test enabling and disabling tracing triggers
167 fail "Tracing on and off triggers still exist"
/openbmc/phosphor-fan-presence/docs/control/
H A Devents.md4 can contain groups, triggers, and actions.
7 Triggers specify when an action should run. Groups specify which D-Bus objects
8 the triggers and actions should operate on.
13 - [Triggers](#triggers)
30 "triggers": [
88 The actions and triggers defined with this group will look at this D-Bus
93 The actions and triggers defined with this group will look at this D-Bus
96 ## Triggers section in events.json
98 There are several classes of triggers, and the JSON configuration is different
103 Init triggers run when fan control events are enabled on fan control startup.
[all …]
/openbmc/bmcweb/redfish-core/schema/dmtf/json-schema-installed/
H A DTriggersCollection.json14 "description": "The collection of `Triggers` resource instances.",
15 …gDescription": "This resource shall represent a resource collection of `Triggers` instances for a …
57 … "$ref": "http://redfish.dmtf.org/schemas/v1/Triggers.json#/definitions/Triggers"
93 "/redfish/v1/TelemetryService/Triggers"

12345678910>>...47