| /kernel/linux/linux-5.10/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 …]
|
| /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-5.10/drivers/usb/gadget/function/ |
| D | f_hid.c | 664 goto respond; in hidg_setup()
672 goto respond; in hidg_setup()
680 goto respond; in hidg_setup()
690 goto respond; in hidg_setup()
705 goto respond; in hidg_setup()
715 goto respond; in hidg_setup()
733 goto respond; in hidg_setup()
741 goto respond; in hidg_setup()
762 respond: in hidg_setup()
|
| /kernel/linux/linux-5.10/Documentation/devicetree/bindings/iio/pressure/ |
| D | ms5611.txt | 7 - reg: the I2C address or SPI chip select the device will respond to
|
| D | zpa2326.txt | 7 - reg: the I2C address or SPI chip select the device will respond to
|
| /kernel/linux/linux-5.10/net/tipc/ |
| D | discover.c | 209 bool respond = false; in tipc_disc_rcv() local
250 &maddr, &respond, &dupl_addr); in tipc_disc_rcv()
253 if (!respond) in tipc_disc_rcv()
|
| D | node.h | 96 bool *respond, bool *dupl_addr);
|
| D | node.c | 1147 bool *respond, bool *dupl_addr) in tipc_node_check_dest() argument
1163 *respond = false; in tipc_node_check_dest()
1190 *respond = true; in tipc_node_check_dest()
1208 *respond = true; in tipc_node_check_dest()
1228 *respond = true; in tipc_node_check_dest()
1240 *respond = true; in tipc_node_check_dest()
1262 *respond = false; in tipc_node_check_dest()
|
| /kernel/linux/linux-5.10/Documentation/devicetree/bindings/rtc/ |
| D | isil,isl12026.txt | 4 registers respond at bus address 0x6f, and the EEPROM array responds
|
| /kernel/linux/linux-5.10/Documentation/devicetree/bindings/input/touchscreen/ |
| D | tsc2005.txt | 15 - ti,esd-recovery-timeout-ms : integer, if the touchscreen does not respond after
|
| /kernel/linux/linux-5.10/Documentation/driver-api/xilinx/ |
| D | eemi.rst | 17 device to issue or respond to power management requests.
|
| /kernel/linux/linux-5.10/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
|
| /kernel/linux/linux-5.10/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()
|
| /kernel/linux/linux-5.10/Documentation/devicetree/bindings/iio/ |
| D | st-sensors.txt | 9 - reg: the I2C or SPI address the device will respond to
|
| /kernel/linux/linux-5.10/Documentation/w1/masters/ |
| D | omap-hdq.rst | 29 does not respond with a presence pulse as it does in the 1-Wire protocol.
|
| /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/Documentation/driver-api/pldmfw/ |
| D | index.rst | 66 the device. For each component, the firmware may respond with an
|
| /kernel/linux/linux-5.10/Documentation/scsi/ |
| D | megaraid.rst | 10 Different classes of controllers from LSI Logic accept and respond to the
|
| D | BusLogic.rst | 312 respond to synchronous transfer negotiation for UltraSCSI speed. AutoSCSI
330 The BT-948/958/958D will not respond to any of the ISA compatible I/O ports
331 that previous BusLogic SCSI Host Adapters respond to. This driver supports
381 UltraSCSI operation, or where existing SCSI devices do not properly respond
524 respond correctly when Logical Units above 0 are addressed.
|
| /kernel/linux/linux-5.10/Documentation/usb/ |
| D | raw-gadget.rst | 20 descriptors. However note, that the UDC driver might respond to some
|
| /kernel/linux/linux-5.10/Documentation/filesystems/ |
| D | befs.rst | 34 respond to the address given above...
|
| /kernel/linux/linux-5.10/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
|
| /kernel/linux/linux-5.10/Documentation/driver-api/ |
| D | switchtec.rst | 26 respond with a 4-byte return code and up to 1KB of command-specific
|
| /kernel/linux/linux-5.10/Documentation/hid/ |
| D | uhid.rst | 49 register the device. UHID will respond with an UHID_START event. You can now
176 parallel. However, if you fail to respond with a UHID_GET_REPORT_REPLY, the
|