Lines Matching refs:runCommand
47 runCommand request is made from the work-loop's thread, it doens't check for a
57 CAUTION: The runAction and runCommand functions can not be called from an interrupt context. But attemptCommand can, though it may return an error
68 a runCommand is executed by a client. Cast to this type when you want a C++
70 through from the runCommand to the action callout.
113 IOCommandGate calls runCommand. NB Can be a C++ member function but caller
123 /*! @function runCommand
128 client's thread runCommand will sleep until the work-loop's gate opens for
137 virtual IOReturn runCommand(void *arg0 = 0, void *arg1 = 0,
207 @discussion When a command gate is disabled all future calls to runAction and runCommand will stall until the gate is enable()d later. This can be used to block client threads when a system sleep is requested. The IOWorkLoop thread itself will never stall, even when making runAction/runCommand calls. This call must be made from a gated context, to clear potential race conditions. */
212 @discussion Enable the command gate. The attemptAction/attemptCommand calls will now be enabled and can succeeed. Stalled runCommand/runAction calls will be woken up. */