Home
last modified time | relevance | path

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

12345

/linux-5.10/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-5.10/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-5.10/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-5.10/drivers/input/serio/
Di8042.h29 * This is in 50us units, the time we wait for the i8042 to react. This
/linux-5.10/Documentation/i2c/
Di2c-stub.rst13 driver, which will then only react to SMBus commands to these addresses.
/linux-5.10/drivers/input/
Dapm-power.c34 /* only react on key down events */ in apmpower_event()
/linux-5.10/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-5.10/Documentation/usb/
Draw-gadget.rst49 Raw Gadget and react to those depending on what kind of USB device
/linux-5.10/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-5.10/include/linux/
Dlis3lv02d.h45 * pass filtered data which makes it react to the changes in the acceleration.
/linux-5.10/Documentation/driver-api/
Drfkill.rst16 The subsystem also provides the ability to react on button presses and
/linux-5.10/arch/arm/kernel/
Dmachine_kexec.c115 pr_warn("Non-crashing CPUs did not react to IPI\n"); in crash_smp_send_stop()
/linux-5.10/net/6lowpan/
Dndisc.c109 /* react on overrides only. TODO check if this is really right. */ in lowpan_ndisc_update()
/linux-5.10/tools/testing/selftests/net/forwarding/
Dmirror_gre_changes.sh7 # Test how mirrors to gretap and ip6gretap react to changes to relevant
/linux-5.10/arch/mips/pci/
Dops-rc32434.c111 * Certain devices react delayed at device scan time, this in read_config_dword()
/linux-5.10/Documentation/devicetree/bindings/leds/
Dcommon.yaml135 indicate its state. E.g. USB 2.0 LED may react to device(s) in a USB 2.0
/linux-5.10/Documentation/input/devices/
Dyealink.rst206 is not initialized and does not react to any actions.
/linux-5.10/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-5.10/include/media/
Dv4l2-mc.h169 * React to link management on powered pipelines by updating the use count of
/linux-5.10/net/iucv/
Daf_iucv.c1836 * afiucv_hs_callback_syn - react on received SYN
1901 * afiucv_hs_callback_synack() - react on received SYN-ACK
1922 * afiucv_hs_callback_synfin() - react on received SYN_FIN
1942 * afiucv_hs_callback_fin() - react on received FIN
1963 * afiucv_hs_callback_win() - react on received WIN
1981 * afiucv_hs_callback_rx() - react on received data
/linux-5.10/drivers/xen/
Dxen-balloon.c62 /* React to a change in the target key */
/linux-5.10/drivers/parisc/
Dpower.c56 /* how long does the power button needs to be down until we react ? */
/linux-5.10/drivers/cpufreq/
Dlongrun.c212 /* try decreasing in 10% steps, some processors react only in longrun_determine_freqs()
/linux-5.10/drivers/power/reset/
Dltc2952-poweroff.c14 * and react by properly shutting down the system.
/linux-5.10/drivers/media/usb/pvrusb2/
Dpvrusb2-context.c357 should not happen, but react if it does. */ in pvr2_channel_limit_inputs()

12345