Searched hist:"926 df663de38c4ab643a7d7f1556b2a8dd3e5d9f" (Results 1 – 7 of 7) sorted by relevance
| /openbmc/phosphor-fan-presence/control/ |
| H A D | triggers.hpp | diff 926df663de38c4ab643a7d7f1556b2a8dd3e5d9f Tue Oct 09 09:51:12 CDT 2018 Matthew Barth <msbarth@us.ibm.com> Separate handlers for signals and method calls
Signals and method calls have different parameter structures. When the
associated event trigger is chosen, what's generated to retrieve the
dbus data is specific to that trigger event. For signals, the data is
read from the given signal message. A method call is method specific and
is called to be done against all of the members within the event group.
Change-Id: I92cbdbf05852fbaa7f1b56ed518e30278cdf840b
Signed-off-by: Matthew Barth <msbarth@us.ibm.com>
|
| H A D | triggers.cpp | diff 926df663de38c4ab643a7d7f1556b2a8dd3e5d9f Tue Oct 09 09:51:12 CDT 2018 Matthew Barth <msbarth@us.ibm.com> Separate handlers for signals and method calls
Signals and method calls have different parameter structures. When the
associated event trigger is chosen, what's generated to retrieve the
dbus data is specific to that trigger event. For signals, the data is
read from the given signal message. A method call is method specific and
is called to be done against all of the members within the event group.
Change-Id: I92cbdbf05852fbaa7f1b56ed518e30278cdf840b
Signed-off-by: Matthew Barth <msbarth@us.ibm.com>
|
| H A D | functor.hpp | diff 926df663de38c4ab643a7d7f1556b2a8dd3e5d9f Tue Oct 09 09:51:12 CDT 2018 Matthew Barth <msbarth@us.ibm.com> Separate handlers for signals and method calls
Signals and method calls have different parameter structures. When the
associated event trigger is chosen, what's generated to retrieve the
dbus data is specific to that trigger event. For signals, the data is
read from the given signal message. A method call is method specific and
is called to be done against all of the members within the event group.
Change-Id: I92cbdbf05852fbaa7f1b56ed518e30278cdf840b
Signed-off-by: Matthew Barth <msbarth@us.ibm.com>
|
| H A D | types.hpp | diff 926df663de38c4ab643a7d7f1556b2a8dd3e5d9f Tue Oct 09 09:51:12 CDT 2018 Matthew Barth <msbarth@us.ibm.com> Separate handlers for signals and method calls
Signals and method calls have different parameter structures. When the
associated event trigger is chosen, what's generated to retrieve the
dbus data is specific to that trigger event. For signals, the data is
read from the given signal message. A method call is method specific and
is called to be done against all of the members within the event group.
Change-Id: I92cbdbf05852fbaa7f1b56ed518e30278cdf840b
Signed-off-by: Matthew Barth <msbarth@us.ibm.com>
|
| H A D | gen-fan-zone-defs.py | diff 926df663de38c4ab643a7d7f1556b2a8dd3e5d9f Tue Oct 09 09:51:12 CDT 2018 Matthew Barth <msbarth@us.ibm.com> Separate handlers for signals and method calls
Signals and method calls have different parameter structures. When the
associated event trigger is chosen, what's generated to retrieve the
dbus data is specific to that trigger event. For signals, the data is
read from the given signal message. A method call is method specific and
is called to be done against all of the members within the event group.
Change-Id: I92cbdbf05852fbaa7f1b56ed518e30278cdf840b
Signed-off-by: Matthew Barth <msbarth@us.ibm.com>
|
| /openbmc/phosphor-fan-presence/control/templates/ |
| H A D | defs.mako | diff 926df663de38c4ab643a7d7f1556b2a8dd3e5d9f Tue Oct 09 09:51:12 CDT 2018 Matthew Barth <msbarth@us.ibm.com> Separate handlers for signals and method calls
Signals and method calls have different parameter structures. When the
associated event trigger is chosen, what's generated to retrieve the
dbus data is specific to that trigger event. For signals, the data is
read from the given signal message. A method call is method specific and
is called to be done against all of the members within the event group.
Change-Id: I92cbdbf05852fbaa7f1b56ed518e30278cdf840b
Signed-off-by: Matthew Barth <msbarth@us.ibm.com>
|
| H A D | fan_zone_defs.mako.cpp | diff 926df663de38c4ab643a7d7f1556b2a8dd3e5d9f Tue Oct 09 09:51:12 CDT 2018 Matthew Barth <msbarth@us.ibm.com> Separate handlers for signals and method calls
Signals and method calls have different parameter structures. When the
associated event trigger is chosen, what's generated to retrieve the
dbus data is specific to that trigger event. For signals, the data is
read from the given signal message. A method call is method specific and
is called to be done against all of the members within the event group.
Change-Id: I92cbdbf05852fbaa7f1b56ed518e30278cdf840b
Signed-off-by: Matthew Barth <msbarth@us.ibm.com>
|