Searched refs:respond (Results 1 – 9 of 9) sorted by relevance
156 struct u132_respond respond[RESPOND_SIZE]; member335 struct u132_respond *respond = &ftdi->respond[RESPOND_MASK & in ftdi_elan_abandon_completions() local337 *respond->result = -ESHUTDOWN; in ftdi_elan_abandon_completions()338 *respond->value = 0; in ftdi_elan_abandon_completions()339 complete(&respond->wait_completion); in ftdi_elan_abandon_completions()1065 struct u132_respond *respond = &ftdi->respond[ in ftdi_elan_respond_engine() local1074 *respond->value = data; in ftdi_elan_respond_engine()1075 *respond->result = 0; in ftdi_elan_respond_engine()1076 complete(&respond->wait_completion); in ftdi_elan_respond_engine()1354 struct u132_respond *respond = &ftdi->respond[ in ftdi_elan_read_reg() local[all …]
470 goto respond; in hidg_setup()506 goto respond; in hidg_setup()514 goto respond; in hidg_setup()535 respond: in hidg_setup()
393 u8 command[4], respond[2], command_size, respond_size; in dvbsky_ci_ctrl() local408 respond, respond_size); in dvbsky_ci_ctrl()412 *mem = respond[1]; in dvbsky_ci_ctrl()
165 problems, but the board would not respond beyond that point. When a check was
125 visorchannel_signalremove() functions to respond to and initiate activity
631 goto respond; in fwtty_port_handler()668 respond: in fwtty_port_handler()
1792 * Bitmask of ids to respond as a target.
939 * and respond as quickly as possible to the standard
1701 * and respond as quickly as possible to the standard