Searched refs:responding (Results 1 – 14 of 14) sorted by relevance
255 int responding; in wdm_int_callback() local314 responding = test_and_set_bit(WDM_RESPONDING, &desc->flags); in wdm_int_callback()315 if (!desc->resp_count++ && !responding in wdm_int_callback()988 int responding; in wdm_rxwork() local994 responding = test_and_set_bit(WDM_RESPONDING, &desc->flags); in wdm_rxwork()996 if (!responding) in wdm_rxwork()
10 module loaded, the device will sometimes stop responding after unloading the
41 documented, especially when you are responding to complaints
55 when responding to KCSAN complaints. Churning the code base with
95 an I2C device was temporarily not responding, usually it
48 still responding before doing the write call to ping the watchdog.
321 responsible for responding to this. If the subsystem has references to424 responsible for responding to the change.
372 - Disable device from responding to MMIO/IO Port addresses437 Disable Device from responding to MMIO/IO Port addresses
144 the frame by responding with a message containing an |ACK|-type frame with
192 not responding. Reasons for this may be:
496 to stop responding.
971 Does nothing. Can be used to check if the firmware is responding.2217 is responding.
690 Retry file operations if server is not responding
5666 event channel delivery, so responding within the kernel without