Searched refs:gIOTerminatedNotification (Results 1 - 3 of 3) sorted by relevance
/darwin-on-arm/xnu/iokit/Kernel/ |
H A D | IOService.cpp | 137 const OSSymbol * gIOTerminatedNotification; variable 322 gIOTerminatedNotification = OSSymbol::withCStringNoCopy( 357 && gIOTerminatedNotification && gIOServiceKey 1780 victim->deliverNotification( gIOTerminatedNotification, 0, 0xffffffff ); 3831 else if( type == gIOTerminatedNotification) 4040 || (type == gIOTerminatedNotification)) {
|
H A D | IOUserClient.cpp | 1728 else if( sym == gIOTerminatedNotification)
|
/darwin-on-arm/xnu/iokit/IOKit/ |
H A D | IOService.h | 130 extern const OSSymbol * gIOTerminatedNotification; 660 @discussion IOService will deliver notifications of changes in state of an IOService object to registered clients. The type of notification is specified by a symbol, for example <code>gIOMatchedNotification</code> or <code>gIOTerminatedNotification</code>, and notifications will only include IOService objects that match the supplied matching dictionary. Notifications are ordered by a priority set with <code>addNotification</code>. When the notification is installed, its handler will be called with each of any currently existing IOService objects that are in the correct state (eg. registered) and match the supplied matching dictionary, avoiding races between finding preexisting and new IOService events. The notification request is identified by an instance of an IONotifier object, through which it can be enabled, disabled, or removed. <code>addNotification</code> consumes a retain count on the matching dictionary when the notification is removed. 666 <br> <code>gIOTerminatedNotification</code> Delivered after an IOService object has been terminated, during its finalize stage. 683 @discussion IOService will deliver notifications of changes in state of an IOService object to registered clients. The type of notification is specified by a symbol, for example <code>gIOMatchedNotification</code> or <code>gIOTerminatedNotification</code>, and notifications will only include IOService objects that match the supplied matching dictionary. Notifications are ordered by a priority set with <code>addNotification</code>. When the notification is installed, its handler will be called with each of any currently existing IOService objects that are in the correct state (eg. registered) and match the supplied matching dictionary, avoiding races between finding preexisting and new IOService events. The notification request is identified by an instance of an IONotifier object, through which it can be enabled, disabled, or removed. <code>addMatchingNotification</code> does not consume a reference on the matching dictionary when the notification is removed, unlike addNotification. 689 <br> <code>gIOTerminatedNotification</code> Delivered after an IOService object has been terminated, during its finalize stage.
|
Completed in 42 milliseconds