Searched refs:kIOServiceRequired (Results 1 - 4 of 4) sorted by relevance

/xnu-2782.1.97/iokit/Kernel/
H A DIOCatalogue.cpp569 if ( !service->terminate(kIOServiceRequired|kIOServiceSynchronous) ) {
H A DIOService.cpp2041 options |= kIOServiceRequired;
2380 options |= kIOServiceRequired;
H A DIOUserClient.cpp4604 if ( !service->terminate( kIOServiceRequired
/xnu-2782.1.97/iokit/IOKit/
H A DIOService.h84 kIOServiceRequired = 0x00000001, enumerator in enum:__anon644
595 @discussion Registering an IOService object informs possible clients of its existance and instantiates drivers that may be used with it; <code>terminate</code> involves the opposite process of informing clients that an IOService object is no longer able to be used and will be destroyed. By default, if any client has the service open, <code>terminate</code> fails. If the <code>kIOServiceRequired</code> flag is passed however, <code>terminate</code> will be successful though further progress in the destruction of the IOService object will not proceed until the last client has closed it. The service will be made inactive immediately upon successful termination, and all its clients will be notified via their @link message message@/link method with a message of type <code>kIOMessageServiceIsTerminated</code>. Both these actions take place on the caller's thread. After the IOService object is made inactive, further matching or attach calls will fail on it. Each client has its @link stop stop@/link method called upon their close of an inactive IOService object , or on its termination if they do not have it open. After <code>stop</code>, @link detach detach@/link is called in each client. When all clients have been detached, the @link finalize finalize@/link method is called in the inactive service. The termination process is inherently asynchronous because it will be deferred until all clients have chosen to close.

Completed in 125 milliseconds