Searched refs:gIOMatchedNotification (Results 1 - 3 of 3) sorted by relevance
| /darwin-on-arm/xnu/iokit/Kernel/ |
| H A D | IOService.cpp | 135 const OSSymbol * gIOMatchedNotification; variable
318 gIOMatchedNotification = OSSymbol::withCStringNoCopy(
356 && gIOPublishNotification && gIOMatchedNotification
3163 deliverNotification( gIOMatchedNotification,
3828 else if( (type == gIOMatchedNotification)
3979 notify = IOService::setNotification( gIOMatchedNotification, matching,
|
| H A D | IOUserClient.cpp | 1725 else if( (sym == gIOMatchedNotification)
|
| /darwin-on-arm/xnu/iokit/IOKit/ |
| H A D | IOService.h | 128 extern const OSSymbol * gIOMatchedNotification;
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.
664 <br> <code>gIOMatchedNotification</code> Delivered when an IOService object has been matched with all client drivers, and they have been probed and started.
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.
687 <br> <code>gIOMatchedNotification</code> Delivered when an IOService object has been matched with all client drivers, and they have been probed and started.
|
Completed in 38 milliseconds