| /Linux-v6.6/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()
|
| /Linux-v6.6/include/linux/ |
| 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
|
| /Linux-v6.6/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 */
|
| /Linux-v6.6/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 */
|
| /Linux-v6.6/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
|
| /Linux-v6.6/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.
|
| /Linux-v6.6/drivers/misc/ibmasm/ |
| 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
|
| /Linux-v6.6/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()
|
| /Linux-v6.6/Documentation/process/ |
| 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
|
| /Linux-v6.6/drivers/input/joystick/iforce/ |
| 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()
|
| /Linux-v6.6/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:
|
| /Linux-v6.6/drivers/usb/gadget/function/ |
| D | f_hid.c | 668 goto respond; in hidg_setup()
676 goto respond; in hidg_setup()
684 goto respond; in hidg_setup()
694 goto respond; in hidg_setup()
709 goto respond; in hidg_setup()
719 goto respond; in hidg_setup()
737 goto respond; in hidg_setup()
745 goto respond; in hidg_setup()
766 respond: in hidg_setup()
|
| /Linux-v6.6/drivers/net/wwan/iosm/ |
| 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);
|
| /Linux-v6.6/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()
|
| /Linux-v6.6/drivers/platform/chrome/ |
| 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()
|
| /Linux-v6.6/Documentation/ABI/testing/ |
| D | sysfs-bus-fsi-devices-sbefifo | 6 timeout; i.e. the SBE did not respond within the time allotted
|
| /Linux-v6.6/drivers/media/rc/ |
| D | gpio-ir-recv.c | 37 * Respond to interrupt taking more latency when cpu in idle. in gpio_ir_recv_irq()
43 * respond to interrupt, another is delay introduced by async api. in gpio_ir_recv_irq()
|
| /Linux-v6.6/Documentation/devicetree/bindings/rtc/ |
| D | isil,isl12026.txt | 4 registers respond at bus address 0x6f, and the EEPROM array responds
|
| /Linux-v6.6/net/dccp/ |
| D | input.c | 52 * - RESPOND (already handled by dccp_check_req) in dccp_rcv_close()
327 * or (S.state == RESPOND and P.type == Data), in __dccp_rcv_established()
592 * S.state = RESPOND in dccp_rcv_state_process()
596 * Cookies Continue with S.state == RESPOND in dccp_rcv_state_process()
636 * or (S.state == RESPOND and P.type == Data), in dccp_rcv_state_process()
|
| /Linux-v6.6/Documentation/maintainer/ |
| D | feature-and-driver-maintainers.rst | 34 reviewers should try to respond quicker than what is the usual patch
81 Maintainers furthermore should respond to reports about other kinds of
|
| /Linux-v6.6/drivers/platform/chrome/wilco_ec/ |
| D | mailbox.c | 131 /* For some commands (eg shutdown) the EC will not respond, that's OK */ in wilco_ec_transfer()
133 dev_dbg(ec->dev, "EC does not respond to this command\n"); in wilco_ec_transfer()
|
| /Linux-v6.6/Documentation/scsi/ |
| D | BusLogic.rst | 306 respond to synchronous transfer negotiation for UltraSCSI speed. AutoSCSI
324 The BT-948/958/958D will not respond to any of the ISA compatible I/O ports
325 that previous BusLogic SCSI Host Adapters respond to. This driver supports
375 UltraSCSI operation, or where existing SCSI devices do not properly respond
500 respond correctly when Logical Units above 0 are addressed.
|
| /Linux-v6.6/Documentation/devicetree/bindings/i2c/ |
| D | hpe,gxp-i2c.yaml | 34 arm and respond to interrupts from its engine. Each bit in the
|
| /Linux-v6.6/net/tipc/ |
| D | discover.c | 210 bool respond = false; in tipc_disc_rcv() local
251 &maddr, &respond, &dupl_addr); in tipc_disc_rcv()
254 if (!respond) in tipc_disc_rcv()
|
| /Linux-v6.6/Documentation/devicetree/bindings/media/i2c/ |
| D | chrontel,ch7322.yaml | 42 the device will respond to power status requests with "standby"
|
