| /openbmc/sdbusplus/tools/sdbusplus/templates/ |
| H A D | events.md.mako | 1 ${"##"} Events
12 ${"###"} Events
|
| H A D | events.hpp.mako | 1 /* Events for ${events.name}
|
| /openbmc/openbmc-test-automation/gui/test/server_overview/ |
| H A D | test_obmc_gui_server_overview.robot | 66 Verify High Priority Events Should Display At OBMC Power Off State
74 Verify High Priority Events Can Be Operated At OBMC Power Off State
75 [Documentation] Will open the "High Priority Events".
120 Verify High Priority Events Can Be Operated At OBMC Power Running State
121 [Documentation] Will open the "High Priority Events"
|
| /openbmc/intel-ipmi-oem/ |
| H A D | README.md | 24 - Extended parsing of IPMI Platform Events`[4]`
31 4. [Intel Platform Events parsing](docs/Intel_IPMI_Platform_Events.md)
|
| /openbmc/phosphor-inventory-manager/ |
| H A D | manager.hpp | 133 using Events = std::vector<EventInfo>; typedef in phosphor::inventory::manager::Manager
210 static const Events _events;
|
| H A D | generated.mako.cpp | 49 const Manager::Events Manager::_events{
|
| /openbmc/linux/Documentation/admin-guide/perf/ |
| H A D | qcom_l2_pmu.rst | 17 Events can be envisioned as a 2-dimensional array. Each column represents
22 Events are specified as 0xCCG, where CC is 2 hex digits specifying
|
| /openbmc/qemu/tests/qapi-schema/ |
| H A D | doc-invalid-return.json | 1 # Events can't have 'Returns' section
|
| /openbmc/linux/Documentation/devicetree/bindings/goldfish/ |
| H A D | events.txt | 1 Android Goldfish Events Keypad
|
| /openbmc/docs/designs/ |
| H A D | redfish-eventservice.md | 88 Redfish event service provides a way to subscribe to specific kinds of Events,
99 2. Server-Sent Events (SSE): Client opens an SSE connection to the service by
109 - Server Sent-Events (Section 12.5)
590 HttpHeaders and send the Events over network using http protocol for the
643 2. Server-Sent Events (SSE): The EventDestination resource of the subscription
669 "DeliveryRetryIntervalSeconds". In case of Push Style Events if send fails due
737 ### Server-Sent Events (SSE):
739 Server-Sent Events (SSE) is a server push technology enabling a browser to
741 Events EventSource API is standardized as part of HTML5 by the W3C.
743 Server-Sent Events is a standard describing how servers can initiate data
[all …]
|
| /openbmc/qemu/python/qemu/qmp/ |
| H A D | qmp_client.py | 24 from .events import Events
158 class QMPClient(AsyncProtocol[Message], Events):
208 Events.__init__(self)
|
| /openbmc/openbmc/meta-openembedded/meta-python/recipes-devtools/python/python3-inotify/ |
| H A D | new-test-inotify.patch | 93 + raise Exception("Events not correct.")
135 + raise Exception("Events not correct.")
197 + raise Exception("Events not correct.")
263 + raise Exception("Events not correct.")
394 + raise Exception("Events not correct.")
476 + raise Exception("Events not correct.")
545 + raise Exception("Events not correct.")
583 + raise Exception("Events not correct.")
|
| /openbmc/linux/Documentation/driver-api/surface_aggregator/clients/ |
| H A D | cdev.rst | 28 Receiving Events
31 Events can be received by reading from the device-file. The are represented by
185 Events are not automatically disabled when the device file is closed. This must
195 Note that this will not unregister any notifiers. Events may still be received
|
| H A D | dtx.rst | 23 different contexts. Events are sent by the EC upon some internal state
276 Events section in User-Space Interface Documentation
279 Events can be received by reading from the device file. They are disabled by
550 Enable events for the current file descriptor. Events can be obtained by
551 reading from the device, if enabled. Events are disabled by default.
558 Disable events for the current file descriptor. Events can be obtained by
559 reading from the device, if enabled. Events are disabled by default.
|
| /openbmc/openbmc-test-automation/gui/gui_test/logs_and_services_menu/ |
| H A D | test_event_logs_sub_menu.robot | 98 Select All Events
106 Select And Verify Default UTC Timezone For Events
191 Select All Events
248 Select All Events
|
| /openbmc/linux/Documentation/power/regulator/ |
| H A D | regulator.rst | 25 Regulator Events
|
| /openbmc/linux/fs/notify/inotify/ |
| H A D | Kconfig | 9 directories via a single open fd. Events are read from the file
|
| /openbmc/linux/Documentation/trace/ |
| H A D | events-msr.rst | 2 MSR Trace Events
|
| H A D | tracepoint-analysis.rst | 2 Notes on Analysing Behaviour Using Events and Tracepoints
23 2. Listing Available Events
52 3. Enabling Events
121 Events can be activated and tracked for the duration of a process on a local
|
| /openbmc/intel-ipmi-oem/docs/ |
| H A D | Intel_IPMI_Platform_Events.md | 1 # Intel IPMI Platform Events parsing
3 In many cases Manufacturers-specific IPMI Platfrom Events are stored in binary
6 IPMI Platform Events in a human readable form by defining a generic framework
30 human-readable format. IPMI Platform Events is one type of these messages, used
33 Part of IPMI Platform Events are standarized and described in the specification
|
| /openbmc/qemu/docs/devel/testing/ |
| H A D | blkdebug.rst | 59 ``flush_to_os``, ``flush_to_disk``). See `Events`_ for
86 Events chapter
155 ``flush_to_os`, ``flush_to_disk``). See `Events`_ for
|
| /openbmc/linux/Documentation/driver-api/usb/ |
| H A D | dwc3.rst | 55 9. Trace Events for debugging
130 DWC3 relies exclusively on Trace Events for debugging. Everything is
134 In order to capture DWC3's Trace Events you should run the following
184 Anyway, there isn't much to say here other than Trace Events will be
533 Trace Events
552 bugs. Because of that, DWC3 offers two Trace Events (one for argument
558 Interrupt Events argument
|
| /openbmc/linux/Documentation/input/devices/ |
| H A D | rotary-encoder.rst | 46 Events / state machine
50 rotational direction based on the last stable state. Events are reported in
|
| /openbmc/linux/drivers/w1/ |
| H A D | Kconfig | 24 1. Events. They are generated each time new master or slave device found
|
| /openbmc/phosphor-dbus-monitor/ |
| H A D | meson.build | 15 conf_data.set_quoted('BUSNAME_EVENT', 'xyz.openbmc_project.Events')
|