Home
last modified time | relevance | path

Searched refs:respond (Results 1 – 25 of 126) sorted by relevance

123456

/OK3568_Linux_fs/kernel/drivers/usb/misc/
H A Dftdi-elan.c152 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 …]
/OK3568_Linux_fs/kernel/drivers/usb/gadget/function/
H A Df_hid.c664 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()
/OK3568_Linux_fs/kernel/Documentation/misc-devices/
H A Deeprom.rst68 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
/OK3568_Linux_fs/kernel/net/tipc/
H A Ddiscover.c209 bool respond = false; in tipc_disc_rcv() local
250 &maddr, &respond, &dupl_addr); in tipc_disc_rcv()
253 if (!respond) in tipc_disc_rcv()
H A Dnode.h96 bool *respond, bool *dupl_addr);
/OK3568_Linux_fs/yocto/meta-openembedded/meta-oe/recipes-extended/rarpd/rarpd/
H A D0001-rarpd.8-add-man-file.patch40 +) before it decides to respond to the RARP request.
60 +will not respond to the request.
/OK3568_Linux_fs/kernel/Documentation/devicetree/bindings/iio/pressure/
H A Dms5611.txt7 - reg: the I2C address or SPI chip select the device will respond to
H A Dzpa2326.txt7 - reg: the I2C address or SPI chip select the device will respond to
/OK3568_Linux_fs/buildroot/package/openzwave/
H A DConfig.in11 manipulate and respond to devices on a Z-Wave network,
/OK3568_Linux_fs/kernel/Documentation/devicetree/bindings/rtc/
H A Disil,isl12026.txt4 registers respond at bus address 0x6f, and the EEPROM array responds
/OK3568_Linux_fs/yocto/poky/meta/recipes-connectivity/nfs-utils/nfs-utils/
H A Dnfs-utils-debianize-start-statd.patch20 # statd already running - must have been slow to respond.
/OK3568_Linux_fs/kernel/Documentation/devicetree/bindings/input/touchscreen/
H A Dtsc2005.txt15 - ti,esd-recovery-timeout-ms : integer, if the touchscreen does not respond after
/OK3568_Linux_fs/kernel/Documentation/driver-api/xilinx/
H A Deemi.rst17 device to issue or respond to power management requests.
/OK3568_Linux_fs/yocto/poky/documentation/test-manual/
H A Dtest-process.rst30 branch. If not successful, someone would respond to the changes on the
80 - QA teams respond to the email saying which tests they plan to run and
/OK3568_Linux_fs/kernel/drivers/media/usb/dvb-usb-v2/
H A Ddvbsky.c350 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()
/OK3568_Linux_fs/kernel/Documentation/i2c/
H A Dten-bit-addresses.rst8 address 0x10 (though a single device could respond to both of them).
H A Di2c-stub.rst16 quick commands to the specified addresses; it will respond to the other
/OK3568_Linux_fs/kernel/Documentation/process/
H A D6.Followthrough.rst44 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
/OK3568_Linux_fs/kernel/Documentation/devicetree/bindings/iio/
H A Dst-sensors.txt9 - reg: the I2C or SPI address the device will respond to
/OK3568_Linux_fs/kernel/Documentation/w1/masters/
H A Domap-hdq.rst29 does not respond with a presence pulse as it does in the 1-Wire protocol.
/OK3568_Linux_fs/kernel/Documentation/driver-api/pldmfw/
H A Dindex.rst66 the device. For each component, the firmware may respond with an
/OK3568_Linux_fs/kernel/Documentation/scsi/
H A Dmegaraid.rst10 Different classes of controllers from LSI Logic accept and respond to the
/OK3568_Linux_fs/u-boot/board/Synology/ds109/
H A Dopenocd.cfg26 # Furthermore, the JTAG interface doesn't respond at all when
/OK3568_Linux_fs/buildroot/package/ipmitool/
H A D0008-fru-Fix-buffer-overflow-vulnerabilities.patch11 respond with more than the requested amount of data; it uses the
/OK3568_Linux_fs/yocto/meta-openembedded/meta-oe/recipes-kernel/ipmitool/ipmitool/
H A D0001-fru-Fix-buffer-overflow-vulnerabilities.patch11 respond with more than the requested amount of data; it uses the

123456