Home
last modified time | relevance | path

Searched refs:react (Results 1 – 25 of 40) sorted by relevance

12

/openbmc/linux/include/linux/
H A Drv.h41 void (*react)(char *msg); member
53 void (*react)(char *msg); member
/openbmc/linux/kernel/trace/rv/
H A Drv_reactors.c180 mdef->monitor->react = rdef->reactor->react; in monitor_swap_reactors()
479 .react = rv_nop_reaction
H A Dreactor_printk.c23 .react = rv_printk_reaction
H A Dreactor_panic.c24 .react = rv_panic_reaction
/openbmc/phosphor-fan-presence/control/config_files/p10bmc/com.ibm.Hardware.Chassis.Model.Rainier4U/
H A Devents.json1439 // dbus. There's no need to react to their removal.
/openbmc/phosphor-fan-presence/control/config_files/p10bmc/com.ibm.Hardware.Chassis.Model.Bonnell/
H A Devents.json534 // dbus. There's no need to react to their removal.
/openbmc/phosphor-fan-presence/control/config_files/p10bmc/com.ibm.Hardware.Chassis.Model.Rainier1S4U/
H A Devents.json1124 // dbus. There's no need to react to their removal.
/openbmc/phosphor-fan-presence/control/config_files/p10bmc/com.ibm.Hardware.Chassis.Model.Rainier2U/
H A Devents.json1626 // dbus. There's no need to react to their removal.
/openbmc/phosphor-fan-presence/control/config_files/p10bmc/com.ibm.Hardware.Chassis.Model.BlueRidge2U/
H A Devents.json1626 // dbus. There's no need to react to their removal.
/openbmc/phosphor-fan-presence/control/config_files/p10bmc/com.ibm.Hardware.Chassis.Model.Everest/
H A Devents.json2122 // dbus. There's no need to react to their removal.
/openbmc/linux/include/rv/
H A Dda_monitor.h36 if (rv_##name.react) \
37 rv_##name.react(msg); \
/openbmc/openbmc/poky/meta/recipes-support/consolekit/
H A Dconsolekit_0.4.6.bb2 DESCRIPTION = "It provides a mechanism for software to react to changes \
/openbmc/linux/Documentation/devicetree/bindings/cpufreq/
H A Dbrcm,stb-avs-cpu-freq.txt12 so a driver can react to interrupts generated by the AVS CPU whenever a command
/openbmc/phosphor-dbus-interfaces/yaml/xyz/openbmc_project/Control/
H A DREADME.msl.md12 requirements on how the setting is used; implementations are free to react to
/openbmc/linux/Documentation/i2c/
H A Di2c-stub.rst13 driver, which will then only react to SMBus commands to these addresses.
/openbmc/linux/Documentation/trace/rv/
H A Druntime-verification.rst55 react to an unexpected event. The forms of reaction can vary from logging the
89 file. In contrast, *synchronous online* method can react at the exact moment
/openbmc/linux/Documentation/usb/
H A Draw-gadget.rst57 Raw Gadget and react to those depending on what kind of USB gadget must
/openbmc/linux/Documentation/input/devices/
H A Dyealink.rst206 is not initialized and does not react to any actions.
/openbmc/linux/Documentation/driver-api/
H A Drfkill.rst16 The subsystem also provides the ability to react on button presses and
/openbmc/linux/Documentation/sound/cards/
H A Dmaya44.rst50 - The level meters ("multi track") in 'alsamixer' do not seem to react to signals in (if this is a …
/openbmc/bmcweb/
H A DAGGREGATION.md169 then forward it to the client. It is up to the client to determine how to react
/openbmc/linux/Documentation/networking/
H A Dphy.rst156 the link state changes, so it can react.
162 allowing the network driver to react first to any changes before the PAL
175 First, you need a function to react to changes in the link state. This
/openbmc/qemu/docs/specs/
H A Dvmgenid.rst18 guest operating system notices the change, and is then able to react as
/openbmc/linux/arch/arm/boot/dts/ti/omap/
H A Dam3874-iceboard.dts354 /* The PLL doesn't react well to the SPI controller reset, so
/openbmc/linux/Documentation/hwmon/
H A Dpmbus-core.rst117 necessary for chips which react badly if non-supported commands are executed,

12