| /Linux-v6.1/drivers/usb/misc/ |
| D | ftdi-elan.c | 152 struct u132_respond respond[RESPOND_SIZE]; member
332 struct u132_respond *respond = &ftdi->respond[RESPOND_MASK & in ftdi_elan_abandon_completions() local
334 *respond->result = -ESHUTDOWN; in ftdi_elan_abandon_completions()
335 *respond->value = 0; in ftdi_elan_abandon_completions()
336 complete(&respond->wait_completion); in ftdi_elan_abandon_completions()
1013 struct u132_respond *respond = &ftdi->respond[ in ftdi_elan_respond_engine() local
1022 *respond->value = data; in ftdi_elan_respond_engine()
1023 *respond->result = 0; in ftdi_elan_respond_engine()
1024 complete(&respond->wait_completion); in ftdi_elan_respond_engine()
1302 struct u132_respond *respond = &ftdi->respond[ in ftdi_elan_read_reg() local
[all …]
|
| /Linux-v6.1/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.1/drivers/usb/gadget/function/ |
| D | f_hid.c | 656 goto respond; in hidg_setup()
664 goto respond; in hidg_setup()
672 goto respond; in hidg_setup()
682 goto respond; in hidg_setup()
697 goto respond; in hidg_setup()
707 goto respond; in hidg_setup()
725 goto respond; in hidg_setup()
733 goto respond; in hidg_setup()
754 respond: in hidg_setup()
|
| /Linux-v6.1/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()
|
| D | node.h | 96 bool *respond, bool *dupl_addr);
|
| D | node.c | 1174 bool *respond, bool *dupl_addr) in tipc_node_check_dest() argument
1189 *respond = false; in tipc_node_check_dest()
1216 *respond = true; in tipc_node_check_dest()
1234 *respond = true; in tipc_node_check_dest()
1253 *respond = true; in tipc_node_check_dest()
1265 *respond = true; in tipc_node_check_dest()
1286 *respond = false; in tipc_node_check_dest()
|
| /Linux-v6.1/Documentation/ABI/testing/ |
| D | sysfs-bus-fsi-devices-sbefifo | 6 timeout; i.e. the SBE did not respond within the time allotted
|
| D | sysfs-class-power-ltc4162l | 73 remain in this mode (and no longer respond to I2C commands)
|
| /Linux-v6.1/Documentation/devicetree/bindings/rtc/ |
| D | isil,isl12026.txt | 4 registers respond at bus address 0x6f, and the EEPROM array responds
|
| /Linux-v6.1/Documentation/block/ |
| D | null_blk.rst | 76 Whether or not to use a memory buffer to respond to IO requests
80 1 Use a memory buffer to respond to IO requests
|
| /Linux-v6.1/drivers/net/wwan/iosm/ |
| D | iosm_ipc_mux_codec.h | 280 size_t res_size, bool blocking, bool respond);
|
| /Linux-v6.1/Documentation/driver-api/xilinx/ |
| D | eemi.rst | 17 device to issue or respond to power management requests.
|
| /Linux-v6.1/Documentation/i2c/ |
| D | ten-bit-addresses.rst | 8 address 0x10 (though a single device could respond to both of them).
|
| D | i2c-stub.rst | 16 quick commands to the specified addresses; it will respond to the other
|
| /Linux-v6.1/drivers/media/usb/dvb-usb-v2/ |
| D | dvbsky.c | 350 u8 command[4], respond[2], command_size, respond_size; in dvbsky_ci_ctrl() local
365 respond, respond_size); in dvbsky_ci_ctrl()
369 *mem = respond[1]; in dvbsky_ci_ctrl()
|
| /Linux-v6.1/Documentation/w1/masters/ |
| D | omap-hdq.rst | 29 does not respond with a presence pulse as it does in the 1-Wire protocol.
|
| /Linux-v6.1/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
|
| /Linux-v6.1/Documentation/driver-api/pldmfw/ |
| D | index.rst | 66 the device. For each component, the firmware may respond with an
|
| /Linux-v6.1/Documentation/driver-api/thermal/ |
| D | intel_dptf.rst | 71 User space daemon write 1 to respond to firmware event
74 firmware calls for user space to respond with imok ACPI
|
| /Linux-v6.1/Documentation/scsi/ |
| D | megaraid.rst | 10 Different classes of controllers from LSI Logic accept and respond to the
|
| 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.1/Documentation/usb/ |
| D | raw-gadget.rst | 25 descriptors. Note that the UDC driver might respond to some requests on
|
| /Linux-v6.1/Documentation/filesystems/ |
| D | befs.rst | 34 respond to the address given above...
|
| /Linux-v6.1/Documentation/input/devices/ |
| D | alps.rst | 31 All ALPS touchpads should respond to the "E6 report" command sequence:
32 E8-E6-E6-E6-E9. An ALPS touchpad should respond with either 00-00-0A or
53 EC-EC-EC-E9 places the device in command mode, and the device will respond
|
| /Linux-v6.1/arch/arm64/boot/dts/xilinx/ |
| D | zynqmp-sm-k26-revA.dts | 245 * With the FW fix, stdp4320 should respond to address 0x73 only.
|
