| /kernel/linux/linux-5.10/drivers/crypto/cavium/cpt/ |
| 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()
|
| /kernel/linux/linux-4.19/drivers/crypto/cavium/cpt/ |
| D | cptvf_mbox.c | 116 dev_err(&pdev->dev, "PF didn't respond to READY msg\n"); in cptvf_check_pf_ready()
135 dev_err(&pdev->dev, "PF didn't respond to vq_size msg\n"); in cptvf_send_vq_size_msg()
154 dev_err(&pdev->dev, "PF didn't respond to vf_type msg\n"); in cptvf_send_vf_to_grp_msg()
173 dev_err(&pdev->dev, "PF didn't respond to vf_type msg\n"); in cptvf_send_vf_priority_msg()
189 dev_err(&pdev->dev, "PF didn't respond to UP msg\n"); in cptvf_send_vf_up()
206 dev_err(&pdev->dev, "PF didn't respond to DOWN msg\n"); in cptvf_send_vf_down()
|
| /kernel/linux/linux-4.19/drivers/misc/mic/scif/ |
| D | scif_epd.c | 115 * scif_cnctreq() - Respond to SCIF_CNCT_REQ interrupt message
166 * scif_cnctgnt() - Respond to SCIF_CNCT_GNT interrupt message
192 * scif_cnctgnt_ack() - Respond to SCIF_CNCT_GNTACK interrupt message
214 * scif_cnctgnt_nack() - Respond to SCIF_CNCT_GNTNACK interrupt message
232 * scif_cnctrej() - Respond to SCIF_CNCT_REJ interrupt message
251 * scif_discnct() - Respond to SCIF_DISCNCT interrupt message
312 * scif_discnct_ack() - Respond to SCIF_DISCNT_ACK interrupt message
328 * scif_clientsend() - Respond to SCIF_CLIENT_SEND interrupt message
344 * scif_clientrcvd() - Respond to SCIF_CLIENT_RCVD interrupt message
|
| /kernel/linux/linux-5.10/drivers/usb/misc/ |
| D | ftdi-elan.c | 152 struct u132_respond respond[RESPOND_SIZE]; member
331 struct u132_respond *respond = &ftdi->respond[RESPOND_MASK & in ftdi_elan_abandon_completions() local
333 *respond->result = -ESHUTDOWN; in ftdi_elan_abandon_completions()
334 *respond->value = 0; in ftdi_elan_abandon_completions()
335 complete(&respond->wait_completion); in ftdi_elan_abandon_completions()
502 dev_err(&ftdi->udev->dev, "respond error %d\n", retval); in ftdi_elan_respond_work()
1012 struct u132_respond *respond = &ftdi->respond[ in ftdi_elan_respond_engine() local
1021 *respond->value = data; in ftdi_elan_respond_engine()
1022 *respond->result = 0; in ftdi_elan_respond_engine()
1023 complete(&respond->wait_completion); in ftdi_elan_respond_engine()
[all …]
|
| /kernel/linux/linux-4.19/drivers/usb/misc/ |
| D | ftdi-elan.c | 152 struct u132_respond respond[RESPOND_SIZE]; member
331 struct u132_respond *respond = &ftdi->respond[RESPOND_MASK & in ftdi_elan_abandon_completions() local
333 *respond->result = -ESHUTDOWN; in ftdi_elan_abandon_completions()
334 *respond->value = 0; in ftdi_elan_abandon_completions()
335 complete(&respond->wait_completion); in ftdi_elan_abandon_completions()
501 dev_err(&ftdi->udev->dev, "respond error %d\n", retval); in ftdi_elan_respond_work()
1036 struct u132_respond *respond = &ftdi->respond[ in ftdi_elan_respond_engine() local
1045 *respond->value = data; in ftdi_elan_respond_engine()
1046 *respond->result = 0; in ftdi_elan_respond_engine()
1047 complete(&respond->wait_completion); in ftdi_elan_respond_engine()
[all …]
|
| /kernel/linux/linux-4.19/Documentation/misc-devices/ |
| D | eeprom | 59 The other devices will not be found on a DIMM because they respond to more
71 does not respond to byte reads. If this register is present, the lower 128
74 device will no longer respond at the 0x30-37 address. The eeprom driver
|
| /kernel/linux/linux-5.10/drivers/char/tpm/ |
| D | tpm_ibmvtpm.h | 52 #define INIT_CRQ_RES 0x01 /* Init respond */
53 #define INIT_CRQ_COMP_RES 0x02 /* Init complete respond */
|
| /kernel/linux/linux-4.19/drivers/char/tpm/ |
| D | tpm_ibmvtpm.h | 57 #define INIT_CRQ_RES 0x01 /* Init respond */
58 #define INIT_CRQ_COMP_RES 0x02 /* Init complete respond */
|
| /kernel/linux/linux-4.19/arch/sparc/kernel/ |
| 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 */
|
| /kernel/linux/linux-5.10/arch/sparc/kernel/ |
| 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 */
|
| /kernel/linux/linux-5.10/net/netlabel/ |
| 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.
|
| /kernel/linux/linux-5.10/Documentation/misc-devices/ |
| 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
|
| /kernel/linux/linux-4.19/net/netlabel/ |
| D | netlabel_mgmt.h | 78 * The kernel should respond with a series of the following messages.
155 * NLM_F_DUMP flag should be set. The kernel should respond with a series of
165 * kernel to respond to an VERSION request.
|
| /kernel/linux/linux-5.10/drivers/misc/ibmasm/ |
| D | heartbeat.c | 21 * to the driver. The driver must respond to the heartbeats or else the OS
24 * continues to respond to heartbeats, making the service processor believe
|
| /kernel/linux/linux-4.19/drivers/infiniband/hw/qib/ |
| 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()
|
| /kernel/linux/linux-5.10/drivers/infiniband/hw/qib/ |
| 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()
|
| /kernel/linux/linux-4.19/drivers/misc/ibmasm/ |
| D | heartbeat.c | 35 * to the driver. The driver must respond to the heartbeats or else the OS
38 * continues to respond to heartbeats, making the service processor believe
|
| /kernel/linux/linux-4.19/Documentation/process/ |
| D | 6.Followthrough.rst | 44 impulse to respond in kind. Code review is about the code, not about
59 that the reviewer is asking you to fix. And respond back to the reviewer:
177 respond to these reports is a matter of basic pride in your work. If that
209 really only one way to respond: be pleased that your problem got solved and
|
| /kernel/linux/linux-5.10/Documentation/process/ |
| D | 6.Followthrough.rst | 44 impulse to respond in kind. Code review is about the code, not about
59 that the reviewer is asking you to fix. And respond back to the reviewer:
177 respond to these reports is a matter of basic pride in your work. If that
209 really only one way to respond: be pleased that your problem got solved and
|
| /kernel/linux/linux-5.10/drivers/input/joystick/iforce/ |
| D | iforce-main.c | 278 dev_warn(&iforce->dev->dev, "Device does not respond to id packet M\n"); in iforce_init_device()
283 dev_warn(&iforce->dev->dev, "Device does not respond to id packet P\n"); in iforce_init_device()
288 dev_warn(&iforce->dev->dev, "Device does not respond to id packet B\n"); in iforce_init_device()
293 dev_warn(&iforce->dev->dev, "Device does not respond to id packet N\n"); in iforce_init_device()
|
| /kernel/linux/linux-5.10/drivers/scsi/bfa/ |
| D | bfa_hw_ct.c | 61 * Actions to respond RME Interrupt for Catapult ASIC:
79 * Actions to respond RME Interrupt for Catapult2 ASIC:
|
| /kernel/linux/linux-4.19/drivers/platform/chrome/ |
| D | cros_ec_spi.c | 32 * about 400-500us for the EC to respond there is not a lot of
33 * point in tuning this. If the EC could respond faster then
42 * Allow for a long time for the EC to respond. We support i2c
210 dev_warn(ec_dev->dev, "EC failed to respond in time\n"); in cros_ec_spi_receive_packet()
318 dev_warn(ec_dev->dev, "EC failed to respond in time\n"); in cros_ec_spi_receive_response()
426 * itself, it can't respond to any commands and instead in cros_ec_pkt_xfer_spi()
|
| /kernel/linux/linux-5.10/drivers/w1/slaves/ |
| 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()
|
| /kernel/linux/linux-4.19/drivers/scsi/bfa/ |
| D | bfa_hw_ct.c | 69 * Actions to respond RME Interrupt for Catapult ASIC:
88 * Actions to respond RME Interrupt for Catapult2 ASIC:
|
| /kernel/linux/linux-4.19/drivers/input/joystick/iforce/ |
| D | iforce-main.c | 322 dev_warn(&iforce->dev->dev, "Device does not respond to id packet M\n"); in iforce_init_device()
327 dev_warn(&iforce->dev->dev, "Device does not respond to id packet P\n"); in iforce_init_device()
332 dev_warn(&iforce->dev->dev, "Device does not respond to id packet B\n"); in iforce_init_device()
337 dev_warn(&iforce->dev->dev, "Device does not respond to id packet N\n"); in iforce_init_device()
|