| /openbmc/phosphor-fan-presence/control/json/triggers/ |
| H A D | signal.cpp | 42 void subscribe(const std::string& match, SignalPkg&& signalPkg, in subscribe() function 113 subscribe(match, std::move(signalPkg), isSameSig, mgr); in propertiesChanged() 137 subscribe(match, std::move(signalPkg), isSameSig, mgr); in interfacesAdded() 161 subscribe(match, std::move(signalPkg), isSameSig, mgr); in interfacesRemoved() 195 subscribe(match, std::move(signalPkg), isSameSig, mgr); in nameOwnerChanged() 231 subscribe(match, std::move(signalPkg), isSameSig, mgr); in member()
|
| H A D | signal.hpp | 43 void subscribe(const std::string& match, SignalPkg&& pkg,
|
| /openbmc/dbus-sensors/src/tests/ |
| H A D | test_MCTPReactor.cpp | 38 MOCK_METHOD(void, subscribe, 124 EXPECT_CALL(*endpoint, subscribe(testing::_, testing::_, testing::_)) in TEST_F() 153 EXPECT_CALL(*endpoint, subscribe(testing::_, testing::_, testing::_)) in TEST_F() 187 EXPECT_CALL(*endpoint, subscribe(testing::_, testing::_, testing::_)) in TEST_F() 231 EXPECT_CALL(*iep, subscribe(testing::_, testing::_, testing::_)) in TEST() 254 EXPECT_CALL(*rep, subscribe(testing::_, testing::_, testing::_)) in TEST()
|
| /openbmc/openbmc-test-automation/bin/ |
| H A D | event_notification_util.py | 55 event_notifications = my_event.subscribe(dbus_path, enable_trace)
|
| /openbmc/openbmc/meta-openembedded/meta-networking/recipes-connectivity/nanomsg/ |
| H A D | nng_1.7.3.bb | 2 …imple API to solve common recurring messaging problems, such as publish/subscribe, RPC-style reque…
|
| /openbmc/dbus-sensors/src/mctp/ |
| H A D | MCTPEndpoint.hpp | 115 virtual void subscribe(Event&& degraded, Event&& available, 221 void subscribe(Event&& degraded, Event&& available,
|
| H A D | MCTPReactor.cpp | 38 ep->subscribe( in trackEndpoint()
|
| H A D | MCTPEndpoint.cpp | 280 void MCTPDEndpoint::subscribe(Event&& degraded, Event&& available, in subscribe() function in MCTPDEndpoint
|
| /openbmc/openbmc-test-automation/lib/ |
| H A D | event_notification.py | 61 def subscribe(self, dbus_path, enable_trace=False): member in event_notification
|
| /openbmc/openbmc/meta-openembedded/meta-networking/recipes-connectivity/mosquitto/ |
| H A D | mosquitto_2.0.20.bb | 6 publish/subscribe model. "
|
| /openbmc/openbmc/poky/meta/files/common-licenses/ |
| H A D | OPUBL-1.0 | 71 To subscribe to the Open Publication Authors' List: 72 Send E-mail to opal-request@opencontent.org with the word "subscribe" in the body.
|
| H A D | TORQUE-1.1 | 4 …mmunity of TORQUE users at torqueusers@supercluster.org. Users can also subscribe to the user mail…
|
| H A D | CECILL-2.1 | 190 undertakes to have the transferees subscribe to the obligations set
|
| /openbmc/docs/ |
| H A D | rest-api.md | 335 It is possible to subscribe to events, of interest, occurring on the BMC. The 347 `<BMC IP>/subscribe`. 350 var ws = new WebSocket("wss://<BMC IP>/subscribe");
|
| /openbmc/openbmc/meta-arm/ |
| H A D | README.md | 40 To subscribe to the meta-arm mailing list, please go to
|
| /openbmc/docs/designs/ |
| H A D | psu-firmware-update.md | 147 1. On start, the service will subscribe to the PropertiesChanged signal to the 148 PSU object path to monitor the PSU presence status. (Or maybe subscribe the
|
| H A D | redfish-eventservice.md | 88 Redfish event service provides a way to subscribe to specific kinds of Events, 460 2. Push style events(HTTP/HTTPS): It covers how to subscribe for Push style 668 re-subscribe for events. This is requirement as per current redfish 709 and Client must re-subscribe for SSE events using "ServerSentEventUri", 842 subscribe for the events. The monitor and formatter resources (both Event log 1024 2. Subscription: Client can subscribe for events on BMC using below 1136 external system and subscribe to BMC with the subscription details along with 1190 "Use 'http://<IP>:5000/events' as destination to subscribe for BMC events",
|
| H A D | multi-host-postcode.md | 169 subscribe to `PropertiesChanged` signals on this object to get the updates.
|
| H A D | target-fail-monitoring.md | 141 This application will not register any interfaces on D-Bus but will subscribe to
|
| H A D | bmc-service-failure-debug-and-recovery.md | 475 - The state-manager service-monitor will subscribe to signals for service
|
| /openbmc/openbmc/poky/documentation/ref-manual/ |
| H A D | resources.rst | 62 and announcements. To subscribe to one of the following mailing lists,
|
| /openbmc/openbmc/poky/documentation/dev-manual/ |
| H A D | security-subjects.rst | 59 This is a public mailing list for anyone to subscribe to. This list is an
|
| /openbmc/phosphor-dbus-interfaces/yaml/xyz/openbmc_project/Certs/ |
| H A D | README.md | 32 - Applications should subscribe the xyz.openbmc_project.Certs.Manager to see any
|
| /openbmc/phosphor-fan-presence/docs/control/ |
| H A D | events.md | 124 Signal triggers subscribe to certain D-Bus signals for each member of its 756 to subscribe to propertiesChanged for them all.
|
| /openbmc/qemu/docs/devel/ |
| H A D | submitting-a-patch.rst | 28 You do not have to subscribe to post (list policy is to reply-to-all to 31 ideas from other posts. If you do subscribe, be prepared for a high
|