| /linux-6.3-rc2/drivers/usb/class/ |
| A D | cdc-wdm.c | 250 int responding; in wdm_int_callback() local
309 responding = test_and_set_bit(WDM_RESPONDING, &desc->flags); in wdm_int_callback()
310 if (!desc->resp_count++ && !responding in wdm_int_callback()
979 int responding; in wdm_rxwork() local
985 responding = test_and_set_bit(WDM_RESPONDING, &desc->flags); in wdm_rxwork()
987 if (!responding) in wdm_rxwork()
|
| /linux-6.3-rc2/Documentation/devicetree/bindings/bus/ |
| A D | baikal,bt1-apb.yaml | 18 device not responding on timeout an IRQ is raised with an erroneous address
|
| A D | baikal,bt1-axi.yaml | 20 some peripherals). In case of any protocol error, device not responding
|
| /linux-6.3-rc2/Documentation/admin-guide/nfs/ |
| A D | pnfs-block-server.rst | 23 If the nfsd server needs to fence a non-responding client it calls
|
| /linux-6.3-rc2/Documentation/networking/device_drivers/atm/ |
| A D | cxacru.rst | 10 module loaded, the device will sometimes stop responding after unloading the
|
| /linux-6.3-rc2/drivers/scsi/mpt3sas/ |
| A D | mpt3sas_base.h | 572 u8 responding; member
635 u8 responding; member
724 u8 responding; member
818 u8 responding; member
|
| A D | mpt3sas_scsih.c | 9738 sas_device->responding = 1; in _scsih_mark_responding_sas_device()
9908 pcie_device->responding = 1; in _scsih_mark_responding_pcie_device()
10030 raid_device->responding = 1; in _scsih_mark_responding_raid_device()
10160 sas_expander->responding = 1; in _scsih_mark_responding_expander()
10267 if (!sas_device->responding) in _scsih_remove_unresponding_devices()
10270 sas_device->responding = 0; in _scsih_remove_unresponding_devices()
10298 if (!pcie_device->responding) in _scsih_remove_unresponding_devices()
10301 pcie_device->responding = 0; in _scsih_remove_unresponding_devices()
10316 if (!raid_device->responding) in _scsih_remove_unresponding_devices()
10320 raid_device->responding = 0; in _scsih_remove_unresponding_devices()
[all …]
|
| /linux-6.3-rc2/drivers/bus/ |
| A D | Kconfig | 49 not responding on timeout an IRQ is raised with an erroneous address
66 any bus protocol errors and device not responding situations by
|
| /linux-6.3-rc2/Documentation/i2c/ |
| A D | fault-codes.rst | 91 an I2C device was temporarily not responding, usually it
|
| /linux-6.3-rc2/Documentation/process/ |
| A D | 2.Process.rst | 426 - When responding to linux-kernel email (or that on other lists) preserve
429 sure that the person you are responding to is in the Cc: list. This
438 text you are responding to). It makes your response harder to read and
|
| A D | 5.Posting.rst | 306 - If you are responding to a bug report or a feature request, copy the
|
| /linux-6.3-rc2/Documentation/watchdog/ |
| A D | watchdog-api.rst | 48 still responding before doing the write call to ping the watchdog.
|
| /linux-6.3-rc2/Documentation/filesystems/ |
| A D | configfs.rst | 321 responsible for responding to this. If the subsystem has references to
424 responsible for responding to the change.
|
| A D | fuse.rst | 178 not responding. Reasons for this may be:
|
| /linux-6.3-rc2/Documentation/PCI/ |
| A D | pci.rst | 372 - Disable device from responding to MMIO/IO Port addresses
437 Disable Device from responding to MMIO/IO Port addresses
|
| /linux-6.3-rc2/Documentation/driver-api/surface_aggregator/ |
| A D | ssh.rst | 144 the frame by responding with a message containing an |ACK|-type frame with
|
| /linux-6.3-rc2/Documentation/hwmon/ |
| A D | abituguru-datasheet.rst | 12 the program inside the uC that is responding to calls.
|
| /linux-6.3-rc2/Documentation/scsi/ |
| A D | aic79xx.rst | 496 to stop responding.
|
| /linux-6.3-rc2/tools/memory-model/Documentation/ |
| A D | access-marking.txt | 49 when responding to KCSAN complaints. Churning the code base with
|
| /linux-6.3-rc2/Documentation/driver-api/media/drivers/ |
| A D | cx2341x-devel.rst | 971 Does nothing. Can be used to check if the firmware is responding.
2217 is responding.
|
| /linux-6.3-rc2/Documentation/networking/ |
| A D | ip-sysctl.rst | 502 tcp_keepalive_probes it is time to kill not responding connection,
2509 responding to a unicast neighbor solicitation.
2518 message. When responding to unicast solicitations, the option can be
|
| A D | rxrpc.rst | 1054 the peer into responding, which would then cause the value returned by the
|
| /linux-6.3-rc2/drivers/spi/ |
| A D | Kconfig | 1193 SPI slave handler responding with the time of reception of the last
|
| /linux-6.3-rc2/Documentation/admin-guide/cifs/ |
| A D | usage.rst | 688 Retry file operations if server is not responding
|
| /linux-6.3-rc2/Documentation/admin-guide/ |
| A D | reporting-issues.rst | 1347 Sometimes the maintainer might not be responding in a timely manner; other
|