| /openbmc/linux/drivers/crypto/cavium/cpt/ |
| H A D | cptvf_mbox.c | 96 dev_err(&pdev->dev, "PF didn't respond to READY msg\n"); in cptvf_check_pf_ready()
115 dev_err(&pdev->dev, "PF didn't respond to vq_size msg\n"); in cptvf_send_vq_size_msg()
134 dev_err(&pdev->dev, "PF didn't respond to vf_type msg\n"); in cptvf_send_vf_to_grp_msg()
153 dev_err(&pdev->dev, "PF didn't respond to vf_type msg\n"); in cptvf_send_vf_priority_msg()
169 dev_err(&pdev->dev, "PF didn't respond to UP msg\n"); in cptvf_send_vf_up()
186 dev_err(&pdev->dev, "PF didn't respond to DOWN msg\n"); in cptvf_send_vf_down()
|
| /openbmc/linux/include/linux/ |
| H A D | pmbus.h | 21 * Some PMBus chips respond with valid data when trying to read an unsupported
40 * Some PMBus chips don't respond with valid data when reading the CAPABILITY
62 * Some PMBus chips respond with invalid data when reading the WRITE_PROTECT
|
| /openbmc/openbmc/meta-openembedded/meta-oe/recipes-extended/rarpd/rarpd/ |
| H A D | 0001-rarpd.8-add-man-file.patch | 42 +) before it decides to respond to the RARP request.
49 +Respond to ARP as well as RARP requests.
62 +will not respond to the request.
|
| /openbmc/phosphor-host-ipmid/xyz/openbmc_project/Ipmi/Internal/ |
| H A D | SoftPowerOff.interface.yaml | 3 Host will respond with a GetMessageFlags command and the BMC will respond
|
| /openbmc/openbmc/meta-arm/meta-arm-systemready/lib/oeqa/runtime/cases/ |
| H A D | arm_systemready_fedora_unattended.py | 31 # Waiting to respond to the boot loader prompt error message.
33 'Please respond \'yes\' or \'no\': ',
|
| /openbmc/linux/drivers/char/tpm/ |
| H A D | tpm_ibmvtpm.h | 52 #define INIT_CRQ_RES 0x01 /* Init respond */
53 #define INIT_CRQ_COMP_RES 0x02 /* Init complete respond */
|
| /openbmc/linux/arch/sparc/kernel/ |
| H A D | pci_sabre.c | 137 #define SABRE_PCITASR_EF 0x0000000000000080UL /* Respond to 0xe0000000-0xffffffff */
138 #define SABRE_PCITASR_CD 0x0000000000000040UL /* Respond to 0xc0000000-0xdfffffff */
139 #define SABRE_PCITASR_AB 0x0000000000000020UL /* Respond to 0xa0000000-0xbfffffff */
140 #define SABRE_PCITASR_89 0x0000000000000010UL /* Respond to 0x80000000-0x9fffffff */
141 #define SABRE_PCITASR_67 0x0000000000000008UL /* Respond to 0x60000000-0x7fffffff */
142 #define SABRE_PCITASR_45 0x0000000000000004UL /* Respond to 0x40000000-0x5fffffff */
143 #define SABRE_PCITASR_23 0x0000000000000002UL /* Respond to 0x20000000-0x3fffffff */
144 #define SABRE_PCITASR_01 0x0000000000000001UL /* Respond to 0x00000000-0x1fffffff */
|
| /openbmc/u-boot/cmd/aspeed/nettest/ |
| H A D | ncsi.c | 63 // PRINTF( FP_LOG, "[NCSI-Respond] DA : %02x %02x %02x %02x %02x %02x\n", in->DA[ 5 ], … in ncsi_respdump()
64 // PRINTF( FP_LOG, "[NCSI-Respond] SA : %02x %02x %02x %02x %02x %02x\n", in->SA[ 5 ], … in ncsi_respdump()
65 …PRINTF( FP_LOG, "[NCSI-Respond] DA : %02x %02x %02x %02x %02x %02x\n", in->DA[ 0 ], in… in ncsi_respdump()
66 …PRINTF( FP_LOG, "[NCSI-Respond] SA : %02x %02x %02x %02x %02x %02x\n", in->SA[ 0 ], in… in ncsi_respdump()
67 …PRINTF( FP_LOG, "[NCSI-Respond] EtherType : %04x\n", SWAP_2B_BEDN( in->EtherType ) … in ncsi_respdump()
68 …PRINTF( FP_LOG, "[NCSI-Respond] MC_ID : %02x\n", in->MC_ID … in ncsi_respdump()
69 …PRINTF( FP_LOG, "[NCSI-Respond] Header_Revision: %02x\n", in->Header_Revision … in ncsi_respdump()
70 // PRINTF( FP_LOG, "[NCSI-Respond] Reserved_1 : %02x\n", in->Reserved_1 … in ncsi_respdump()
71 …PRINTF( FP_LOG, "[NCSI-Respond] IID : %02x\n", in->IID … in ncsi_respdump()
72 …PRINTF( FP_LOG, "[NCSI-Respond] Command : %02x\n", in->Command … in ncsi_respdump()
[all …]
|
| /openbmc/linux/net/netlabel/ |
| H A D | netlabel_mgmt.h | 64 * The kernel should respond with a series of the following messages.
141 * NLM_F_DUMP flag should be set. The kernel should respond with a series of
151 * kernel to respond to an VERSION request.
|
| /openbmc/linux/Documentation/misc-devices/ |
| H A D | eeprom.rst | 68 The other devices will not be found on a DIMM because they respond to more
80 does not respond to byte reads. If this register is present, the lower 128
83 device will no longer respond at the 0x30-37 address. The eeprom driver
|
| /openbmc/docs/designs/ |
| H A D | bmc-reset-with-host-up.md | 69 - Both IPMI and PLDM stacks will give the host a set amount of time to respond.
122 ### Automated Recovery when host does not respond
126 host has failed to respond to any of the different mechanisms to communicate
187 on the host so it does not respond to the BMC when it comes back from its
|
| /openbmc/u-boot/include/ |
| H A D | hda_codec.h | 30 * @return 0 if OK -ETIMEDOUT if codec did not respond in time
38 * @return 0 if OK -ETIMEDOUT if codec did not respond in time
|
| /openbmc/linux/drivers/misc/ibmasm/ |
| H A D | heartbeat.c | 22 * to the driver. The driver must respond to the heartbeats or else the OS
25 * continues to respond to heartbeats, making the service processor believe
|
| /openbmc/linux/drivers/infiniband/hw/qib/ |
| H A D | qib_qsfp.c | 81 * Module could take up to 2 Msec to respond to MOD_SEL, and there in qsfp_read()
123 * ready to respond to MOD_SEL negation, and there is no way in qsfp_read()
131 * Module could take up to 2 Msec to respond to MOD_SEL in qsfp_read()
190 * Module could take up to 2 Msec to respond to MOD_SEL, in qib_qsfp_write()
228 * ready to respond to MOD_SEL negation, and there is no way in qib_qsfp_write()
235 * Module could take up to 2 Msec to respond to MOD_SEL in qib_qsfp_write()
|
| /openbmc/linux/Documentation/process/ |
| H A D | 6.Followthrough.rst | 44 impulse to respond in kind. Code review is about the code, not about
66 that the reviewer is asking you to fix. And respond back to the reviewer:
184 respond to these reports is a matter of basic pride in your work. If that
216 really only one way to respond: be pleased that your problem got solved and
|
| /openbmc/openbmc/meta-openembedded/meta-networking/recipes-connectivity/tayga/files/ |
| H A D | tayga.conf | 22 # needs to be able to send ICMP messages. TAYGA will also respond to ICMP
34 # needs to be able to send ICMP messages. TAYGA will also respond to ICMP
|
| /openbmc/linux/drivers/input/joystick/iforce/ |
| H A D | iforce-main.c | 279 dev_warn(&iforce->dev->dev, "Device does not respond to id packet M\n"); in iforce_init_device()
284 dev_warn(&iforce->dev->dev, "Device does not respond to id packet P\n"); in iforce_init_device()
289 dev_warn(&iforce->dev->dev, "Device does not respond to id packet B\n"); in iforce_init_device()
294 dev_warn(&iforce->dev->dev, "Device does not respond to id packet N\n"); in iforce_init_device()
|
| /openbmc/linux/drivers/scsi/bfa/ |
| H A D | bfa_hw_ct.c | 61 * Actions to respond RME Interrupt for Catapult ASIC:
79 * Actions to respond RME Interrupt for Catapult2 ASIC:
|
| /openbmc/linux/drivers/w1/slaves/ |
| H A D | w1_ds2413.c | 62 /* slave didn't respond, try to select it again */ in state_read()
63 dev_warn(&sl->dev, "slave device did not respond to PIO_ACCESS_READ, " \ in state_read()
|
| /openbmc/openbmc/poky/documentation/test-manual/ |
| H A D | test-process.rst | 30 branch. If not successful, someone would respond to the changes on the
77 - QA teams respond to the email saying which tests they plan to run and
|
| /openbmc/phosphor-mboxd/Documentation/ |
| H A D | mbox_protocol.md | 153 write to in order to communicate to the other which will respond in some way.
228 supported version of the protocol. The BMC must respond with a protocol version
241 or otherwise set this argument to zero. The BMC must respond with the LPC bus
371 invalid sequence number. For all other cases, the BMC must respond with
744 that any commands which didn't respond as such succeeded.
749 host must not assume that any commands which didn't respond as such
778 will respond as it or the BMC may have crashed without clearing
|
| /openbmc/linux/drivers/net/wwan/iosm/ |
| H A D | iosm_ipc_mux_codec.h | 266 * ipc_mux_dl_acb_send_cmds - Respond to the Command blocks.
274 * @respond: If true return transaction ID
280 size_t res_size, bool blocking, bool respond);
|
| /openbmc/linux/drivers/usb/gadget/function/ |
| H A D | f_hid.c | 669 goto respond; in hidg_setup()
677 goto respond; in hidg_setup()
685 goto respond; in hidg_setup()
695 goto respond; in hidg_setup()
710 goto respond; in hidg_setup()
720 goto respond; in hidg_setup()
738 goto respond; in hidg_setup()
746 goto respond; in hidg_setup()
767 respond: in hidg_setup()
|
| /openbmc/linux/Documentation/ABI/testing/ |
| H A D | sysfs-bus-fsi-devices-sbefifo | 6 timeout; i.e. the SBE did not respond within the time allotted
|
| /openbmc/linux/drivers/platform/chrome/ |
| H A D | cros_ec_spi.c | 24 * about 400-500us for the EC to respond there is not a lot of
25 * point in tuning this. If the EC could respond faster then
34 * Allow for a long time for the EC to respond. We support i2c
226 dev_warn(ec_dev->dev, "EC failed to respond in time\n"); in cros_ec_spi_receive_packet()
334 dev_warn(ec_dev->dev, "EC failed to respond in time\n"); in cros_ec_spi_receive_response()
444 * itself, it can't respond to any commands and instead in do_cros_ec_pkt_xfer_spi()
|