| /Linux-v5.10/drivers/crypto/cavium/cpt/ |
| D | cptvf_main.c | 735 dev_err(dev, "PF not responding to READY msg"); in cptvf_probe()
749 dev_err(dev, "PF not responding to QLEN msg"); in cptvf_probe()
759 dev_err(dev, "PF not responding to VF_GRP msg"); in cptvf_probe()
766 dev_err(dev, "PF not responding to VF_PRIO msg"); in cptvf_probe()
787 dev_err(dev, "PF not responding to UP msg"); in cptvf_probe()
824 dev_err(&pdev->dev, "PF not responding to DOWN msg"); in cptvf_remove()
|
| /Linux-v5.10/drivers/net/ethernet/sfc/falcon/ |
| D | mdio_10g.c | 56 /* Read MMD STATUS2 to check it is responding. */ in ef4_mdio_check_mmd()
60 "PHY MMD %d not responding.\n", mmd); in ef4_mdio_check_mmd()
141 /* Check all required MMDs are responding and happy. */ in ef4_mdio_check_mmds()
|
| /Linux-v5.10/drivers/bus/ |
| 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-v5.10/drivers/usb/class/ |
| D | cdc-wdm.c | 236 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/devicetree/bindings/bus/ |
| D | baikal,bt1-apb.yaml | 18 device not responding on timeout an IRQ is raised with an erroneous address
|
| D | baikal,bt1-axi.yaml | 20 some peripherals). In case of any protocol error, device not responding
|
| /Linux-v5.10/Documentation/admin-guide/nfs/ |
| D | pnfs-block-server.rst | 23 If the nfsd server needs to fence a non-responding client it calls
|
| /Linux-v5.10/drivers/scsi/mpt3sas/ |
| D | mpt3sas_base.h | 530 * @responding: used in _scsih_sas_device_mark_responding
554 u8 responding; member
591 * @responding: used in _scsih_pcie_device_mark_responding
614 u8 responding; member
681 * @responding: used in _scsih_raid_device_mark_responding
703 u8 responding; member
776 * @responding: used in _scsih_expander_device_mark_responding
789 u8 responding; member
|
| D | mpt3sas_scsih.c | 3457 * _scsih_error_recovery_delete_devices - remove devices not responding
6526 status_str = "responding"; in _scsih_sas_topology_change_event_debug()
6562 status_str = "target responding"; in _scsih_sas_topology_change_event_debug()
7269 status_str = "responding"; in _scsih_pcie_topology_change_event_debug()
7305 status_str = "target responding"; in _scsih_pcie_topology_change_event_debug()
8661 * _scsih_mark_responding_sas_device - mark a sas_devices as responding
8665 * After host reset, find out whether devices are still responding.
8691 sas_device->responding = 1; in _scsih_mark_responding_sas_device()
8803 * After host reset, find out whether devices are still responding.
8840 * _scsih_mark_responding_pcie_device - mark a pcie_device as responding
[all …]
|
| /Linux-v5.10/drivers/misc/ibmasm/ |
| D | heartbeat.c | 27 * Before responding to a heartbeat the driver checks if a panic has happened,
|
| /Linux-v5.10/drivers/gpu/drm/radeon/ |
| D | vce_v1_0.c | 337 DRM_ERROR("VCE not responding, trying to reset the ECPU!!!\n"); in vce_v1_0_start()
349 DRM_ERROR("VCE not responding, giving up!!!\n"); in vce_v1_0_start()
|
| D | uvd_v1_0.c | 341 DRM_ERROR("UVD not responding, trying to reset the VCPU!!!\n"); in uvd_v1_0_start()
350 DRM_ERROR("UVD not responding, giving up!!!\n"); in uvd_v1_0_start()
|
| /Linux-v5.10/Documentation/networking/device_drivers/atm/ |
| D | cxacru.rst | 10 module loaded, the device will sometimes stop responding after unloading the
|
| /Linux-v5.10/arch/x86/boot/ |
| D | pm.c | 109 puts("A20 gate not responding, unable to boot...\n"); in go_to_protected_mode()
|
| /Linux-v5.10/include/net/netns/ |
| D | sctp.h | 19 /* This is the global socket data structure used for responding to
|
| /Linux-v5.10/drivers/thunderbolt/ |
| D | ctl.h | 39 * this is the the upstream port of the responding
|
| /Linux-v5.10/drivers/greybus/ |
| D | svc_watchdog.c | 87 panic("SVC is not responding\n"); in do_work()
|
| /Linux-v5.10/Documentation/i2c/ |
| D | fault-codes.rst | 91 an I2C device was temporarily not responding, usually it
|
| /Linux-v5.10/Documentation/process/ |
| D | 2.Process.rst | 433 - 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
|
| /Linux-v5.10/drivers/pcmcia/ |
| D | soc_common.h | 32 * use when responding to a Card Services query of some kind.
|
| /Linux-v5.10/drivers/net/wireless/ath/carl9170/ |
| D | fwdesc.h | 48 /* The firmware is capable of responding to incoming BAR frames */
|
| /Linux-v5.10/drivers/gpu/drm/amd/amdgpu/ |
| D | vce_v2_0.c | 129 DRM_ERROR("VCE not responding, trying to reset the ECPU!!!\n"); in vce_v2_0_firmware_loaded()
268 DRM_ERROR("VCE not responding, giving up!!!\n"); in vce_v2_0_start()
|
| /Linux-v5.10/drivers/scsi/megaraid/ |
| D | megaraid_mbox.h | 165 * @hw_error : set if FW not responding
|
| /Linux-v5.10/fs/ocfs2/dlm/ |
| D | dlmast.c | 347 mlog(0, "Responding with DLM_RECOVERING!\n"); in dlm_proxy_ast_handler()
352 mlog(0, "Responding with DLM_MIGRATING!\n"); in dlm_proxy_ast_handler()
|
| /Linux-v5.10/drivers/media/i2c/smiapp/ |
| D | smiapp-regs.c | 223 * Due to unknown reason sensor stops responding. This in smiapp_write_no_quirk()
|
