iokit/IOKit/IOService.h

490     @param options Options for the open. The provider family may implement options for open; IOService defines only <code>kIOServiceSeize</code> to request the device be withdrawn from its current owner.
517     @discussion IOService calls this method in its subclasses in response to the @link open open@/link method, so the subclass may implement the request. The default implementation provides single owner access to an IOService object via <code>open</code>. The object is locked via @link lockForArbitration lockForArbitration@/link before <code>handleOpen</code> is called.
528     @discussion IOService calls this method in its subclasses in response to the @link close close@/link method, so the subclass may implement the request. The default implementation provides single owner access to an IOService object via @link open open@/link. The object is locked via @link lockForArbitration lockForArbitration@/link before <code>handleClose</code> is called.
537     @discussion IOService calls this method in its subclasses in response to the @link open open@/link method, so the subclass may implement the request. The default implementation provides single owner access to an IOService object via @link open open@/link. The object is locked via @link lockForArbitration lockForArbitration@/link before <code>handleIsOpen</code> is called.
568     @param isSuccessRequired If a request for access to an IOService object should be denied if it is terminated, pass <code>false</code>, otherwise pass <code>true</code>. */
583     @result result of the terminate request on the client. */
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.
672     @result An instance of an IONotifier object that can be used to control or destroy the notification request. */
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.
695     @result An instance of an IONotifier object that can be used to control or destroy the notification request. */
933     @discussion The platform expert or other drivers may implement various functions to control hardware features.  <code>callPlatformFunction</code> allows any IOService object to access these functions. Normally <code>callPlatformFunction</code> is called on a service's provider. The provider services the request or passes it to its provider. The system's IOPlatformExpert subclass catches functions it knows about and redirects them into other parts of the service plane. If the IOPlatformExpert subclass cannot execute the function, the base class is called. The IOPlatformExpert base class attempts to find a service to execute the function by looking up the function name in an IOResources name space. A service may publish a service using <code>publishResource(functionName, this)</code>. If no service can be found to execute the function an error is returned.
1085     @discussion For bus families that do not usually detect device addition or removal, this method represents an external request (eg. from a utility application) to rescan and publish or remove found devices.
1148     @discussion A non kernel client may request a connection be opened via the @link //apple_ref/c/func/IOServiceOpen IOServiceOpen@/link library function, which will call this method in an IOService object. The rules and capabilities of user level clients are family dependent, and use the functions of the IOUserClient class for support. IOService's implementation returns <code>kIOReturnUnsupported</code>, so any family supporting user clients must implement this method.
1421     <code>makeUsable</code> is implemented using @link changePowerStateToPriv changePowerStateToPriv@/link. Subsequent requests for lower power, such as from <code>changePowerStateToPriv</code>, will pre-empt this request.
1603     @result The driver must return <code>IOPMAckImplied</code> if it has complied with the request when it returns. Otherwise if it has started the process of changing power state but not finished it, the driver should return a number of microseconds which is an upper limit of the time it will need to finish. Then, when it has completed the power switch, it should call @link acknowledgeSetPowerState acknowledgeSetPowerState@/link. */
1701     Drivers may eliminate the influence of the <code>changePowerStateTo</code> method on power state one of two ways. See @link powerOverrideOnPriv powerOverrideOnPriv@/link to ignore the method's influence, or call <code>changePowerStateTo(0)</code> in the driver's <code>start</code> routine to remove the <code>changePowerStateTo</code> method's power request.
1804 	static void releasePMRequest( IOPMRequest * request );
1811 	void addPowerChild1( IOPMRequest * request );
1812 	void addPowerChild2( IOPMRequest * request );
1813 	void addPowerChild3( IOPMRequest * request );
1816 	void handlePMstop( IOPMRequest * request );
1817 	void handleRegisterPowerDriver( IOPMRequest * request );
1818 	bool handleAcknowledgePowerChange( IOPMRequest * request );
1819 	void handlePowerDomainWillChangeTo( IOPMRequest * request );
1820 	void handlePowerDomainDidChangeTo( IOPMRequest * request );
1821 	void handleRequestPowerState( IOPMRequest * request );
1822 	void handlePowerOverrideChanged( IOPMRequest * request );
1823 	void handleActivityTickle( IOPMRequest * request );
1824 	void handleInterestChanged( IOPMRequest * request );
1825     void handleSynchronizePowerTree( IOPMRequest * request );
1826 	void submitPMRequest( IOPMRequest * request );
1827 	void submitPMRequest( IOPMRequest ** request, IOItemCount count );
1828 	void executePMRequest( IOPMRequest * request );
1829 	bool servicePMRequest( IOPMRequest * request, IOPMWorkQueue * queue  );
1830 	bool retirePMRequest(  IOPMRequest * request, IOPMWorkQueue * queue );
1831 	bool servicePMRequestQueue( IOPMRequest * request, IOPMRequestQueue * queue );
1832 	bool servicePMReplyQueue( IOPMRequest * request, IOPMRequestQueue * queue );
1833 	bool servicePMFreeQueue( IOPMRequest * request, IOPMCompletionQueue * queue );
1840 	bool isPMBlocked( IOPMRequest * request, int count );