Home
last modified time | relevance | path

Searched full:react (Results 1 – 25 of 126) sorted by relevance

123456

/linux-6.14.4/tools/testing/selftests/firmware/
Dfw_fallback.sh29 # Give kernel a chance to react.
56 # Give kernel a chance to react.
85 # Give kernel a chance to react.
118 # Give kernel a chance to react.
/linux-6.14.4/include/linux/
Drv.h41 void (*react)(char *msg); member
53 void (*react)(char *msg); member
Dlis3lv02d.h45 * pass filtered data which makes it react to the changes in the acceleration.
/linux-6.14.4/drivers/gpu/drm/amd/display/modules/hdcp/
Dhdcp1_transition.c77 * not ready. give it more time to react before retry. in mod_hdcp_hdcp1_transition()
224 * not ready. give it more time to react before retry. in mod_hdcp_hdcp1_dp_transition()
285 * give it more time to react. in mod_hdcp_hdcp1_dp_transition()
/linux-6.14.4/kernel/trace/rv/
Drv_reactors.c180 mdef->monitor->react = rdef->reactor->react; in monitor_swap_reactors()
478 .react = rv_nop_reaction
Dreactor_panic.c24 .react = rv_panic_reaction
Dreactor_printk.c23 .react = rv_printk_reaction
/linux-6.14.4/drivers/hwmon/
Dhih6130.c101 * much longer to react to a change in external conditions. How quickly in hih6130_update_measurements()
107 * than it can react against better response times in conditions more in hih6130_update_measurements()
/linux-6.14.4/Documentation/trace/rv/
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
/linux-6.14.4/drivers/input/serio/
Di8042.h29 * This is in 50us units, the time we wait for the i8042 to react. This
/linux-6.14.4/Documentation/i2c/
Di2c-stub.rst13 driver, which will then only react to SMBus commands to these addresses.
/linux-6.14.4/drivers/input/
Dapm-power.c34 /* only react on key down events */ in apmpower_event()
/linux-6.14.4/Documentation/devicetree/bindings/cpufreq/
Dbrcm,stb-avs-cpu-freq.txt12 so a driver can react to interrupts generated by the AVS CPU whenever a command
/linux-6.14.4/Documentation/usb/
Draw-gadget.rst57 Raw Gadget and react to those depending on what kind of USB gadget must
/linux-6.14.4/include/rv/
Dda_monitor.h36 if (rv_##name.react) \
37 rv_##name.react(msg); \
/linux-6.14.4/arch/x86/kernel/cpu/microcode/
Dcore.c615 * must be online as well because they still react to NMIs when they are
622 * As soft-offlined CPUs still react on NMIs, the SMT sibling
646 * with interrupts disabled, but they still react on NMIs in setup_cpus()
/linux-6.14.4/arch/arm/kernel/
Dmachine_kexec.c125 pr_warn("Non-crashing CPUs did not react to IPI\n"); in crash_smp_send_stop()
/linux-6.14.4/tools/testing/selftests/net/forwarding/
Dmirror_gre_changes.sh7 # Test how mirrors to gretap and ip6gretap react to changes to relevant
/linux-6.14.4/net/6lowpan/
Dndisc.c104 /* react on overrides only. TODO check if this is really right. */ in lowpan_ndisc_update()
/linux-6.14.4/Documentation/driver-api/
Drfkill.rst16 The subsystem also provides the ability to react on button presses and
/linux-6.14.4/Documentation/networking/
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
/linux-6.14.4/arch/mips/pci/
Dops-rc32434.c111 * Certain devices react delayed at device scan time, this in read_config_dword()
/linux-6.14.4/Documentation/sound/cards/
Dmaya44.rst50 - The level meters ("multi track") in 'alsamixer' do not seem to react to signals in (if this is a …
/linux-6.14.4/drivers/parisc/
Dpower.c31 /* how long does the power button needs to be down until we react ? */
/linux-6.14.4/Documentation/input/devices/
Dyealink.rst206 is not initialized and does not react to any actions.

123456