| /linux/kernel/trace/rv/ |
| H A D | rv_reactors.c | 177 mon->react = reactor->react; in monitor_swap_reactors_single()
438 .react = rv_nop_reaction
471 if (!rv_reacting_on() || !monitor->react) in rv_react()
477 monitor->react(msg, args); in rv_react()
|
| H A D | reactor_panic.c | 24 .react = rv_panic_reaction
|
| H A D | reactor_printk.c | 23 .react = rv_printk_reaction
|
| /linux/include/linux/ |
| H A D | rv.h | 95 __printf(1, 0) void (*react)(const char *msg, va_list args);
109 __printf(1, 0) void (*react)(const char *msg, va_list args);
|
| /linux/include/rv/ |
| H A D | da_monitor.h | 31 static void react(enum states curr_state, enum events event) in react() function
119 react(curr_state, event); in da_event()
160 react(curr_state, event); in da_event()
|
| /linux/Documentation/devicetree/bindings/cpufreq/ |
| H A D | brcm,stb-avs-cpu-freq.txt | 12 so a driver can react to interrupts generated by the AVS CPU whenever a command
|
| /linux/Documentation/i2c/ |
| H A D | i2c-stub.rst | 13 driver, which will then only react to SMBus commands to these addresses.
|
| H A D | slave-testunit-backend.rst | 224 hardware and, thus, may not be able to react to the response of the host fast
|
| /linux/Documentation/trace/rv/ |
| H A D | runtime-verification.rst | 55 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
|
| /linux/Documentation/usb/ |
| H A D | raw-gadget.rst | 57 Raw Gadget and react to those depending on what kind of USB gadget must
|
| /linux/Documentation/input/devices/ |
| H A D | yealink.rst | 206 is not initialized and does not react to any actions.
|
| /linux/Documentation/driver-api/ |
| H A D | rfkill.rst | 16 The subsystem also provides the ability to react on button presses and
|
| /linux/Documentation/sound/cards/ |
| H A D | maya44.rst | 50 - The level meters ("multi track") in 'alsamixer' do not seem to react to signals in (if this is a …
|
| /linux/Documentation/networking/ |
| H A D | phy.rst | 156 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
|
| /linux/arch/arm/boot/dts/ti/omap/ |
| H A D | am3874-iceboard.dts | 354 /* The PLL doesn't react well to the SPI controller reset, so
|
| /linux/Documentation/power/ |
| H A D | freezing-of-tasks.rst | 31 wakes up all the kernel threads. All freezable tasks must react to that by
|
| /linux/Documentation/userspace-api/fwctl/ |
| H A D | fwctl.rst | 131 driver can react to the device configuration at function reset/driver load
|
| /linux/Documentation/hwmon/ |
| H A D | pmbus-core.rst | 117 necessary for chips which react badly if non-supported commands are executed,
|
| /linux/Documentation/process/ |
| H A D | management-style.rst | 193 Some people react badly to smart people. Others take advantage of them.
|
| H A D | embargoed-hardware-issues.rst | 212 the incident team immediately. If the disclosing party does not react
|
| /linux/Documentation/driver-api/media/ |
| H A D | cec-core.rst | 238 Your adapter driver will also have to react to events (typically interrupt
|
| /linux/Documentation/mm/ |
| H A D | hmm.rst | 426 and system react under memory pressure in the presence of device memory before
|
| /linux/Documentation/admin-guide/ |
| H A D | reporting-issues.rst | 161 outcome in one way or the other. Thus react publicly and in a timely manner
1279 outcome in one way or the other. Thus react publicly and in a timely manner
1440 react somehow to every issue report, but they are only obliged to fix those
|
| /linux/Documentation/driver-api/pm/ |
| H A D | devices.rst | 752 should recognize such situations and react to them appropriately, but the
|
| /linux/Documentation/admin-guide/laptops/ |
| H A D | thinkpad-acpi.rst | 1250 it is normal for the EC to take several seconds to react to fan
|