Home
last modified time | relevance | path

Searched refs:responding (Results 1 – 22 of 22) sorted by relevance

/Linux-v5.10/drivers/usb/class/
Dcdc-wdm.c236 int responding; in wdm_int_callback() local
295 responding = test_and_set_bit(WDM_RESPONDING, &desc->flags); in wdm_int_callback()
296 if (!desc->resp_count++ && !responding in wdm_int_callback()
791 int responding; in wdm_rxwork() local
797 responding = test_and_set_bit(WDM_RESPONDING, &desc->flags); in wdm_rxwork()
799 if (!responding) in wdm_rxwork()
/Linux-v5.10/Documentation/admin-guide/nfs/
Dpnfs-block-server.rst23 If the nfsd server needs to fence a non-responding client it calls
/Linux-v5.10/drivers/scsi/mpt3sas/
Dmpt3sas_base.h554 u8 responding; member
614 u8 responding; member
703 u8 responding; member
789 u8 responding; member
Dmpt3sas_scsih.c8691 sas_device->responding = 1; in _scsih_mark_responding_sas_device()
8863 pcie_device->responding = 1; in _scsih_mark_responding_pcie_device()
8985 raid_device->responding = 1; in _scsih_mark_responding_raid_device()
9111 sas_expander->responding = 1; in _scsih_mark_responding_expander()
9203 if (!sas_device->responding) in _scsih_remove_unresponding_devices()
9206 sas_device->responding = 0; in _scsih_remove_unresponding_devices()
9224 if (!pcie_device->responding) in _scsih_remove_unresponding_devices()
9227 pcie_device->responding = 0; in _scsih_remove_unresponding_devices()
9242 if (!raid_device->responding) in _scsih_remove_unresponding_devices()
9246 raid_device->responding = 0; in _scsih_remove_unresponding_devices()
[all …]
/Linux-v5.10/Documentation/networking/device_drivers/atm/
Dcxacru.rst10 module loaded, the device will sometimes stop responding after unloading the
/Linux-v5.10/drivers/bus/
DKconfig49 not responding on timeout an IRQ is raised with an erroneous address
66 any bus protocol errors and device not responding situations by
/Linux-v5.10/Documentation/i2c/
Dfault-codes.rst91 an I2C device was temporarily not responding, usually it
/Linux-v5.10/Documentation/process/
D2.Process.rst433 - When responding to linux-kernel email (or that on other lists) preserve
436 sure that the person you are responding to is in the Cc: list. This
445 text you are responding to). It makes your response harder to read and
D5.Posting.rst289 - If you are responding to a bug report or a feature request, copy the
/Linux-v5.10/Documentation/watchdog/
Dwatchdog-api.rst48 still responding before doing the write call to ping the watchdog.
/Linux-v5.10/Documentation/admin-guide/
Dreporting-bugs.rst177 responding to these types of bugs in a timely manner (especially during a
/Linux-v5.10/Documentation/ide/
Dide.rst142 this means that the hardware is not responding to the driver's attempts
/Linux-v5.10/Documentation/filesystems/
Dconfigfs.rst322 responsible for responding to this. If the subsystem has references to
425 responsible for responding to the change.
Dfuse.rst178 not responding. Reasons for this may be:
/Linux-v5.10/Documentation/PCI/
Dpci.rst371 - Disable device from responding to MMIO/IO Port addresses
436 Disable Device from responding to MMIO/IO Port addresses
/Linux-v5.10/Documentation/hwmon/
Dabituguru-datasheet.rst12 the program inside the uC that is responding to calls.
/Linux-v5.10/Documentation/scsi/
Daic79xx.rst496 to stop responding.
/Linux-v5.10/Documentation/driver-api/media/drivers/
Dcx2341x-devel.rst971 Does nothing. Can be used to check if the firmware is responding.
2217 is responding.
/Linux-v5.10/Documentation/networking/
Dip-sysctl.rst434 tcp_keepalive_probes it is time to kill not responding connection,
2140 responding to a unicast neighbor solicitation.
2149 message. When responding to unicast solicitations, the option can be
Drxrpc.rst1054 the peer into responding, which would then cause the value returned by the
/Linux-v5.10/drivers/spi/
DKconfig1038 SPI slave handler responding with the time of reception of the last
/Linux-v5.10/Documentation/admin-guide/cifs/
Dusage.rst688 Retry file operations if server is not responding