Home
last modified time | relevance | path

Searched full:responding (Results 1 – 25 of 200) sorted by relevance

12345678

/linux/drivers/gpu/drm/amd/amdgpu/
H A Dta_secureDisplay_if.h34 /* Query whether TA is responding used only for validation purpose */
72 * This value is used to validate whether TA is responding successfully
115 * Output buffer format for query TA whether TA is responding used only for validation purpose
H A Damdgpu_securedisplay.c39 * 1:Query whether TA is responding used only for validation pupose
/linux/drivers/crypto/cavium/cpt/
H A Dcptvf_main.c726 dev_err(dev, "PF not responding to READY msg"); in cptvf_probe()
740 dev_err(dev, "PF not responding to QLEN msg"); in cptvf_probe()
750 dev_err(dev, "PF not responding to VF_GRP msg"); in cptvf_probe()
757 dev_err(dev, "PF not responding to VF_PRIO msg"); in cptvf_probe()
778 dev_err(dev, "PF not responding to UP msg"); in cptvf_probe()
815 dev_err(&pdev->dev, "PF not responding to DOWN msg"); in cptvf_remove()
/linux/drivers/net/ethernet/sfc/falcon/
H A Dmdio_10g.c56 /* 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/drivers/bus/
H A 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/Documentation/admin-guide/nfs/
H A Dpnfs-block-server.rst23 If the nfsd server needs to fence a non-responding client it calls
/linux/Documentation/devicetree/bindings/bus/
H A Dbaikal,bt1-apb.yaml18 device not responding on timeout an IRQ is raised with an erroneous address
H A Dbaikal,bt1-axi.yaml20 some peripherals). In case of any protocol error, device not responding
/linux/drivers/scsi/mpt3sas/
H A Dmpt3sas_base.h545 * @responding: used in _scsih_sas_device_mark_responding
572 u8 responding; member
612 * @responding: used in _scsih_pcie_device_mark_responding
635 u8 responding; member
702 * @responding: used in _scsih_raid_device_mark_responding
724 u8 responding; member
802 * @responding: used in _scsih_expander_device_mark_responding
818 u8 responding; member
/linux/drivers/usb/class/
H A Dcdc-wdm.c250 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()
980 int responding; in wdm_rxwork() local
986 responding = test_and_set_bit(WDM_RESPONDING, &desc->flags); in wdm_rxwork()
988 if (!responding) in wdm_rxwork()
/linux/drivers/gpu/drm/radeon/
H A Dvce_v1_0.c337 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()
H A Duvd_v1_0.c341 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/include/pcmcia/
H A Dsoc_common.h24 * use when responding to a Card Services query of some kind.
/linux/drivers/misc/ibmasm/
H A Dheartbeat.c28 * Before responding to a heartbeat the driver checks if a panic has happened,
/linux/Documentation/networking/device_drivers/atm/
H A Dcxacru.rst10 module loaded, the device will sometimes stop responding after unloading the
/linux/tools/memory-model/Documentation/
H A DREADME38 documented, especially when you are responding to complaints
/linux/Documentation/process/
H A D2.Process.rst426 - 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
439 the quoted text you are responding to.) For more details, see
/linux/arch/x86/boot/
H A Dpm.c110 puts("A20 gate not responding, unable to boot...\n"); in go_to_protected_mode()
/linux/include/net/netns/
H A Dsctp.h22 /* This is the global socket data structure used for responding to
/linux/drivers/thunderbolt/
H A Dctl.h38 * this is the upstream port of the responding
/linux/drivers/greybus/
H A Dsvc_watchdog.c87 panic("SVC is not responding\n"); in do_work()
/linux/drivers/gpu/drm/amd/pm/swsmu/inc/pmfw_if/
H A Dsmu_v13_0_1_ppsmc.h45 #define PPSMC_MSG_TestMessage 0x01 ///< To check if PMFW is alive and responding.…
/linux/Documentation/i2c/
H A Dfault-codes.rst95 an I2C device was temporarily not responding, usually it
/linux/drivers/net/wireless/ath/carl9170/
H A Dfwdesc.h48 /* The firmware is capable of responding to incoming BAR frames */
/linux/drivers/bluetooth/
H A Dbtqcomsmd.c133 /* The firmware stops responding for a while after setting the bdaddr, in btqcomsmd_set_bdaddr()

12345678