Searched refs:Completion (Results 1 – 9 of 9) sorted by relevance
111 Poisoned TLP | Flow Control Protocol | Completion Timeout | \112 Completer Abort | Unexpected Completion | Receiver Overflow | \
786 DECLARE_COMPLETION_ONSTACK(Completion); in DAC960_ExecuteCommand()788 Command->Completion = &Completion; in DAC960_ExecuteCommand()796 wait_for_completion(&Completion); in DAC960_ExecuteCommand()2016 struct completion *Completion = &Completions[Channel]; in DAC960_V1_ReadDeviceConfiguration() local2018 init_completion(Completion); in DAC960_V1_ReadDeviceConfiguration()2021 Command->Completion = Completion; in DAC960_V1_ReadDeviceConfiguration()2065 struct completion *Completion = &Completions[Channel]; in DAC960_V1_ReadDeviceConfiguration() local2067 wait_for_completion(Completion); in DAC960_V1_ReadDeviceConfiguration()2077 Command->Completion = Completion; in DAC960_V1_ReadDeviceConfiguration()2091 wait_for_completion(Completion); in DAC960_V1_ReadDeviceConfiguration()[all …]
2230 struct completion *Completion; member
117 2/ Completion callback routines cannot submit new operations. This172 1/ Completion callbacks are expected to happen in tasklet context
269 chipset, you may experience the "133-Mhz Mode Split Completion Data288 section 56, "133-MHz Mode Split Completion Data Corruption" for more
83 flag is set. Completion handlers for isochronous URBs should only see
117 Completion must be signalled by a call to capi_ctr_ready().125 Completion must be signalled by a call to capi_ctr_down().
109 Description: Completion vector used for the first RDMA channel.
61 ** Completion of request: