| /linux-6.1.9/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-6.1.9/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-6.1.9/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()
|
| /linux-6.1.9/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);
|
| /linux-6.1.9/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-6.1.9/Documentation/devicetree/bindings/rtc/ |
| D | isil,isl12026.txt | 4 registers respond at bus address 0x6f, and the EEPROM array responds
|
| /linux-6.1.9/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-6.1.9/Documentation/devicetree/bindings/media/i2c/ |
| D | chrontel,ch7322.yaml | 39 the device will respond to power status requests with "standby"
|
| /linux-6.1.9/drivers/net/wwan/iosm/ |
| D | iosm_ipc_mux_codec.h | 280 size_t res_size, bool blocking, bool respond);
|
| /linux-6.1.9/Documentation/driver-api/xilinx/ |
| D | eemi.rst | 17 device to issue or respond to power management requests.
|
| /linux-6.1.9/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-6.1.9/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-6.1.9/Documentation/devicetree/bindings/input/touchscreen/ |
| D | ti,tsc2005.yaml | 44 if the touchscreen does not respond after the configured time
|
| /linux-6.1.9/Documentation/w1/masters/ |
| D | omap-hdq.rst | 29 does not respond with a presence pulse as it does in the 1-Wire protocol.
|
| /linux-6.1.9/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-6.1.9/Documentation/devicetree/bindings/display/ |
| D | dsi-controller.yaml | 51 peripherals respond to more than a single virtual channel. In that
|
| /linux-6.1.9/Documentation/driver-api/pldmfw/ |
| D | index.rst | 66 the device. For each component, the firmware may respond with an
|
| /linux-6.1.9/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-6.1.9/Documentation/scsi/ |
| D | megaraid.rst | 10 Different classes of controllers from LSI Logic accept and respond to the
|
| /linux-6.1.9/Documentation/filesystems/ |
| D | befs.rst | 34 respond to the address given above...
|
| /linux-6.1.9/Documentation/usb/ |
| D | raw-gadget.rst | 25 descriptors. Note that the UDC driver might respond to some requests on
|
| /linux-6.1.9/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
|