Lines Matching full:process

49 Detachment Process
72 Note that the detachment process is governed fully by the EC. The
74 commands from user-space to the EC, i.e. it does not influence this process.
76 The detachment process is started with the user pressing the *detach* button
106   detachment process. Furthermore, the EC will send a detach-request event,
107   similar to the user pressing the detach-button to cancel said process (see
123   No other actions will be performed, i.e. the detachment process will neither
127 - Execute ``SDTX_IOCTL_LATCH_CANCEL``. This will abort the detachment process,
131   does not trigger a new detachment process if none is currently in
134 - Do nothing. The detachment process eventually times out as described in
142 received the corresponding response concluding the process), the detachment
143 process is canceled on the EC-level and an identical event is being sent.
145 detachment process.
147 The detachment process may further be canceled by the EC due to hardware
214      - Detachment process timed out while the latch was locked.
301      - Detachment process initiated/aborted.
306      - EC canceled detachment process.
328 Sent when a detachment process is started or, if in progress, aborted by the
337 Sent when a detachment process is canceled by the EC due to unfulfilled
525      - Cancel detachment process.
577 latch when sent during an ongoing detachment process. It will be silently
586 detachment-process is active, detachment is requested. Otherwise the
587 currently active detachment-process will be aborted.
589 If a detachment process is canceled by this operation, a generic detachment
600 detachment process, this command causes the latch to be opened immediately.
613 command can be used to keep the detachment process alive while work required
624 Cancels detachment in progress (if any). If a detachment process is canceled