]> git.saurik.com Git - apple/xnu.git/blame - iokit/IOKit/IOService.h
xnu-201.tar.gz
[apple/xnu.git] / iokit / IOKit / IOService.h
CommitLineData
1c79356b
A
1/*
2 * Copyright (c) 1998-2000 Apple Computer, Inc. All rights reserved.
3 *
4 * @APPLE_LICENSE_HEADER_START@
5 *
6 * The contents of this file constitute Original Code as defined in and
7 * are subject to the Apple Public Source License Version 1.1 (the
8 * "License"). You may not use this file except in compliance with the
9 * License. Please obtain a copy of the License at
10 * http://www.apple.com/publicsource and read it before using this file.
11 *
12 * This Original Code and all software distributed under the License are
13 * distributed on an "AS IS" basis, WITHOUT WARRANTY OF ANY KIND, EITHER
14 * EXPRESS OR IMPLIED, AND APPLE HEREBY DISCLAIMS ALL SUCH WARRANTIES,
15 * INCLUDING WITHOUT LIMITATION, ANY WARRANTIES OF MERCHANTABILITY,
16 * FITNESS FOR A PARTICULAR PURPOSE OR NON-INFRINGEMENT. Please see the
17 * License for the specific language governing rights and limitations
18 * under the License.
19 *
20 * @APPLE_LICENSE_HEADER_END@
21 */
22/*
23 * Copyright (c) 1998,1999 Apple Computer, Inc. All rights reserved.
24 *
25 * HISTORY
26 *
27 */
28
29
30#ifndef _IOKIT_IOSERVICE_H
31#define _IOKIT_IOSERVICE_H
32
33#include <IOKit/IORegistryEntry.h>
34#include <IOKit/IOReturn.h>
35#include <IOKit/IODeviceMemory.h>
36#include <IOKit/IONotifier.h>
37#include <IOKit/IOLocks.h>
38
39#include <IOKit/IOKitDebug.h>
40#include <IOKit/IOInterrupts.h>
41
42class IOPMinformee;
43class IOPowerConnection;
44
45#include <IOKit/pwr_mgt/IOPMpowerState.h>
46#include <IOKit/IOServicePM.h>
47
48extern "C" {
49#include <kern/thread_call.h>
50}
51
52enum {
53 kIODefaultProbeScore = 0
54};
55
56// masks for getState()
57enum {
58 kIOServiceInactiveState = 0x00000001,
59 kIOServiceRegisteredState = 0x00000002,
60 kIOServiceMatchedState = 0x00000004,
61 kIOServiceFirstPublishState = 0x00000008,
62 kIOServiceFirstMatchState = 0x00000010
63};
64
1c79356b 65enum {
0b4e3aa0 66 // options for registerService()
1c79356b 67 kIOServiceExclusive = 0x00000001,
1c79356b 68
0b4e3aa0
A
69 // options for terminate()
70 kIOServiceRequired = 0x00000001,
71 kIOServiceTerminate = 0x00000004,
72
73 // options for registerService() & terminate()
74 kIOServiceSynchronous = 0x00000002,
75 // options for registerService()
76 kIOServiceAsynchronous = 0x00000008
1c79356b
A
77};
78
79// options for open()
80enum {
81 kIOServiceSeize = 0x00000001,
82 kIOServiceFamilyOpenOptions = 0xffff0000
83};
84
85// options for close()
86enum {
87 kIOServiceFamilyCloseOptions = 0xffff0000
88};
89
90typedef void * IONotificationRef;
91
92extern const IORegistryPlane * gIOServicePlane;
93extern const IORegistryPlane * gIOPowerPlane;
94
95extern const OSSymbol * gIOResourcesKey;
96extern const OSSymbol * gIOResourceMatchKey;
97extern const OSSymbol * gIOProviderClassKey;
98extern const OSSymbol * gIONameMatchKey;
99extern const OSSymbol * gIONameMatchedKey;
100extern const OSSymbol * gIOPropertyMatchKey;
101extern const OSSymbol * gIOLocationMatchKey;
102extern const OSSymbol * gIOPathMatchKey;
103extern const OSSymbol * gIOMatchCategoryKey;
104extern const OSSymbol * gIODefaultMatchCategoryKey;
105extern const OSSymbol * gIOMatchedServiceCountKey;
106
107extern const OSSymbol * gIOUserClientClassKey;
108extern const OSSymbol * gIOKitDebugKey;
109extern const OSSymbol * gIOServiceKey;
110
111extern const OSSymbol * gIOCommandPoolSizeKey;
112
113extern const OSSymbol * gIOPublishNotification;
114extern const OSSymbol * gIOFirstPublishNotification;
115extern const OSSymbol * gIOMatchedNotification;
116extern const OSSymbol * gIOFirstMatchNotification;
117extern const OSSymbol * gIOTerminatedNotification;
118
119extern const OSSymbol * gIOGeneralInterest;
120extern const OSSymbol * gIOBusyInterest;
0b4e3aa0 121extern const OSSymbol * gIOOpenInterest;
1c79356b 122extern const OSSymbol * gIOAppPowerStateInterest;
0b4e3aa0 123extern const OSSymbol * gIOPriorityPowerStateInterest;
1c79356b
A
124
125extern const OSSymbol * gIODeviceMemoryKey;
126extern const OSSymbol * gIOInterruptControllersKey;
127extern const OSSymbol * gIOInterruptSpecifiersKey;
128
129extern SInt32 IOServiceOrdering( const OSMetaClassBase * inObj1, const OSMetaClassBase * inObj2, void * ref );
130
131typedef void (*IOInterruptAction)( OSObject * target, void * refCon,
132 IOService * nub, int source );
133
134/*! @typedef IOServiceNotificationHandler
135 @param target Reference supplied when the notification was registered.
136 @param refCon Reference constant supplied when the notification was registered.
137 @param newService The IOService object the notification is delivering. It is retained for the duration of the handler's invocation and doesn't need to be released by the handler. */
138
139typedef bool (*IOServiceNotificationHandler)( void * target, void * refCon,
140 IOService * newService );
141
142/*! @typedef IOServiceInterestHandler
143 @param target Reference supplied when the notification was registered.
144 @param refCon Reference constant supplied when the notification was registered.
145 @param messageType Type of the message - IOKit defined in IOKit/IOMessage.h or family specific.
146 @param provider The IOService object who is delivering the notification. It is retained for the duration of the handler's invocation and doesn't need to be released by the handler.
147 @param messageArgument An argument for message, dependent on its type.
148 @param argSize Non zero if the argument represents a struct of that size, used when delivering messages outside the kernel. */
149
150typedef IOReturn (*IOServiceInterestHandler)( void * target, void * refCon,
151 UInt32 messageType, IOService * provider,
152 void * messageArgument, vm_size_t argSize );
153
154typedef void (*IOServiceApplierFunction)(IOService * service, void * context);
155typedef void (*OSObjectApplierFunction)(OSObject * object, void * context);
156
157class IOUserClient;
158class IOPlatformExpert;
159
160/*! @class IOService : public IORegistryEntry
161 @abstract The base class for most families, devices and drivers.
162 @discussion The IOService base class defines APIs used to publish services, instantiate other services based on the existance of a providing service (ie. driver stacking), destroy a service and its dependent stack, notify interested parties of service state changes, and general utility functions useful across all families.
163
164Types of service are specified with a matching dictionary that describes properties of the service. For example, a matching dictionary might describe any IOUSBDevice (or subclass), an IOUSBDevice with a certain class code, or a IOPCIDevice with a set of OpenFirmware matching names or device & vendor IDs. Since the matching dictionary is interpreted by the family which created the service, as well as generically by IOService, the list of properties considered for matching depends on the familiy.
165
166Matching dictionaries are associated with IOService classes by the catalogue, as driver property tables, and also supplied by clients of the notification APIs.
167
168IOService provides matching based on c++ class (via OSMetaClass dynamic casting), registry entry name, a registry path to the service (which includes OpenFirmware paths), a name assigned by BSD, or by its location (its point of attachment).
169
170<br><br>Driver Instantiation by IOService<br><br>
171
172Drivers are subclasses of IOService, and their availability is managed through the catalogue. They are instantiated based on the publication of an IOService they use (for example, an IOPCIDevice or IOUSBDevice), or when they are added to the catalogue and the IOService(s) they use are already available.
173
174When an IOService (the "provider") is published with the registerService() method, the matching and probing process begins, which is always single threaded per provider. A list of matching dictionaries from the catalog and installed publish notification requests, that successfully match the IOService, is constructed, with ordering supplied by kIOProbeScoreKey ("IOProbeScore") property in the dictionary, or supplied with the notification.
175
176Each entry in the list is then processed in order - for notifications, the notification is delivered, for driver property tables a lot more happens.
177
178The driver class is instantiated and init() called with its property table. The new driver instance is then attached to the provider, and has its probe() method called with the provider as an argument. The default probe method does nothing but return success, but a driver may implement this method to interrogate the provider to make sure it can work with it. It may also modify its probe score at this time. After probe, the driver is detached and the next in the list is considered (ie. attached, probed, and detached).
179
180When the probing phase is complete, the list consists of successfully probed drivers, in order of their probe score (after adjustment during the probe() call). The list is then divided into categories based on the kIOMatchCategoryKey property ("IOMatchCategory"); drivers without a match category are all considered in one default category. Match categories allow multiple clients of a provider to be attached and started, though the provider may also enforce open/close semantics to gain active access to it.
181
182For each category, the highest scoring driver in that category is attached to the provider, and its start() method called. If start() is successful, the rest of the drivers in the same match category are discarded, otherwise the next highest scoring driver is started, and so one.
183
184The driver should only consider itself in action when the start method is called, meaning it has been selected for use on the provider, and consuming that particular match category. It should also be prepared to be allocated, probed and freed even if the probe was sucessful.
185
186After the drivers have all synchronously been started, the installed "matched" notifications that match the registered IOService are delivered.
187
188<br><br>Properties used by IOService<br><br>
189
190 kIOClassKey, extern const OSSymbol * gIOClassKey, "IOClass"
191<br>
192Class of the driver to instantiate on matching providers.
193<br>
194<br>
195 kIOProviderClassKey, extern const OSSymbol * gIOProviderClassKey, "IOProviderClass"
196<br>
197Class of the provider(s) to be considered for matching, checked with OSDynamicCast so subclasses will also match.
198<br>
199<br>
200 kIOProbeScoreKey, extern const OSSymbol * gIOProbeScoreKey, "IOProbeScore"
201<br>
202The probe score initially used to order multiple matching drivers.
203<br>
204<br>
205 kIOMatchCategoryKey, extern const OSSymbol * gIOMatchCategoryKey, "IOMatchCategory"
206<br>
207A string defining the driver category for matching purposes. All drivers with no IOMatchCategory property are considered to be in the same default category. Only one driver in a category can be started on each provider.
208<br>
209<br>
210 kIONameMatchKey, extern const OSSymbol * gIONameMatchKey, "IONameMatch"
211<br>
212A string or collection of strings that match the provider's name. The comparison is implemented with the IORegistryEntry::compareNames method, which supports a single string, or any collection (OSArray, OSSet, OSDictionary etc.) of strings. IOService objects with OpenFirmware device tree properties (eg. IOPCIDevice) will also be matched based on that standard's "compatible", "name", "device_type" properties. The matching name will be left in the driver's property table in the kIONameMatchedKey property.
213<br>
214Examples
215<br>
216 &ltkey&gtIONameMatch&lt/key&gt <br>
217 &ltstring&gtpci106b,7&ltstring&gt
218<br>
219For a list of possible matching names, a serialized array of strings should used, eg.
220<br>
221 &ltkey&gtIONameMatch&lt/key&gt <br>
222 &ltarray&gt <br>
223 &ltstring&gtAPPL,happy16&lt/string&gt <br>
224 &ltstring&gtpci106b,7&lt/string&gt <br>
225 &lt/array&gt
226<br>
227<br>
228 kIONameMatchedKey, extern const OSSymbol * gIONameMatchedKey, "IONameMatched"
229<br>
230The name successfully matched name from the kIONameMatchKey property will be left in the driver's property table as the kIONameMatchedKey property.
231<br>
232<br>
233 kIOPropertyMatchKey, extern const OSSymbol * gIOPropertyMatchKey, "IOPropertyMatch"
234<br>
235A dictionary of properties that each must exist in the matching IOService and compare sucessfully with the isEqualTo method.
236 &ltkey&gtIOPropertyMatch&lt/key&gt <br>
237 &ltdictionary&gt <br>
238 &ltkey&gtname&lt/key&gt <br>
239 &ltstring&gtAPPL,meek8&lt/string&gt <br>
240 &lt/dictionary&gt
241<br>
242<br>
243 kIOUserClientClassKey, extern const OSSymbol * gIOUserClientClassKey, "IOUserClientClass"
244<br>
245The class name that the service will attempt to allocate when a user client connection is requested. First the device nub is queried, then the nub's provider is queried by default.
246<br>
247<br>
248 kIOKitDebugKey, extern const OSSymbol * gIOKitDebugKey, "IOKitDebug"
249<br>
250Set some debug flags for logging the driver loading process. Flags are defined in IOKit/IOKitDebug.h, but 65535 works well.
251
252*/
253
254class IOService : public IORegistryEntry
255{
256 OSDeclareDefaultStructors(IOService)
257
258protected:
259/*! @struct ExpansionData
260 @discussion This structure will be used to expand the capablilties of this class in the future.
261 */
262 struct ExpansionData { };
263
264/*! @var reserved
265 Reserved for future use. (Internal use only) */
266 ExpansionData * reserved;
267
268private:
269 IOService * __provider;
270 SInt32 __providerGeneration;
271 IOService * __owner;
272 IOOptionBits __state[2];
273 IOOptionBits __reserved[4];
274
275 // pointer to private instance variables for power management
276 IOPMpriv * priv;
277
278protected:
279 // TRUE once PMinit has been called
280 bool initialized;
0b4e3aa0
A
281
282public:
1c79356b
A
283 // pointer to protected instance variables for power management
284 IOPMprot * pm_vars;
285
0b4e3aa0
A
286public:
287 /* methods available in Mac OS X 10.1 or later */
288/*! @function requestTerminate
289 @abstract Passes a termination up the stack.
290 @discussion When an IOService is made inactive the default behaviour is to also make any of its clients that have it as their only provider also inactive, in this way recursing the termination up the driver stack. This method allows an IOService object to override this behaviour. Returning true from this method when passed a just terminated provider will cause the client to also be terminated.
291 @param provider The terminated provider of this object.
292 @param options Options originally passed to terminate, plus kIOServiceRecursing.
293 @result true if this object should be terminated now that its provider as been. */
294
295 virtual bool requestTerminate( IOService * provider, IOOptionBits options );
296
297/*! @function willTerminate
298 @abstract Passes a termination up the stack.
299 @discussion Notification that a provider has been terminated, sent before recursing up the stack, in root-to-leaf order.
300 @param provider The terminated provider of this object.
301 @param options Options originally passed to terminate.
302 @result true return true. */
303
304 virtual bool willTerminate( IOService * provider, IOOptionBits options );
305
306/*! @function didTerminate
307 @abstract Passes a termination up the stack.
308 @discussion Notification that a provider has been terminated, sent after recursing up the stack, in leaf-to-root order.
309 @param provider The terminated provider of this object.
310 @param options Options originally passed to terminate.
311 @param defer If there is pending I/O that requires this object to persist, and the provider is not opened by this object set defer to true and call the IOService::didTerminate() implementation when the I/O completes. Otherwise, leave defer set to its default value of false.
312 @result true return true. */
313
314 virtual bool didTerminate( IOService * provider, IOOptionBits options, bool * defer );
315
1c79356b 316private:
0b4e3aa0
A
317 OSMetaClassDeclareReservedUsed(IOService, 0);
318 OSMetaClassDeclareReservedUsed(IOService, 1);
319 OSMetaClassDeclareReservedUsed(IOService, 2);
320
1c79356b
A
321 OSMetaClassDeclareReservedUnused(IOService, 3);
322 OSMetaClassDeclareReservedUnused(IOService, 4);
323 OSMetaClassDeclareReservedUnused(IOService, 5);
324 OSMetaClassDeclareReservedUnused(IOService, 6);
325 OSMetaClassDeclareReservedUnused(IOService, 7);
326 OSMetaClassDeclareReservedUnused(IOService, 8);
327 OSMetaClassDeclareReservedUnused(IOService, 9);
328 OSMetaClassDeclareReservedUnused(IOService, 10);
329 OSMetaClassDeclareReservedUnused(IOService, 11);
330 OSMetaClassDeclareReservedUnused(IOService, 12);
331 OSMetaClassDeclareReservedUnused(IOService, 13);
332 OSMetaClassDeclareReservedUnused(IOService, 14);
333 OSMetaClassDeclareReservedUnused(IOService, 15);
334 OSMetaClassDeclareReservedUnused(IOService, 16);
335 OSMetaClassDeclareReservedUnused(IOService, 17);
336 OSMetaClassDeclareReservedUnused(IOService, 18);
337 OSMetaClassDeclareReservedUnused(IOService, 19);
338 OSMetaClassDeclareReservedUnused(IOService, 20);
339 OSMetaClassDeclareReservedUnused(IOService, 21);
340 OSMetaClassDeclareReservedUnused(IOService, 22);
341 OSMetaClassDeclareReservedUnused(IOService, 23);
342 OSMetaClassDeclareReservedUnused(IOService, 24);
343 OSMetaClassDeclareReservedUnused(IOService, 25);
344 OSMetaClassDeclareReservedUnused(IOService, 26);
345 OSMetaClassDeclareReservedUnused(IOService, 27);
346 OSMetaClassDeclareReservedUnused(IOService, 28);
347 OSMetaClassDeclareReservedUnused(IOService, 29);
348 OSMetaClassDeclareReservedUnused(IOService, 30);
349 OSMetaClassDeclareReservedUnused(IOService, 31);
350 OSMetaClassDeclareReservedUnused(IOService, 32);
351 OSMetaClassDeclareReservedUnused(IOService, 33);
352 OSMetaClassDeclareReservedUnused(IOService, 34);
353 OSMetaClassDeclareReservedUnused(IOService, 35);
354 OSMetaClassDeclareReservedUnused(IOService, 36);
355 OSMetaClassDeclareReservedUnused(IOService, 37);
356 OSMetaClassDeclareReservedUnused(IOService, 38);
357 OSMetaClassDeclareReservedUnused(IOService, 39);
358 OSMetaClassDeclareReservedUnused(IOService, 40);
359 OSMetaClassDeclareReservedUnused(IOService, 41);
360 OSMetaClassDeclareReservedUnused(IOService, 42);
361 OSMetaClassDeclareReservedUnused(IOService, 43);
362 OSMetaClassDeclareReservedUnused(IOService, 44);
363 OSMetaClassDeclareReservedUnused(IOService, 45);
364 OSMetaClassDeclareReservedUnused(IOService, 46);
365 OSMetaClassDeclareReservedUnused(IOService, 47);
366 OSMetaClassDeclareReservedUnused(IOService, 48);
367 OSMetaClassDeclareReservedUnused(IOService, 49);
368 OSMetaClassDeclareReservedUnused(IOService, 50);
369 OSMetaClassDeclareReservedUnused(IOService, 51);
370 OSMetaClassDeclareReservedUnused(IOService, 52);
371 OSMetaClassDeclareReservedUnused(IOService, 53);
372 OSMetaClassDeclareReservedUnused(IOService, 54);
373 OSMetaClassDeclareReservedUnused(IOService, 55);
374 OSMetaClassDeclareReservedUnused(IOService, 56);
375 OSMetaClassDeclareReservedUnused(IOService, 57);
376 OSMetaClassDeclareReservedUnused(IOService, 58);
377 OSMetaClassDeclareReservedUnused(IOService, 59);
378 OSMetaClassDeclareReservedUnused(IOService, 60);
379 OSMetaClassDeclareReservedUnused(IOService, 61);
380 OSMetaClassDeclareReservedUnused(IOService, 62);
381 OSMetaClassDeclareReservedUnused(IOService, 63);
382
383public:
384/*! @function getState
385 @abstract Accessor for IOService state bits, not normally needed or used outside IOService.
386 @result State bits for the IOService, eg. kIOServiceInactiveState, kIOServiceRegisteredState. */
387
388 virtual IOOptionBits getState( void ) const;
389
390/*! @function isInactive
391 @abstract Check the IOService has been terminated, and is in the process of being destroyed.
392 @discussion When an IOService is successfully terminated, it is immediately made inactive, which blocks further attach()es, matching or notifications occuring on the object. It remains inactive until the last client closes, and is then finalized and destroyed.
393 @result Returns true if the IOService has been terminated. */
394
395 inline bool isInactive( void ) const
396 { return( 0 != (kIOServiceInactiveState & getState())); }
397
398 /* Stack creation */
399
400/*! @function registerService
401 @abstract Start the registration process for a newly discovered IOService.
402 @discussion This function allows an IOService subclass to be published and made available to possible clients, by starting the registration process and delivering notifications to registered clients. The object should be completely setup and ready to field requests from clients before registerService is called.
403 @param options The default zero options mask is recommended & should be used in most cases. The registration process is usually asynchronous, with possible driver probing & notification occurring some time later. kIOServiceSynchronous may be passed to carry out the matching and notification process for currently registered clients before returning to the caller. */
404
405 virtual void registerService( IOOptionBits options = 0 );
406
407/*! @function probe
408 @abstract During an IOService instantiation probe a matched service to see if it can be used.
409 @discussion The registration process for an IOService (the provider) includes instantiating possible driver clients. The probe method is called in the client instance to check the matched service can be used before the driver is considered to be started. Since matching screens many possible providers, in many cases the probe method can be left unimplemented by IOService subclasses. The client is already attached to the provider when probe is called.
410 @param provider The registered IOService which matches a driver personality's matching dictionary.
411 @param score Pointer to the current driver's probe score, which is used to order multiple matching drivers in the same match category. It defaults to the value of the IOProbeScore property in the drivers property table, or kIODefaultProbeScore if none is specified. The probe method may alter the score to affect start order.
412 @result Returns an IOService instance or zero when the probe is unsuccessful. In almost all cases the value of this is returned on success. If another IOService object is returned, the probed instance is detached and freed, and the returned instance is used in its stead for start. */
413
414 virtual IOService * probe( IOService * provider,
415 SInt32 * score );
416
417/*! @function start
418 @abstract During an IOService instantiation, the start method is called when the IOService has been selected to run on the provider.
419 @discussion The registration process for an IOService (the provider) includes instantiating possible driver clients. The start method is called in the client instance when it has been selected (by its probe score and match category) to be the winning client. The client is already attached to the provider when start is called.
420 @result Return true if the start was successful, false otherwise (which will cause the instance to be detached and usually freed). */
421
422 virtual bool start( IOService * provider );
423
424/*! @function stop
425 @abstract During an IOService termination, the stop method is called in its clients before they are detached & it is destroyed.
426 @discussion The termination process for an IOService (the provider) will call stop in each of its clients, after they have closed the provider if they had it open, or immediately on termination. */
427
428 virtual void stop( IOService * provider );
429
430 /* Open / Close */
431
432/*! @function open
433 @abstract Request active access to a provider.
434 @discussion IOService provides generic open and close semantics to track clients of a provider that have established an active datapath. The use of open & close, and rules regarding ownership are family defined, and defined by the handleOpen / handleClose methods in the provider. Some families will limit access to a provider based on its open state.
435 @param forClient Designates the client of the provider requesting the open.
436 @param options Options for the open. The provider family may implement options for open; IOService defines only kIOServiceSeize to request the device be withdrawn from its current owner.
437 @result Return true if the open was successful, false otherwise. */
438
439 virtual bool open( IOService * forClient,
440 IOOptionBits options = 0,
441 void * arg = 0 );
442
443/*! @function close
444 @abstract Release active access to a provider.
445 @discussion IOService provides generic open and close semantics to track clients of a provider that have established an active datapath. The use of open & close, and rules regarding ownership are family defined, and defined by the handleOpen / handleClose methods in the provider.
446 @param forClient Designates the client of the provider requesting the close.
447 @param options Options available for the close. The provider family may implement options for close; IOService defines none.
448 @param arg Family specific arguments, ignored by IOService. */
449
450 virtual void close( IOService * forClient,
451 IOOptionBits options = 0 );
452
453/*! @function isOpen
454 @abstract Determine whether a specific, or any, client has an IOService open.
455 @discussion Returns the open state of an IOService with respect to the specified client, or when it is open by any client.
456 @param forClient If non-zero, isOpen returns the open state for that client. If zero is passed, isOpen returns the open state for all clients.
457 @result Returns true if the specific, or any, client has the IOService open. */
458
459 virtual bool isOpen( const IOService * forClient = 0 ) const;
460
461/*! @function handleOpen
462 @abstract Overrideable method to control the open / close behaviour of an IOService.
463 @discussion IOService calls this method in its subclasses in response to the open method, so the subclass may implement the request. The default implementation provides single owner access to an IOService via open. The object is locked via lockForArbitration before handleOpen is called.
464 @param forClient Designates the client of the provider requesting the open.
465 @param options Options for the open, may be interpreted by the implementor of handleOpen.
466 @result Return true if the open was successful, false otherwise. */
467
468 virtual bool handleOpen( IOService * forClient,
469 IOOptionBits options,
470 void * arg );
471
472/*! @function handleClose
473 @abstract Overrideable method to control the open / close behaviour of an IOService.
474 @discussion IOService calls this method in its subclasses in response to the close method, so the subclass may implement the request. The default implementation provides single owner access to an IOService via open. The object is locked via lockForArbitration before handleClose is called.
475 @param forClient Designates the client of the provider requesting the close.
476 @param options Options for the close, may be interpreted by the implementor of handleOpen. */
477
478 virtual void handleClose( IOService * forClient,
479 IOOptionBits options );
480
481/*! @function handleIsOpen
482 @abstract Overrideable method to control the open / close behaviour of an IOService.
483 @discussion IOService calls this method in its subclasses in response to the open method, so the subclass may implement the request. The default implementation provides single owner access to an IOService via open. The object is locked via lockForArbitration before handleIsOpen is called.
484 @param forClient If non-zero, isOpen returns the open state for that client. If zero is passed, isOpen returns the open state for all clients.
485 @result Returns true if the specific, or any, client has the IOService open. */
486
487 virtual bool handleIsOpen( const IOService * forClient ) const;
488
489 /* Stacking change */
490
491/*! @function terminate
492 @abstract Make an IOService inactive and begin its destruction.
493 @discussion Registering an IOService informs possible clients of its existance and instantiates drivers that may be used with it; terminate involves the opposite process of informing clients that an IOService is no longer able to be used and will be destroyed. By default, if any client has the service open, terminate fails. If the kIOServiceRequired flag is passed however, terminate will be sucessful though further progress in the destruction of the IOService 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 message method with a message of type kIOMessageServiceIsTerminated. Both these actions take place on the callers thread. After the IOService is made inactive, further matching or attach calls will fail on it. Each client has its stop method called upon their close of an inactive IOService, or on its termination if they do not have it open. After stop, detach is called in each client. When all clients have been detached, the finalize method is called in the inactive service. The terminate process is inherently asynchronous since it will be deferred until all clients have chosen to close.
494 @param options In most cases no options are needed. kIOServiceSynchronous may be passed to cause terminate to not return until the service is finalized. */
495
496 virtual bool terminate( IOOptionBits options = 0 );
497
498/*! @function finalize
499 @abstract The last stage in an IOService destruction.
500 @discussion The finalize method is called in an inactive (ie. terminated) IOService after the last client has detached. IOService's implementation will call stop, close, and detach on each provider. When finalize returns, the object's retain count will have no references generated by IOService's registration process.
501 @param options The options passed to the terminate method of the IOService are passed on to finalize.
502 @result Returns true. */
503
504 virtual bool finalize( IOOptionBits options );
505
0b4e3aa0
A
506/*! @function free
507 @discussion Free data structures that were allocated when power management was initialized on this service. */
508
509 virtual void free( void );
510
1c79356b
A
511/*! @function lockForArbitration
512 @abstract Locks an IOService against changes in state or ownership.
513 @discussion The registration, termination and open / close functions of IOService use lockForArbtration to single thread access to an IOService. lockForArbitration will grant recursive access to the same thread.
514 @param isSuccessRequired If a request for access to an IOService should be denied if it is terminated, isSuccessRequired should passed as false, otherwise pass true. */
515
516 virtual bool lockForArbitration( bool isSuccessRequired = true );
517
518/*! @function unlockForArbitration
519 @abstract Unlocks an IOService after a successful lockForArbitration.
520 @discussion A thread granted exclusive access to an IOService should release it with unlockForArbitration. */
521
522 virtual void unlockForArbitration( void );
523
524/*! @function terminateClient
525 @abstract Passes a termination up the stack.
526 @discussion When an IOService is made inactive the default behaviour is to also make any of its clients that have it as their only provider also inactive, in this way recursing the termination up the driver stack. This method allows a terminated IOService to override this behaviour. Note the client may also override this behaviour by overriding its terminate method.
527 @param client The client of the of the terminated provider.
528 @param options Options originally passed to terminate, plus kIOServiceRecursing.
529 @result result of the terminate request on the client. */
530
531 virtual bool terminateClient( IOService * client, IOOptionBits options );
532
533 /* Busy state indicates discovery, matching or termination is in progress */
534
535/*! @function getBusyState
536 @abstract Returns the busyState of an IOService.
537 @discussion Many activities in IOService are asynchronous. When registration, matching, or termination is in progress on an IOService, its busyState is increased by one. Change in busyState to or from zero also changes the IOService's provider's busyState by one, which means that an IOService is marked busy when any of the above activities is ocurring on it or any of its clients.
538 @result The busyState. */
539
540 virtual UInt32 getBusyState( void );
541
542/*! @function adjustBusy
543 @abstract Adjusts the busyState of an IOService.
0b4e3aa0 544 @discussion Applies a delta to an IOService's busyState. A change in the busyState to or from zero will change the IOService's provider's busyState by one (in the same direction).
1c79356b
A
545 @param delta The delta to be applied to the IOService busy state. */
546
547 virtual void adjustBusy( SInt32 delta );
548
549/*! @function waitQuiet
550 @abstract Wait for an IOService's busyState to be zero.
551 @discussion Blocks the caller until an IOService is non busy.
552 @param timeout Specifies a maximum time to wait.
553 @result Returns an error code if mach synchronization primitives fail, kIOReturnTimeout, or kIOReturnSuccess. */
554
555 virtual IOReturn waitQuiet( mach_timespec_t * timeout = 0 );
556
557 /* Matching */
558
559/*! @function matchPropertyTable
560 @abstract Allows a registered IOService to implement family specific matching.
561 @discussion All matching on an IOService will call this method to allow a family writer to implement matching in addition to the generic methods provided by IOService. The implementer should examine the matching dictionary passed to see if it contains properties the family understands for matching, and use them to match with the IOService if so. Note that since matching is also carried out by other parts of IOKit, the matching dictionary may contain properties the family does not understand - these should not be considered matching failures.
562 @param table The dictionary of properties to be matched against.
563 @param score Pointer to the current driver's probe score, which is used to order multiple matching drivers in the same match category. It defaults to the value of the IOProbeScore property in the drivers property table, or kIODefaultProbeScore if none is specified.
564 @result Returns false if the family considers the matching dictionary does not match in properties it understands, true otherwise. */
565
566 virtual bool matchPropertyTable( OSDictionary * table,
567 SInt32 * score );
568
569 virtual bool matchPropertyTable( OSDictionary * table );
570
571/*! @function matchLocation
572 @abstract Allows a registered IOService to direct location matching.
573 @discussion By default, a location matching property will be applied to an IOService's provider. This method allows that behaviour to be overridden by families.
574 @param client The IOService at which matching is taking place.
575 @result Returns the IOService instance to be used for location matching. */
576
577 virtual IOService * matchLocation( IOService * client );
578
579 /* Resource service */
580
581/*! @function publishResource
582 @abstract Use the resource service to publish a property.
583 @discussion The resource service uses IOService's matching and notification to allow objects to be published and found by any IOKit client by a global name. publishResource makes an object available to anyone waiting for it or looking for it in the future.
584 @param key An OSSymbol key that globally identifies the object.
585 @param The object to be published. */
586
587 static void publishResource( const OSSymbol * key, OSObject * value = 0 );
588
589/*! @function publishResource
590 @abstract Use the resource service to publish a property.
591 @discussion The resource service uses IOService's matching and notification to allow objects to be published and found by any IOKit client by a global name. publishResource makes an object available to anyone waiting for it or looking for it in the future.
592 @param key A C-string key that globally identifies the object.
593 @param The object to be published. */
594
595 static void publishResource( const char * key, OSObject * value = 0 );
596 virtual bool addNeededResource( const char * key );
597
598 /* Notifications */
599
600/*! @function addNotification
601 @abstract Add a persistant notification handler to be notified of IOService events.
602 @discussion IOService will deliver notifications of changes in state of an IOService to registered clients. The type of notification is specified by a symbol, for example gIOMatchedNotification or gIOTerminatedNotification, and notifications will only include IOService's that match the supplied matching dictionary. Notifications are ordered by a priority set with addNotification. When the notification is installed, its handler will be called with each of any currently existing IOService's 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. addNotification will consume a retain count on the matching dictionary when the notification is removed.
603 @param type An OSSymbol identifying the type of notification and IOService state:
604<br> gIOPublishNotification Delivered when an IOService is registered.
605<br> gIOFirstPublishNotification Delivered when an IOService is registered, but only once per IOService instance. Some IOService's may be reregistered when their state is changed.
606<br> gIOMatchedNotification Delivered when an IOService has been matched with all client drivers, and they have been probed and started.
607<br> gIOFirstMatchNotification Delivered when an IOService has been matched with all client drivers, but only once per IOService instance. Some IOService's may be reregistered when their state is changed.
608<br> gIOTerminatedNotification Delivered after an IOService has been terminated, during its finalize stage.
609 @param matching A matching dictionary to restrict notifications to only matching IOServices. The dictionary will be released when the notification is removed - consuming the passed in reference.
610 @param handler A C-function callback to deliver notifications.
611 @param target An instance reference for the callbacks use.
612 @param ref A reference constant for the callbacks use
613 @param priority A constant ordering all notifications of a each type.
614 @result Returns an instance of an IONotifier object that can be used to control or destroy the notification request. */
615
616 static IONotifier * addNotification(
617 const OSSymbol * type, OSDictionary * matching,
618 IOServiceNotificationHandler handler,
619 void * target, void * ref = 0,
620 SInt32 priority = 0 );
621
622/*! @function waitForService
623 @abstract Wait for a matching to service to be published.
624 @discussion Provides a method of waiting for an IOService matching the supplied matching dictionary to be registered and fully matched.
625 @param matching The matching dictionary describing the desired IOService. waitForService will consume one reference of the matching dictionary.
626 @param timeout The maximum time to wait.
627 @result A published IOService matching the supplied dictionary. */
628
629 static IOService * waitForService( OSDictionary * matching,
630 mach_timespec_t * timeout = 0);
631
632/*! @function getMatchingServices
633 @abstract Finds the set of current published IOServices matching a matching dictionary.
634 @discussion Provides a method of finding the current set of published IOServices matching the supplied matching dictionary.
635 @param matching The matching dictionary describing the desired IOServices.
636 @result An instance of an iterator over a set of IOServices. To be released by the caller. */
637
638 static OSIterator * getMatchingServices( OSDictionary * matching );
639
640/*! @function installNotification
641 @abstract Add a persistant notification handler to be notified of IOService events.
642 @discussion A lower level interface to addNotification that will install a handler and return the current set of IOServices that are in the specified state and match the matching dictionary.
643 @param type See addNotification.
644 @param matching See addNotification.
645 @param handler See addNotification.
646 @param self See addNotification.
647 @param ref See addNotification.
648 @param priority See addNotification.
649 @param existing Returns an iterator over the set of IOServices that are currently in the specified state and match the matching dictionary.
650 @result See addNotification. */
651
652 static IONotifier * installNotification(
653 const OSSymbol * type, OSDictionary * matching,
654 IOServiceNotificationHandler handler,
655 void * target, void * ref,
656 SInt32 priority, OSIterator ** existing );
657
658 /* Helpers to make matching dictionaries for simple cases,
659 * they add keys to an existing dictionary, or create one. */
660
661/*! @function serviceMatching
662 @abstract Create a matching dictionary, or add matching properties to an existing dictionary, that specify an IOService class match.
663 @discussion A very common matching criteria for IOService is based on its class. serviceMatching will create a matching dictionary that specifies any IOService of a class, or its subclasses. The class is specified by name, and an existing dictionary may be passed in, in which case the matching properties will be added to that dictionary rather than creating a new one.
664 @param className The class name, as a const C-string. Class matching is successful on IOService's of this class or any subclass.
665 @param table If zero, serviceMatching will create a matching dictionary and return a reference to it, otherwise the matching properties are added to the specified dictionary.
666 @result The matching dictionary created, or passed in, is returned on success, or zero on failure. */
667
668 static OSDictionary * serviceMatching( const char * className,
669 OSDictionary * table = 0 );
670
671/*! @function serviceMatching
672 @abstract Create a matching dictionary, or add matching properties to an existing dictionary, that specify an IOService class match.
673 @discussion A very common matching criteria for IOService is based on its class. serviceMatching will create a matching dictionary that specifies any IOService of a class, or its subclasses. The class is specified by name, and an existing dictionary may be passed in, in which case the matching properties will be added to that dictionary rather than creating a new one.
674 @param className The class name, as an OSString (which includes OSSymbol). Class matching is successful on IOService's of this class or any subclass.
675 @param table If zero, serviceMatching will create a matching dictionary and return a reference to it, otherwise the matching properties are added to the specified dictionary.
676 @result The matching dictionary created, or passed in, is returned on success, or zero on failure. */
677
678 static OSDictionary * serviceMatching( const OSString * className,
679 OSDictionary * table = 0 );
680
681/*! @function nameMatching
682 @abstract Create a matching dictionary, or add matching properties to an existing dictionary, that specify an IOService name match.
683 @discussion A very common matching criteria for IOService is based on its name. nameMatching will create a matching dictionary that specifies any IOService which respond sucessfully to the IORegistryEntry method compareName. An existing dictionary may be passed in, in which case the matching properties will be added to that dictionary rather than creating a new one.
684 @param name The service's name, as a const C-string. Name matching is successful on IOService's which respond sucessfully to the IORegistryEntry method compareName.
685 @param table If zero, nameMatching will create a matching dictionary and return a reference to it, otherwise the matching properties are added to the specified dictionary.
686 @result The matching dictionary created, or passed in, is returned on success, or zero on failure. */
687
688 static OSDictionary * nameMatching( const char * name,
689 OSDictionary * table = 0 );
690
691/*! @function nameMatching
692 @abstract Create a matching dictionary, or add matching properties to an existing dictionary, that specify an IOService name match.
693 @discussion A very common matching criteria for IOService is based on its name. nameMatching will create a matching dictionary that specifies any IOService which respond sucessfully to the IORegistryEntry method compareName. An existing dictionary may be passed in, in which case the matching properties will be added to that dictionary rather than creating a new one.
694 @param name The service's name, as an OSString (which includes OSSymbol). Name matching is successful on IOService's which respond sucessfully to the IORegistryEntry method compareName.
695 @param table If zero, nameMatching will create a matching dictionary and return a reference to it, otherwise the matching properties are added to the specified dictionary.
696 @result The matching dictionary created, or passed in, is returned on success, or zero on failure. */
697
698 static OSDictionary * nameMatching( const OSString* name,
699 OSDictionary * table = 0 );
700
701/*! @function resourceMatching
702 @abstract Create a matching dictionary, or add matching properties to an existing dictionary, that specify a resource service match.
703 @discussion IOService maintains a resource service IOResources that allows objects to be published and found globally in IOKit based on a name, using the standard IOService matching and notification calls.
704 @param name The resource name, as a const C-string. Resource matching is successful when an object by that name has been published with the publishResource method.
705 @param table If zero, resourceMatching will create a matching dictionary and return a reference to it, otherwise the matching properties are added to the specified dictionary.
706 @result The matching dictionary created, or passed in, is returned on success, or zero on failure. */
707
708 static OSDictionary * resourceMatching( const char * name,
709 OSDictionary * table = 0 );
710
711/*! @function resourceMatching
712 @abstract Create a matching dictionary, or add matching properties to an existing dictionary, that specify a resource service match.
713 @discussion IOService maintains a resource service IOResources that allows objects to be published and found globally in IOKit based on a name, using the standard IOService matching and notification calls.
714 @param name The resource name, as an OSString (which includes OSSymbol). Resource matching is successful when an object by that name has been published with the publishResource method.
715 @param table If zero, resourceMatching will create a matching dictionary and return a reference to it, otherwise the matching properties are added to the specified dictionary.
716 @result The matching dictionary created, or passed in, is returned on success, or zero on failure. */
717
718 static OSDictionary * resourceMatching( const OSString * name,
719 OSDictionary * table = 0 );
720
721/*! @function addLocation
722 @abstract Add a location matching property to an existing dictionary.
723 @discussion This function creates matching properties that specify the location of a IOService, as an embedded matching dictionary. This matching will be successful on an IOService which attached to an IOService which matches this location matching dictionary.
724 @param table The matching properties are added to the specified dictionary, which must be non-zero.
725 @result The location matching dictionary created is returned on success, or zero on failure. */
726
727 static OSDictionary * addLocation( OSDictionary * table );
728
729 /* Helpers for matching dictionaries. */
730
731/*! @function compareProperty
732 @abstract Utility to compare a property in a matching dictionary with an IOService's property table.
733 @discussion This is a helper function to aid in implementing matchPropertyTable. If the property specified by key exists in the matching dictionary, it is compared with a property of the same name in the IOService's property table. The comparison is performed with the isEqualTo method. If the property does not exist in the matching table, success is returned. If the property exists in the matching dictionary but not the IOService property table, failure is returned.
734 @param matching The matching dictionary, which must be non-zero.
735 @param key The dictionary key specifying the property to be compared, as a C-string.
736 @result If the property does not exist in the matching table, true is returned. If the property exists in the matching dictionary but not the IOService property table, failure is returned. Otherwise the result of calling the property from the matching dictionary's isEqualTo method with the IOService property as an argument is returned. */
737
738 virtual bool compareProperty( OSDictionary * matching,
739 const char * key );
740/*! @function compareProperty
741 @abstract Utility to compare a property in a matching dictionary with an IOService's property table.
742 @discussion This is a helper function to aid in implementing matchPropertyTable. If the property specified by key exists in the matching dictionary, it is compared with a property of the same name in the IOService's property table. The comparison is performed with the isEqualTo method. If the property does not exist in the matching table, success is returned. If the property exists in the matching dictionary but not the IOService property table, failure is returned.
743 @param matching The matching dictionary, which must be non-zero.
744 @param key The dictionary key specifying the property to be compared, as an OSString (which includes OSSymbol).
745 @result If the property does not exist in the matching table, true is returned. If the property exists in the matching dictionary but not the IOService property table, failure is returned. Otherwise the result of calling the property from the matching dictionary's isEqualTo method with the IOService property as an argument is returned. */
746
747 virtual bool compareProperty( OSDictionary * matching,
748 const OSString * key );
749
750/*! @function compareProperties
751 @abstract Utility to compare a set of properties in a matching dictionary with an IOService's property table.
752 @discussion This is a helper function to aid in implementing matchPropertyTable. A collection of dictionary keys specifies properties in a matching dictionary to be compared, with compareProperty, with an IOService property table, if compareProperty returns true for each key, success is return else failure.
753 @param matching The matching dictionary, which must be non-zero.
754 @param keys A collection (eg. OSSet, OSArray, OSDictionary) which should contain OSStrings (or OSSymbols) that specify the property keys to be compared.
755 @result if compareProperty returns true for each key in the collection, success is return else failure. */
756
757 virtual bool compareProperties( OSDictionary * matching,
758 OSCollection * keys );
759
760 /* Client / provider accessors */
761
762/*! @function attach
763 @abstract Attaches an IOService client to a provider in the registry.
764 @discussion This function called in an IOService client enters the client into the registry as a child of the provider in the service plane. The provider must be active or the attach will fail. Multiple attach calls to the same provider are no-ops and return success. A client may be attached to multiple providers. Entering an object into the registry will retain both the client and provider until they are detached.
765 @param provider The IOService object which will serve as this objects provider.
766 @result false if the provider is inactive or on a resource failure, otherwise true. */
767
768 virtual bool attach( IOService * provider );
769
770/*! @function detach
771 @abstract Detaches an IOService client from a provider in the registry.
772 @discussion This function called in an IOService client removes the client as a child of the provider in the service plane of the registry. If the provider is not a parent of the client this is a no-op, otherwise the registry will release both the client and provider.
773 @param provider The IOService object to detach from. */
774
775 virtual void detach( IOService * provider );
776
777/*! @function getProvider
778 @abstract Returns an IOService's primary provider.
779 @discussion This function called in an IOService client will return the provider to which it was first attached. Since the majority of IOService objects have only one provider, this is a useful simplification and also supports caching of the provider when the registry is unchanged.
780 @result Returns the first provider of the client, or zero if the IOService is not attached into the registry. The provider is retained while the client is attached, and should not be released by the caller. */
781
782 virtual IOService * getProvider( void ) const;
783
784/*! @function getWorkLoop
785 @abstract Returns the current work loop or provider->getWorkLoop().
786 @discussion This function returns a valid work loop that a client can use to add an IOCommandGate to. The intention is that an IOService client has data that needs to be protected but doesn't want to pay the cost of an entire dedicated thread. This data has to be accessed from a providers call out context as well. So to achieve both of these goals the client creates an IOCommandGate to lock access to his data but he registers it with the providers work loop, i.e. the work loop which will make the completion call outs. In one fell swoop we avoid a potentially nasty deadlock 'cause a work loop's gate is recursive.
787 @result Always returns a work loop, either the current work loop or it walks up the $link getProvider() chain calling getWorkLoop. Eventually it will reach a valid work loop based driver or the root of the io tree where it will return a system wide work loop. Returns 0 if it fails to find (or create) */
788
789 virtual IOWorkLoop * getWorkLoop() const;
790
791/*! @function getProviderIterator
792 @abstract Returns an iterator over an IOService's providers.
793 @discussion For those few IOService objects that obtain service from multiple providers, this method supplies an iterator over a client's providers.
794 @result Returns an iterator over the providers of the client, or zero if there is a resource failure. The iterator must be released when the iteration is finished. All objects returned by the iteration are retained while the iterator is valid, though they may no longer be attached during the iteration. */
795
796 virtual OSIterator * getProviderIterator( void ) const;
797
798/*! @function getOpenProviderIterator
799 @abstract Returns an iterator over an client's providers that are currently opened by the client.
800 @discussion For those few IOService objects that obtain service from multiple providers, this method supplies an iterator over a client's providers, locking each in turn with lockForArbitration and returning those that have been opened by the client.
801 @result Returns an iterator over the providers the client has open, or zero if there is a resource failure. The iterator must be released when the iteration is finished. All objects returned by the iteration are retained while the iterator is valid, and the current entry in the iteration is locked with lockForArbitration, protecting it from state changes. */
802
803 virtual OSIterator * getOpenProviderIterator( void ) const;
804
805/*! @function getClient
806 @abstract Returns an IOService's primary client.
807 @discussion This function called in an IOService provider will return the first client to attach to it. For IOService objects which have only only one client, this may be a useful simplification.
808 @result Returns the first client of the provider, or zero if the IOService is not attached into the registry. The client is retained while it is attached, and should not be released by the caller. */
809
810 virtual IOService * getClient( void ) const;
811
812/*! @function getClientIterator
813 @abstract Returns an iterator over an IOService's clients.
814 @discussion For IOService objects that may have multiple clients, this method supplies an iterator over a provider's clients.
815 @result Returns an iterator over the clients of the provider, or zero if there is a resource failure. The iterator must be released when the iteration is finished. All objects returned by the iteration are retained while the iterator is valid, though they may no longer be attached during the iteration. */
816
817 virtual OSIterator * getClientIterator( void ) const;
818
819/*! @function getOpenClientIterator
820 @abstract Returns an iterator over an provider's clients that currently have opened the provider.
821 @discussion For IOService objects that may have multiple clients, this method supplies an iterator over a provider's clients, locking each in turn with lockForArbitration and returning those that have opened the provider.
822 @result Returns an iterator over the clients which the provider open, or zero if there is a resource failure. The iterator must be released when the iteration is finished. All objects returned by the iteration are retained while the iterator is valid, and the current entry in the iteration is locked with lockForArbitration, protecting it from state changes. */
823
824 virtual OSIterator * getOpenClientIterator( void ) const;
825
826/*! @function callPlatformFunction
827 @abstract Calls the platform function with the given name.
828 @discussion The platform expert or other drivers may implement various functions to control hardware features. callPlatformFunction allows any IOService object to access these functions. Normally callPlatformFunction will be called on a service's provider. The provider will service the request or pass it to it's provider. The systems IOPlatformExpert subclass will catch functions it knows about and redirect them into other parts of the IOService plane. If the IOPlatformExpert subclass can not execute the function, the base class will be called. The IOPlatformExpert base class will attempt to find a service to execute the function by looking up the function name in a IOResources name space. A service may publish a service using publishResource(functionName, this). If no service can be found to execute the function an error will be returned.
829 @param functionName name of the function to be called. When functionName is a c-string, callPlatformFunction will convert the c-string to a OSSymbol and call other OSSymbol version of callPlatformFunction. This process can block and should not be used from an interrupt context.
830 @param waitForFunction if true callPlatformFunction will not return until the function has been called.
831 @result Return an IOReturn code, kIOReturnSuccess if the function was successfully executed, kIOReturnUnsupported if a service to execute the function could not be found. Other return codes may be returned by the function.*/
832
833 virtual IOReturn callPlatformFunction( const OSSymbol * functionName,
834 bool waitForFunction,
835 void *param1, void *param2,
836 void *param3, void *param4 );
837
838 virtual IOReturn callPlatformFunction( const char * functionName,
839 bool waitForFunction,
840 void *param1, void *param2,
841 void *param3, void *param4 );
842
843
844 /* Some accessors */
845
846/*! @function getPlatform
847 @abstract Returns a pointer to the platform expert instance for the machine.
848 @discussion This method provides an accessor to the platform expert instance for the machine.
849 @result A pointer to the IOPlatformExport instance. It should not be released by the caller. */
850
851 static IOPlatformExpert * getPlatform( void );
852
0b4e3aa0
A
853/*! @function getPMRootDomain
854 @abstract Returns a pointer to the power management root domain instance for the machine.
855 @discussion This method provides an accessor to the power management root domain instance for the machine.
856 @result A pointer to the power management root domain instance. It should not be released by the caller. */
857
858 static class IOPMrootDomain * getPMRootDomain( void );
859
1c79356b
A
860/*! @function getServiceRoot
861 @abstract Returns a pointer to the root of the service plane.
862 @discussion This method provides an accessor to the root of the service plane for the machine.
863 @result A pointer to the IOService instance at the root of the service plane. It should not be released by the caller. */
864
865 static IOService * getServiceRoot( void );
866
0b4e3aa0
A
867/*! @function getResourceService
868 @abstract Returns a pointer to the IOResources service.
869 @discussion IOService maintains a resource service IOResources that allows objects to be published and found globally in IOKit based on a name, using the standard IOService matching and notification calls.
870 @result A pointer to the IOResources instance. It should not be released by the caller. */
871
872 static IOService * getResourceService( void );
873
1c79356b
A
874 /* Allocate resources for a matched service */
875
876/*! @function getResources
877 @abstract Allocate any needed resources for a published IOService before clients attach.
878 @discussion This method is called during the registration process for an IOService object if there are success driver matches, before any clients attach. It allows for lazy allocation of resources to an IOService when a matching driver is found.
879 @result Return an IOReturn code, kIOReturnSuccess is necessary for the IOService to be successfully used, otherwise the registration process for the object is halted. */
880
881 virtual IOReturn getResources( void );
882
883 /* Device memory accessors */
884
885/*! @function getDeviceMemoryCount
886 @abstract Returns a count of the physical memory ranges available for a device.
887 @discussion This method will return the count of physical memory ranges, each represented by an IODeviceMemory instance, that have been allocated for a memory mapped device.
888 @result An integer count of the number of ranges available. */
889
890 virtual IOItemCount getDeviceMemoryCount( void );
891
892/*! @function getDeviceMemoryWithIndex
893 @abstract Returns an instance of IODeviceMemory representing one of a device's memory mapped ranges.
894 @discussion This method will return a pointer to an instance of IODeviceMemory for the physical memory range at the given index for a memory mapped device.
895 @param index An index into the array of ranges assigned to the device.
896 @result A pointer to an instance of IODeviceMemory, or zero if the index is beyond the count available. The IODeviceMemory is retained by the provider, so is valid while attached, or while any mappings to it exist. It should not be released by the caller. See also mapDeviceMemory() which will create a device memory mapping. */
897
898 virtual IODeviceMemory * getDeviceMemoryWithIndex( unsigned int index );
899
900/*! @function mapDeviceMemoryWithIndex
901 @abstract Maps a physical range of a device.
902 @discussion This method will create a mapping for the IODeviceMemory at the given index, with IODeviceMemory::map(options). The mapping is represented by the returned instance of IOMemoryMap, which should not be released until the mapping is no longer required.
903 @param index An index into the array of ranges assigned to the device.
904 @result An instance of IOMemoryMap, or zero if the index is beyond the count available. The mapping should be released only when access to it is no longer required. */
905
906 virtual IOMemoryMap * mapDeviceMemoryWithIndex( unsigned int index,
907 IOOptionBits options = 0 );
908
909/*! @function getDeviceMemory
910 @abstract Returns the array of IODeviceMemory objects representing a device's memory mapped ranges.
911 @discussion This method will return an array of IODeviceMemory objects representing the physical memory ranges allocated to a memory mapped device.
912 @result An OSArray of IODeviceMemory objects, or zero if none are available. The array is retained by the provider, so is valid while attached. */
913
914 virtual OSArray * getDeviceMemory( void );
915
916/*! @function setDeviceMemory
917 @abstract Sets the array of IODeviceMemory objects representing a device's memory mapped ranges.
918 @discussion This method will set an array of IODeviceMemory objects representing the physical memory ranges allocated to a memory mapped device.
919 @param array An OSArray of IODeviceMemory objects, or zero if none are available. The array will be retained by the object. */
920
921 virtual void setDeviceMemory( OSArray * array );
922
923 /* Interrupt accessors */
924
925/*! @function registerInterrupt
926 @abstract Register a C-function interrupt handler for a device supplying interrupts.
927 @discussion This method will install a C-function interrupt handler to be called at primary interrupt time for a device's interrupt. Only one handler may be installed per interrupt source. IOInterruptEventSource provides an IOWorkLoop based abstraction for interrupt delivery that may be more appropriate for work loop based drivers.
928 @param source The index of the interrupt source in the device.
929 @param target An object instance to be passed to the interrupt handler.
930 @param handler The C-function to be to be called at primary interrupt time when the interrupt occurs. The handler should process the interrupt by clearing the interrupt, or by disabling the source.
931 @param refCon A reference constant for the handler's use.
932 @result An IOReturn code.<br>kIOReturnNoInterrupt is returned if the source is not valid.<br>kIOReturnNoResources is returned if the interrupt already has an installed handler. */
933
934 virtual IOReturn registerInterrupt(int source, OSObject *target,
935 IOInterruptAction handler,
936 void *refCon = 0);
937
938/*! @function unregisterInterrupt
939 @abstract Remove a C-function interrupt handler for a device supplying hardware interrupts.
940 @discussion This method will remove a C-function interrupt handler previously installed with registerInterrupt.
941 @param source The index of the interrupt source in the device.
942 @result An IOReturn code.<br>kIOReturnNoInterrupt is returned if the source is not valid. */
943
944 virtual IOReturn unregisterInterrupt(int source);
945
946/*! @function getInterruptType
947 @abstract Return the type of interrupt used for a device supplying hardware interrupts.
948 @discussion This method will return the type of interrupt used by the device.
949 @param source The index of the interrupt source in the device.
950 @param interruptType The interrupt type for the interrupt source will be stored here by getInterruptType.<br> kIOInterruptTypeEdge will be returned for edge trigggered sources.<br> kIOInterruptTypeLevel will be returned for level trigggered sources.
951 @result An IOReturn code.<br>kIOReturnNoInterrupt is returned if the source is not valid. */
952
953 virtual IOReturn getInterruptType(int source, int *interruptType);
954
955/*! @function enableInterrupt
956 @abstract Enable a device interrupt.
957 @discussion Enable a device interrupt. It is the callers responsiblity to keep track of the enable state of the interrupt source.
958 @param source The index of the interrupt source in the device.
959 @result An IOReturn code.<br>kIOReturnNoInterrupt is returned if the source is not valid. */
960
961 virtual IOReturn enableInterrupt(int source);
962
963/*! @function disableInterrupt
964 @abstract Disable a device interrupt.
965 @discussion Disable a device interrupt. It is the callers responsiblity to keep track of the enable state of the interrupt source.
966 @param source The index of the interrupt source in the device.
967 @result An IOReturn code.<br>kIOReturnNoInterrupt is returned if the source is not valid. */
968
969 virtual IOReturn disableInterrupt(int source);
970
971/*! @function causeInterrupt
972 @abstract Cause a device interrupt to occur.
973 @discussion Emulate a hardware interrupt, to be called from task level.
974 @param source The index of the interrupt source in the device.
975 @result An IOReturn code.<br>kIOReturnNoInterrupt is returned if the source is not valid. */
976
977 virtual IOReturn causeInterrupt(int source);
978
979/*! @function requestProbe
980 @abstract An external request that hardware be re-scanned for devices.
981 @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.
982 @param options Family defined options, not interpreted by IOService.
983 @result An IOReturn code. */
984
985 virtual IOReturn requestProbe( IOOptionBits options );
986
987 /* Generic API for non-data-path upstream calls */
988
989/*! @function message
990 @abstract Receive a generic message delivered from an attached provider.
991 @discussion A provider may deliver messages via the message method to its clients informing them of state changes, for example kIOMessageServiceIsTerminated or kIOMessageServiceIsSuspended. Certain messages are defined by IOKit in IOMessage.h while others may family dependent. This method is implemented in the client to receive messages.
992 @param type A type defined in IOMessage.h or defined by the provider family.
993 @param provider The provider from which the message originates.
994 @param argument An argument defined by the provider family, not used by IOService.
995 @result An IOReturn code defined by the message type. */
996
997 virtual IOReturn message( UInt32 type, IOService * provider,
998 void * argument = 0 );
999
1000/*! @function messageClient
1001 @abstract Send a generic message to an attached client.
1002 @discussion A provider may deliver messages via the message method to its clients informing them of state changes, for example kIOMessageServiceIsTerminated or kIOMessageServiceIsSuspended. Certain messages are defined by IOKit in IOMessage.h while others may family dependent. This method may be called in the provider to send a message to the specified client, which may be useful for overrides.
1003 @param type A type defined in IOMessage.h or defined by the provider family.
1004 @param client A client of the IOService to send the message.
1005 @param argument An argument defined by the provider family, not used by IOService.
1006 @result The return code from the client message call. */
1007
1008 virtual IOReturn messageClient( UInt32 messageType, OSObject * client,
1009 void * messageArgument = 0, vm_size_t argSize = 0 );
1010
1011/*! @function messageClients
1012 @abstract Send a generic message to all attached clients.
1013 @discussion A provider may deliver messages via the message method to its clients informing them of state changes, for example kIOMessageServiceIsTerminated or kIOMessageServiceIsSuspended. Certain messages are defined by IOKit in IOMessage.h while others may family dependent. This method may be called in the provider to send a message to all the attached clients, via the messageClient method.
1014 @param type A type defined in IOMessage.h or defined by the provider family.
1015 @param argument An argument defined by the provider family, not used by IOService.
1016 @result Any non-kIOReturnSuccess return codes returned by the clients, or kIOReturnSuccess if all return kIOReturnSuccess. */
1017
1018 virtual IOReturn messageClients( UInt32 type,
1019 void * argument = 0, vm_size_t argSize = 0 );
1020
1021 virtual IONotifier * registerInterest( const OSSymbol * typeOfInterest,
1022 IOServiceInterestHandler handler,
1023 void * target, void * ref = 0 );
1024
1025 virtual void applyToProviders( IOServiceApplierFunction applier,
1026 void * context );
1027
1028 virtual void applyToClients( IOServiceApplierFunction applier,
1029 void * context );
1030
1031 virtual void applyToInterested( const OSSymbol * typeOfInterest,
1032 OSObjectApplierFunction applier,
1033 void * context );
1034
1035 virtual IOReturn acknowledgeNotification( IONotificationRef notification,
1036 IOOptionBits response );
1037
1038 /* User client create */
1039
1040/*! @function newUserClient
1041 @abstract A request to create a connection for a non kernel client.
1042 @discussion A non kernel client may request a connection be opened via the IOServiceOpen() library function, which will call this method in an IOService. The rules & capabilities of user level clients are family dependent, and use the functions of the IOUserClient class for support. IOService's implementation returns kIOReturnUnsupported, so any family supporting user clients must implement this method.
1043 @param owningTask The mach task requesting the connection.
1044 @param securityID A token representing the access level for the task.
1045 @param type A constant specifying the type of connection to be created, specified by the caller of IOServiceOpen and interpreted only by the family.
1046 @param handler An instance of an IOUserClient object to represent the connection, which will be released when the connection is closed, or zero if the connection was not opened.
1047 @param properties A dictionary of additional properties for the connection.
1048 @result A return code to be passed back to the caller of IOServiceOpen. */
1049
1050 virtual IOReturn newUserClient( task_t owningTask, void * securityID,
1051 UInt32 type, OSDictionary * properties,
1052 IOUserClient ** handler );
1053
1054 virtual IOReturn newUserClient( task_t owningTask, void * securityID,
1055 UInt32 type, IOUserClient ** handler );
1056
1057 /* Return code utilities */
1058
1059/*! @function stringFromReturn
1060 @abstract A utility to supply a programmer friendly string from an IOReturn code.
1061 @discussion Strings are available for the standard return codes in IOReturn.h in IOService, while subclasses may implement this method to interpret family dependent return codes.
1062 @param rtn The IOReturn code.
1063 @result A pointer to a constant string, or zero if the return code is unknown. */
1064
1065 virtual const char * stringFromReturn( IOReturn rtn );
1066
1067/*! @function errnoFromReturn
1068 @abstract A utility to translate an IOReturn code to a BSD errno.
1069 @discussion BSD defines its own return codes for its functions in sys/errno.h, and IOKit families may need to supply compliant results in BSD shims. Results are available for the standard return codes in IOReturn.h in IOService, while subclasses may implement this method to interpret family dependent return codes.
1070 @param rtn The IOReturn code.
1071 @result The BSD errno or EIO if unknown. */
1072
1073 virtual int errnoFromReturn( IOReturn rtn );
1074
1075 /* * * * * * * * * * * * * * * * * * * * * * * * * * * * */
1076 /* * * * * * * * * * * * Internals * * * * * * * * * * * */
1077 /* * * * * * * * * * * * * * * * * * * * * * * * * * * * */
1078
1079public:
1080 int _numInterruptSources;
1081 IOInterruptSource *_interruptSources;
1082
1083 static void initialize( void );
1084
1085 virtual bool serializeProperties( OSSerialize * s ) const;
1086
1087 static void setPlatform( IOPlatformExpert * platform);
0b4e3aa0 1088 static void setPMRootDomain( class IOPMrootDomain * rootDomain );
1c79356b
A
1089
1090 static IOReturn catalogNewDrivers( OSOrderedSet * newTables );
0b4e3aa0 1091 static IOReturn waitMatchIdle( UInt32 ms );
1c79356b
A
1092
1093 static IOService * resources( void );
1094 virtual bool checkResources( void );
1095 virtual bool checkResource( OSObject * matching );
1096
1097 virtual void probeCandidates( OSOrderedSet * matches );
1098 virtual bool startCandidate( IOService * candidate );
1099 virtual IOService * getClientWithCategory( const OSSymbol * category );
1100
1101 virtual bool passiveMatch( OSDictionary * matching, bool changesOK = false);
1102
1103 virtual void startMatching( IOOptionBits options = 0 );
1104 virtual void doServiceMatch( IOOptionBits options );
1105 virtual void doServiceTerminate( IOOptionBits options );
1106
1107 static OSObject * getExistingServices( OSDictionary * matching,
1108 IOOptionBits inState, IOOptionBits options = 0 );
1109
1110 static IONotifier * setNotification(
1111 const OSSymbol * type, OSDictionary * matching,
1112 IOServiceNotificationHandler handler,
1113 void * target, void * ref,
1114 SInt32 priority = 0 );
1115
1116 static IONotifier * doInstallNotification(
1117 const OSSymbol * type, OSDictionary * matching,
1118 IOServiceNotificationHandler handler,
1119 void * target, void * ref,
1120 SInt32 priority, OSIterator ** existing );
1121
1122 static bool syncNotificationHandler( void * target, void * ref,
1123 IOService * newService );
1124
1125 virtual void deliverNotification( const OSSymbol * type,
1126 IOOptionBits orNewState, IOOptionBits andNewState );
1127
1128 bool invokeNotifer( class _IOServiceNotifier * notify );
1129
1130 virtual void unregisterAllInterest( void );
1131
1132 virtual IOReturn waitForState( UInt32 mask, UInt32 value,
1133 mach_timespec_t * timeout = 0 );
1134
0b4e3aa0
A
1135 UInt32 _adjustBusy( SInt32 delta );
1136
1137 bool terminatePhase1( IOOptionBits options = 0 );
1138 void scheduleTerminatePhase2( IOOptionBits options = 0 );
1139 void scheduleStop( IOService * provider );
1140 void scheduleFinalize( void );
1141 static void terminateThread( void * arg );
1142 static void terminateWorker( IOOptionBits options );
1143 static void actionWillTerminate( IOService * victim, IOOptionBits options,
1144 OSArray * doPhase2List );
1145 static void actionDidTerminate( IOService * victim, IOOptionBits options );
1146 static void actionFinalize( IOService * victim, IOOptionBits options );
1147 static void actionStop( IOService * client, IOService * provider );
1148
1149 void PMfree( void );
1150
1c79356b
A
1151 virtual IOReturn resolveInterrupt(IOService *nub, int source);
1152 virtual IOReturn lookupInterrupt(int source, bool resolve, IOInterruptController **interruptController);
1153
1154 /* power management */
1155
1156/*! @function PMinit
1157 A power managment policy-maker for a device calls itself here to initialize its power management.
1158 PMinit allocates and initializes the power management instance variables, and it should be called before any
1159 access to those variables or the power management methods. */
1160 virtual void PMinit (void );
1161
1162/*! @function PMstop
1163 A power managment policy-maker for a device calls itself here when it resigns its responsibilities as
1164 policy-maker. This typically happens when it is handing off the responsibility to another policy-maker,
1165 or when the device is removed from the system. The power managment variables don't exist after
1166 this call, and the power managment methods in the caller shouldn't be accessed. */
1167 virtual void PMstop ( void );
1168
1169/*! @function joinPMtree
1170 A policy-maker calls its nub here when initializing, to be attached into
1171 the power management hierarchy. The default function is to call the
1172 platform expert, which knows how to do it. This method is overridden
1173 by a nub subclass which may either know how to do it, or may need
1174 to take other action.
1175
1176 This may be the only "power management" method used in a nub, meaning
1177 it may be called even if the nub is not initialized for power management.
1178
1179 Before the nub returns from this method, the caller will probably be called
1180 at "setPowerParent" and "setAggressiveness" and possibly at "addPowerChild" as it is
1181 added to me hierarchy. */
1182 virtual void joinPMtree ( IOService * driver );
1183
1184/*! @function registerPowerDriver
1185 A driver calls a policy-maker here to volunteer to control power to the device.
1186 If the policy-maker accepts the volunteer, it adds the volunteer to its list of
1187 interested drivers, and it will call the volunteer at appropriate times to switch
1188 the power state of the device.
1189 @param controllingDriver
1190 This points to the calling driver.
1191 @param powerStates
1192 This is an array of power states which the driver can deal with. If this array
1193 is no less rich than one supplied by an earlier volunteer, then the policy-maker
1194 uses the calling driver as its power-controlling driver.
1195 @param numberOfStates
1196 The number of power states in the array. Power states are defined in
1197 pwr_mgt/IOPMpowerState.h.
1198 @result
1199 IOPMNoErr is returned. There are various error conditions possible which prevent
1200 the policy-maker from accepting the new power state array. These conditions
1201 are logged in the power managment event log, but not returned to the caller. */
1202 virtual IOReturn registerPowerDriver ( IOService* controllingDriver, IOPMPowerState* powerStates, unsigned long numberOfStates );
1203
1204/*! @function registerInterestedDriver
1205 Some IOService calls a policy-maker here to register interest in the changing
1206 power state of its device.
1207 @param theDriver
1208 The policy-maker adds this pointer to the calling IOService to its list of
1209 interested drivers. It informs drivers on this list pre- and post-power change.
1210 @result
1211 The policy-maker returns flags describing the capability of the device in its
1212 current power state. The policy-maker does not interpret these flags or
1213 understand them; they come from the power state array, and are understood
1214 only by interested drivers and perhaps the power-controlling driver. If the
1215 current power state is not yet defined, zero is returned. This is the case when
1216 the policy-maker is not yet in the power domain hierarchy or when it doesn't
1217 have a power-controlling driver yet. */
1218 virtual IOPMPowerFlags registerInterestedDriver ( IOService* theDriver );
1219
1220/*! @function deRegisterInterestedDriver
1221 An IOService which has previously registered with a policy-maker as an interested
1222 driver calls the policy-maker here to withdraw its interest. The policy-maker removes
1223 it from its list of interested drivers.
1224 @result
1225 These bits describe the capability of the device in its current power state. They are
1226 not understood by the policy-maker; they come from the capabilityFlags field of the
1227 current power state in the power state array. */
1228 virtual IOReturn deRegisterInterestedDriver ( IOService * theDriver );
1229
1230/*! @function acknowledgePowerChange
1231 When a device is changing power state, its policy-maker informs interested
1232 parties before and after the change. Interested parties are those which
1233 have registered as interested drivers and also children of the policy-maker
1234 in the case that it is a power domain.
1235 When an object is so informed, it can return an indication that it is prepared
1236 for the change, or it can return an indication that it needs some time to
1237 prepare. In this case it will call this method in the policy-maker when it has
1238 prepared.
1239 @param theDriver
1240 This points to the calling driver. The policy-maker uses it to know if all
1241 interested parties have acknowledged the power state change.
1242 @result
1243 IOPMNoErr is returned. */
1244 virtual IOReturn acknowledgePowerChange ( IOService * whichDriver );
1245
1246/*! @function acknowledgeSetPowerState
1247 When a policy-maker instructs its controlling driver to switch the state of
1248 the device, the driver can return an indication that the change is complete,
1249 or it can return an indication that it needs some time to make the change.
1250 In this case it will call this method in the policy-maker when it has made the
1251 power state change.
1252 @result
1253 IOPMNoErr is returned. */
1254 virtual IOReturn acknowledgeSetPowerState ( void );
1255
1256/*! @function powerDomainWillChangeTo
1257 When a power domain changes state, it notifies its children, which
1258 are policy-makers, by calling them at this method. It calls here
1259 before it makes the change, and a called policy-maker can return
1260 IOPMAckImplied to indicate that it is prepared for the change,
1261 or it can return a non-zero number to indicate that it is not prepared
1262 but will prepare and then call the parent at acknowledgePowerChange.
1263
1264 To prepare for a lowering of the power domain, the policy-maker
1265 informs all its interested parties of any resulting change in its device,
1266 and when they have all acknowledged, it calls its controlling driver
1267 to switch the device to an appropriate power state for the imminent
1268 domain state. If any interested driver or the controlling driver does
1269 not acknowledge immediately, then the policy-maker also will not.
1270
1271 To prepare for a raising of the power domain, the policy-maker
1272 informs all its interested parties of any resulting change in its device.
1273 If any do not acknowledge immediately, then the policy-maker also will not.
1274 @param newPowerStateFlags
1275 These flags describe the character of power in the imminent domain state.
1276 They are not understood by the policy-maker. It asks the controlling
1277 driver to translate them into a state number within the power state array.
1278 (The policy-maker for the domain also doesn't understand the bits; they
1279 come from a outputPowerCharacter field of the power state array for
1280 the power domain.)
1281 @param whichParent
1282 This pointer identifies the calling parent. */
1283 IOReturn powerDomainWillChangeTo ( IOPMPowerFlags newPowerStateFlags, IOPowerConnection * whichParent );
1284
1285/*! @function powerDomainDidChangeTo
1286 When a power domain changes state, it notifies its children, which
1287 are policy-makers, by calling them at this method. It calls here
1288 after the changed power of the power domain has settled at the
1289 new level. A called policy-maker can return
1290 IOPMAckImplied to indicate that it is prepared for the change,
1291 or it can return a non-zero number to indicate that it is not prepared
1292 but will prepare and then call the parent at acknowledgePowerChange.
1293
1294 To prepare for a lowered power domain, the policy-maker
1295 informs all its interested parties of the new power state of its device.
1296 If any do not acknowledge immediately, then the policy-maker also will not.
1297
1298 To prepare for a raised power domain, the policy-maker calls its controlling
1299 driver to switch the device to the appropriate power state for the new
1300 domain state. When that is accomplished, the policy-maker informs
1301 all its interested parties of the new power state. If any interested driver
1302 or the controlling driver does not acknowledge immediately, then the
1303 policy-maker also will not.
1304
1305 @param newPowerStateFlags
1306 These flags describe the character of power in the new domain state.
1307 They are not understood by the policy-maker. It asks the controlling
1308 driver to translate them into a state number within the power state array.
1309 (The policy-maker for the domain also doesn't understand the bits; they
1310 come from a outputPowerCharacter field of the power state array for
1311 the power domain.)
1312 @param whichParent
1313 This pointer identifies the calling parent. */
1314 IOReturn powerDomainDidChangeTo ( IOPMPowerFlags newPowerStateFlags, IOPowerConnection * whichParent );
1315
1316/*! @function requestPowerDomainState
1317 The child of a power domain calls it parent here to request power of a certain
1318 character. It does this after lowering power in its own device which allows
1319 it to tolerate lower power in the domain, and it does this if it needs more
1320 power for its device than is currently available in the domain.
1321 @param desiredState
1322 These flags describe the power required for some state of the caller's device.
1323 They are not understood by either the child or the parent. They come from
1324 the power state array of the child (in the inputPowerRequirement field), and
1325 the parent compares them to bits in the outputPowerCharacter fields of its
1326 power state array.
1327 @param whichChild
1328 This points to the caller, so the power domain can know which child is requesting.
1329 @param specificationFlags
1330 This value modifies the parent's choice of power state.
1331 If the parameter is IOPMNextHigherState, the parent will choose the lowest state
1332 which matches desiredState and which is higher than the current state.
1333 If the parameter is IOPMHighestState , the parent will choose the highest state
1334 which matches desiredState.
1335 If the parameter is IOPMNextLowerState, the parent will choose the highest state
1336 which matches desiredState and which is lower than the current state.
1337 If the parameter is IOPMLowestState, the parent will choose the lowest state
1338 which matches desiredState.
1339 A state matches desiredState if all the bits set in desiredState are also set in the
1340 outputPowerCharacter field of that state in the parent's power state array.
1341 @result
1342 The power domain parent returns IOPMBadSpecification if specificationFlags
1343 not wellformed. It returns IOPMNoSuchState if no state in its array satisfies
1344 the callers specification. It returns IOPMNotYetInitialized if it has not power
1345 state array yet to compare with. Otherwise it returns IOPMNoErr. In the last
1346 case it will initiate its change to the new state if it has a parent in the hierarchy
1347 (or is the root power domain.) */
1348 virtual IOReturn requestPowerDomainState ( IOPMPowerFlags desiredState, IOPowerConnection * whichChild, unsigned long specificationFlags );
1349
1350/*! @function makeUsable
1351 Some client of a device is asking that it become usable. Although
1352 this has not come from the policy-maker for the device, treat it exactly
1353 as if it had. In this way, subsequent requests for lower power from
1354 the policy-maker will pre-empt this request.
1355 We treat this as policy-maker request to switch to the highest power state.
1356 @result
1357 The return code reflects the state of the policy-maker's internal queue of power
1358 changes and can be ignored by the caller. */
1359 virtual IOReturn makeUsable ( void );
1360
1361 /*! @function temporaryPowerClampOn
1362 A power domain calls this method to hold itself in the highest power state until it
1363 has children, and at that point the domain state is controlled by the childrens'
1364 requirements.
1365 @result
1366 The return code reflects the state of the policy-maker's internal queue of power
1367 changes and can be ignored by the caller. */
1368 virtual IOReturn temporaryPowerClampOn ( void );
1369
1370/*! @function changePowerStateTo
1371 The power-controlling driver calls the policy-maker here when it wants the device
1372 switched to a different power state. This is mildly ironic in that it is the controlling
1373 driver which does the switching, but it must do it this way so that the policy-maker
1374 can make sure the power domain is correct and to notify interested parties
1375 pre-change. When appropriate, the policy-maker will call the controlling driver and
1376 have it switch the device to the requested state in the usual way.
1377 This request by the controlling driver is sticky in that the policy-maker will not
1378 switch the device lower than this request, so if the driver needs power raised for
1379 some reason and then gets it and does what it needs, it should then rescind the
1380 request by requesting state zero. This will allow the policy-maker to control the
1381 device as usual.
1382 @param ordinal
1383 This is the number, in the power state array, of the desired power state.
1384 @result
1385 The return code reflects the state of the policy-maker's internal queue of power
1386 changes and can be ignored by the caller. */
1387 virtual IOReturn changePowerStateTo ( unsigned long ordinal );
1388
1389/*! @function currentCapability
1390 Some object calls a policy-maker here to find out the current capability of a device.
1391 The policy-maker returns a copy of the capabilityFlags field for the current power
1392 state in the power state array. */
1393 virtual IOPMPowerFlags currentCapability ( void );
1394
1395/*! @function currentPowerConsumption
1396 Some object calls a policy-maker here to find out the current power consumption of a device.
1397 The policy-maker returns a copy of the staticPower field for the current power state in the
1398 power state array. */
1399 virtual unsigned long currentPowerConsumption ( void );
1400
1401/*! @function activityTickle
1402 A principal function of a policy-maker is deciding when the device is idle and can be
1403 powered down. To do this it needs to know when the device is being used. In some
1404 cases it is in the data path to the device so it knows when it is being used. In others
1405 it is not and must be told. The activityTickle method is provided for objects in the
1406 system to tell a policy-maker that its device is being used.
1407
1408 If the policy-maker is managing the idleness determination totally on its own, the
1409 paramter should be kIOPMSubclassPolicy, and the policy-maker should intercept
1410 the activityTickle call, because the superclass will do nothing with it.
1411
1412 The IOService superclass can manage idleness determination, too, with the simple
1413 mechanism of an idle timer and this activityTickle call. To start this up, the policy-
1414 maker calls its superclass at setIdleTimerPeriod. This starts a timer for the time
1415 interval specified in the call. When the timer expires, the superclass checks to see
1416 if there has been any activity since the last timer expiration. (It checks to see if
1417 activityTickle has been called). If there has been activity, it restarts the timer, and
1418 this process continues. When the timer expires, and there has been no device
1419 activity, the superclass lowers the device power state to the next lower state.
1420 This can continue until the device is in state zero.
1421
1422 After the device has been powered down by at least one power state,
1423 a call to activityTickle will cause the device to be switched to a higher state
1424 required for the activity.
1425
1426 activityTickle in the IOService superclass is meant to be called by sub-classed
1427 policy-makers, because only they understand the paramters. They may implement
1428 an activityTickle for their clients and then call this activityTickle in the superclass.
1429 @param type
1430 activityTickle with parameter kIOPMSubclassPolicy is not handled in IOService
1431 and should be intercepted by the subclass policy-maker.
1432 activityTickle with parameter kIOPMSuperclassPolicy1 causes an activity flag to be set,
1433 and the device state checked. If the device has been powered down, it is powered up again.
1434 @param stateNumber
1435 When the type parameter is kIOPMSuperclassPolicy1, the stateNumber contains
1436 the desired power state ordinal for the activity. If the device is in a lower state,
1437 the superclass will switch it to this state. This is for devices which can handle
1438 some accesses in lower power states than others; the device is powered up only
1439 as far as it needs to be for the activity.
1440 @result
1441 When the type parameter is kIOPMSuperclassPolicy1, the superclass returns true
1442 if the device is currently in the state specified by stateNumber. If it is in a lower
1443 state and must be brought up, it returns false. In this case the superclass will
1444 cause the device to be brought up. */
1445 virtual bool activityTickle ( unsigned long type, unsigned long stateNumber=0 );
1446
1447/*! @function setAggressiveness
1448 The parent of a policy-maker calls it here while broadcasting an aggressiveness factor
1449 around the power management hierarchy.
1450
1451 A policy-maker may want to intercept this call if it needs to do something with the
1452 new factor, like change its idle timeout, for example. A policy-maker which does
1453 intercept should call setAggressiveness in its superclass, though.
1454 @param type
1455 There are several aggressiveness factors which can be broadcast. One is a general
1456 aggressiveness factor, and the others are specific to parts of the system, like the
1457 hard drive or the display. A policy-maker takes action only on a factor that applies
1458 to its policy. These factor types (e.g. kPMSetGeneralAggressiveness) are defined
1459 in pwr_mgt/IOPM.h.
1460 @param newLevel
1461 This is the aggressiveness factor's new value.
1462 @result
1463 setAggressiveness returns IOPMNoErr. */
1464 virtual IOReturn setAggressiveness ( unsigned long, unsigned long newLevel );
1465
1466 /*! @function getAggressiveness
1467 Return the current aggressiveness value for the given type.
1468 */
1469 virtual IOReturn getAggressiveness ( unsigned long, unsigned long * );
1470
1471 /*! @function systemWake
1472 The parent of a policy-maker calls it here while broadcasting a system wake event.
1473
1474 A policy-maker must intercept this call if its device can wake the system from sleep.
1475 It should check to see if its device did in fact wake the system, and if so, treat the
1476 waking action as activity: it should request power from its parent to keep the system
1477 up until it idles again.
1478
1479 A policy-maker which does intercept should call systemWake in its superclass.
1480 @result
1481 systemWake returns IOPMNoErr. */
1482 virtual IOReturn systemWake ( void );
1483
1484 /*! @function temperatureCriticalForZone
1485 A policy-maker calls its parent power domain to alert it to critical temperature in
1486 some thermal zone.
1487 @param whichZone
1488 This is a pointer to the IOService policy-maker for the thermal zone which has
1489 reported critical temperature.
1490 @result
1491 temperatureCriticalForZone returns IOPMNoErr. */
1492 virtual IOReturn temperatureCriticalForZone ( IOService * whichZone );
1493
1494/*! @function youAreRoot
1495 The Platform Expert instantiates the root power domain IOService and
1496 calls it here to inform it that it is the root power domain.
1497 (The only difference between the root domain and any other power domain
1498 is that the root has no parent and therefore never calls it. */
1499 virtual IOReturn youAreRoot ( void );
1500
1501/*! @function setPowerParent
1502 The Platform Expert or some other IOService calls a policy-maker here to
1503 inform it who its parent is in the power management hierarchy. This is
1504 part of the process of attaching a policy-maker into the hierarchy.
1505 @param theParent
1506 This is a pointer to the parent IOService power domain.
1507 @param stateKnown
1508 This is true if the parent knows its power state. (It would not if it doesn't yet
1509 have a parent or a controlling driver)
1510 @param currentState
1511 If the stateKnown parameter is true, these flags describe the character of
1512 power in the power domain. If the policy-maker has a controlling driver,
1513 the policy-maker asks the driver, given this power domain state,
1514 what state it would be in, and then it tells the driver to assume that state. */
1515 virtual IOReturn setPowerParent ( IOPowerConnection * theParent, bool stateKnown, IOPMPowerFlags currentState );
1516
1517/*! @function addPowerChild
1518 The Platform Expert or some other IOService calls a power domain policy-maker
1519 here to introduce it to a child of it, a member of the domain.
1520 @param theChild
1521 This is a pointer to the child IOService, which is another power domain policy-maker
1522 or a device policy-maker. */
1523 virtual IOReturn addPowerChild ( IOService * theChild );
1524
1525/*! @function removePowerChild
1526 A power domain policy-maker is called here to tell it that one of its enclosed members
1527 is disappearing. This happens when a device policy-maker hands off its responsibility
1528 to another policy-maker or when its device disappears. */
1529 virtual IOReturn removePowerChild ( IOPowerConnection * theChild );
1530
1531/* @function command_received
1532 */
1533 virtual void command_received ( void *, void * , void * , void *);
1534
1535/* @function start_PM_idle_timer
1536 */
1537 virtual void start_PM_idle_timer ( void );
1538
1539/* @function PM_idle_timer_expiration
1540 */
1541 virtual void PM_idle_timer_expiration ( void );
1542
1543/* @function PM_Clamp_Timer_Expired
1544 */
1545 virtual void PM_Clamp_Timer_Expired (void);
1546
1547/*! @function setIdleTimerPeriod
1548 A policy-maker which uses the type 1 idleness determination provided by IOService
1549 calls its superclass here to set or change the idle timer period.
1550
1551 See activityTickle for a description of this idleness determination.
1552 @param period
1553 This is the desired idle timer period in seconds.
1554 @result
1555 The normal return is IOPMNoErr, but it is possible to return kIOReturnError if there
1556 was difficulty creating the timer event or the command queue, for example (which is
1557 done only on the first call.) */
1558 virtual IOReturn setIdleTimerPeriod ( unsigned long );
1559
1560/*! @function getPMworkloop
1561 */
1562 virtual IOWorkLoop *getPMworkloop ( void );
1563
1564/* @function ack_timer_ticked
1565 */
1566 void ack_timer_ticked ( void );
1567
1568/* @function settleTimerExpired
1569 */
1570 void settleTimerExpired ( void );
1571
1572 IOReturn serializedAllowPowerChange2 ( unsigned long );
1573 IOReturn serializedCancelPowerChange2 ( unsigned long );
1574
1575// implemented by power-controlling driver...
1576
1577/*! @function setPowerState
1578 A policy-maker (usually its superclass) calls its controlling driver here to change
1579 the power state of its device.
1580 @param powerStateOrdinal
1581 This is the number in the power state array of the state the driver is being
1582 instructed to switch to.
1583 @param whatDevice
1584 This is a pointer to the policy-maker. It is useful when a single power-controlling
1585 driver controls multiple devices and needs to know for which device it is being
1586 called.
1587 @result
1588 The driver returns IOPMAckImplied if it has complied with the request when it
1589 returns. If it has started the process of changing power state but not finished
1590 it, it should return a number of microseconds which is an upper limit of the time
1591 it will need to finish. Then, when it has completed the power switch, it should
1592 call acknowledgeSetPowerState in the policy-maker. */
1593virtual IOReturn setPowerState ( unsigned long powerStateOrdinal, IOService* whatDevice );
1594
1595/*! @function clampPowerOn
1596 This method sets the device to the highest power state and ensures it stays there
1597 until a timer of duration length expires.
1598 */
1599virtual void clampPowerOn (unsigned long duration);
1600
1601/*! @function maxCapabilityForDomainState
1602 A policy-maker (usually its superclass) calls its controlling driver here to find out
1603 the highest power state possible for a given power domain state. This happens
1604 when the power domain is changing state and the policy-maker wants to find
1605 out what states the device is capable of in the new domain state.
1606 @param domainState
1607 These flags describe the character of domain power in some domain power state.
1608 The flags are not understood by the calling policy-maker; they were passed to it
1609 by its power domain parent. They come from the outputPowerCharacter field
1610 of a state in the power domain's power state array.
1611
1612 This method is implemented in a simple way in IOService. It scans the power state
1613 array looking for the highest state whose inputPowerRequirement field exactly
1614 matches the parameter. If more intelligent determination is required, the
1615 power-controlling driver should implement the method and override the superclass.
1616 @result
1617 A state number is returned. */
1618virtual unsigned long maxCapabilityForDomainState ( IOPMPowerFlags domainState );
1619
1620/*! @function initialPowerStateForDomainState
1621 A policy-maker (usually its superclass) calls its controlling driver here to find out
1622 which power state the device is in, given the current power domain state. This
1623 happens once, when the policy-maker is initializing, and the controlling driver
1624 can use this to know what state the device is in initially.
1625 @param domainState
1626 These flags describe the character of domain power in the current state of the
1627 power domain. The flags are not understood by the calling policy-maker; they
1628 were passed to it by its power domain parent. They come from the
1629 outputPowerCharacter field of the current power state in the power domain's
1630 power state array.
1631
1632 This method is implemented in a simple way in IOService. It scans the power state
1633 array looking for the highest state whose inputPowerRequirement field exactly
1634 matches the parameter. If more intelligent determination is required, the
1635 power-controlling driver should implement the method and override the superclass.
1636 @result
1637 A state number is returned. */
1638virtual unsigned long initialPowerStateForDomainState ( IOPMPowerFlags );
1639
1640/*! @function powerStateForDomainState
1641 A policy-maker (usually its superclass) calls its controlling driver here to find out
1642 what power state the device would be in for a given power domain state. This
1643 happens when the power domain is changing state and the policy-maker wants
1644 to find out the effect of the change.
1645 @param domainState
1646 These flags describe the character of domain power in some domain power state.
1647 The flags are not understood by the calling policy-maker; they were passed to it
1648 by its power domain parent. They come from the outputPowerCharacter field
1649 of a state in the power domain's power state array.
1650
1651 This method is implemented in a simple way in IOService. It scans the power state
1652 array looking for the highest state whose inputPowerRequirement field exactly
1653 matches the parameter. If more intelligent determination is required, the
1654 power-controlling driver should implement the method and override the superclass.
1655 @result
1656 A state number is returned. */
1657virtual unsigned long powerStateForDomainState ( IOPMPowerFlags domainState );
1658
1659/*! @function powerStateWillChangeTo
1660 A policy-maker informs interested parties that its device is about to change to
1661 a different power state. Interested parties are those that have registered for
1662 this notification via registerInterestedDriver and also the power-controlling
1663 driver which is registered as an interested driver automatically when it registers
1664 as the controlling driver.
1665 @param capabilities
1666 These flags describe the capability of the device in the new power state. They
1667 are not understood by the policy-maker; they come from the capabilityFlags field
1668 of the new state in the power state array.
1669 @param stateNumber
1670 This is the number of the state in the state array that the device is switching to.
1671 @param whatDevice
1672 This points to the policy-maker, and it is used by a driver which is receiving power
1673 state change notifications for multiple devices.
1674 @result
1675 The driver returns IOPMAckImplied if it has prepared for the power change when it
1676 returns. If it has started preparing but not finished, it should return a number of
1677 microseconds which is an upper limit of the time it will need to finish preparing.
1678 Then, when it has completed its preparations, it should call acknowledgePowerChange
1679 in the policy-maker. */
1680virtual IOReturn powerStateWillChangeTo ( IOPMPowerFlags, unsigned long, IOService* );
1681
1682/*! @function powerStateDidChangeTo
1683 A policy-maker informs interested parties that its device has changed to
1684 a different power state. Interested parties are those that have registered for
1685 this notification via registerInterestedDriver and also the power-controlling
1686 driver which is registered as an interested driver automatically when it registers
1687 as the controlling driver.
1688 @param capabilities
1689 These flags describe the capability of the device in the new power state. They
1690 are not understood by the policy-maker; they come from the capabilityFlags field
1691 of the new state in the power state array.
1692 @param stateNumber
1693 This is the number of the state in the state array that the device has switched to.
1694 @param whatDevice
1695 This points to the policy-maker, and it is used by a driver which is receiving power
1696 state change notifications for multiple devices.
1697 @result
1698 The driver returns IOPMAckImplied if it has prepared for the power change when it
1699 returns. If it has started preparing but not finished, it should return a number of
1700 microseconds which is an upper limit of the time it will need to finish preparing.
1701 Then, when it has completed its preparations, it should call acknowledgePowerChange
1702 in the policy-maker. */
1703virtual IOReturn powerStateDidChangeTo ( IOPMPowerFlags, unsigned long, IOService* );
1704
1705/*! @function didYouWakeSystem
1706 A policy-maker calls its power driver here to ask if its device is the one
1707 which just woke the system from sleep.
1708 @result
1709 The driver returns true if it did wake the system and false if it didn't. */
1710virtual bool didYouWakeSystem ( void );
1711
1712/*! @function newTemperature
1713 A thermal-zone driver calls its policy-maker here to tell it that the temperature in
1714 the zone has changed. The thermal-zone policy-maker uses this information to
1715 manage its thermal zone.
1716 @param currentTemp
1717 This is the new temperature in the thermal zone.
1718 @param whichZone
1719 This is a pointer to the controlling driver.
1720 */
1721virtual IOReturn newTemperature ( long currentTemp, IOService * whichZone );
1722
1723 virtual bool askChangeDown ( unsigned long );
1724 virtual bool tellChangeDown ( unsigned long );
0b4e3aa0
A
1725 bool tellChangeDown1 ( unsigned long );
1726 bool tellChangeDown2 ( unsigned long );
1c79356b
A
1727 virtual void tellNoChangeDown ( unsigned long );
1728 virtual void tellChangeUp ( unsigned long );
1729 virtual IOReturn allowPowerChange ( unsigned long refcon );
1730 virtual IOReturn cancelPowerChange ( unsigned long refcon );
1731
1732// ...implemented by power-controlling driver
1733
1734 protected:
1735/*! @function changePowerStateToPriv
1736 A policy-maker calls its superclass here to change the power state of the device.
1737 The superclass takes care of making sure the power domain state is appropriate
1738 and informing interested parties. It calls the controlling driver to make the change.
1739 @param ordinal
1740 This is the number, in the power state array, of the desired power state.
1741 @result
1742 The return code reflects the state of the policy-maker's internal queue of power
1743 changes and can be ignored by the caller.
1744 */
1745 IOReturn changePowerStateToPriv ( unsigned long ordinal );
1746
1747/*! @function powerOverrideOnPriv
1748 A policy-maker normally keeps its device at the highest state required by itself,
1749 its power-controlling driver, and its children (when the power domain state
1750 allows). There may be times, however, when a policy-maker needs the power
1751 state lower than its driver or its children desire, and when this is the case, it
1752 calls powerOverrideOnPriv in its superclass to enable this override. When the override
1753 is on, the superclass keeps the device in the state desired by the policy-maker
1754 (requested via changePowerStateToPriv), regardless of the children's or driver's desire.
1755 Turning on the override will initiate a power change if the policy-maker's desired
1756 power state is different from the maximum of the controlling driver's desire and
1757 the children's desires.
1758 @result
1759 The return code reflects the state of the policy-maker's internal queue of power
1760 changes and can be ignored by the caller. */
1761 IOReturn powerOverrideOnPriv ( void );
1762
1763/*! @function powerOverrideOffPriv
1764 When a policy-maker has enabled the override, it can disable it again by calling
1765 this method in its superclass. This will allow the superclass to keep the device
1766 at the highest state required by itself, its power-controlling driver, and its
1767 children (when the power domain state allows). Turning off the override
1768 will initiate a power change if the policy-maker's desired power state is different
1769 from the maximum of the controlling driver's desire and the children's desires.
1770 @result
1771 The return code reflects the state of the policy-maker's internal queue of power
1772 changes and can be ignored by the caller. */
1773 IOReturn powerOverrideOffPriv ( void );
1774
1775 /*! @function powerChangeDone
1776 A policy-maker calls itself here when a power change is completely done, when
1777 all interested parties have acknowledged the powerStateDidChangeTo call.
1778 The implementation here is null; the method is meant to be overridden by
1779 subclassed policy-makers, and that is how one finds out that a power change
1780 it initiated is complete
1781 @param stateNumber
0b4e3aa0 1782 This is the number of the state in the state array that the device has switched from. */
1c79356b
A
1783 virtual void powerChangeDone ( unsigned long );
1784
1785 bool tellClientsWithResponse ( int messageType );
1786 void tellClients ( int messageType );
1787
1788private:
1789
0b4e3aa0
A
1790 IOReturn enqueuePowerChange ( unsigned long, unsigned long, unsigned long, IOPowerConnection *, unsigned long );
1791 void setParentInfo ( IOPMPowerFlags, IOPowerConnection * );
1c79356b
A
1792 IOReturn notifyAll ( bool is_prechange );
1793 bool notifyChild ( IOPowerConnection * nextObject, bool is_prechange );
1794 bool inform ( IOPMinformee * nextObject, bool is_prechange );
1795 void our_prechange_03 ( void );
0b4e3aa0 1796 void our_prechange_04 ( void );
1c79356b
A
1797 void our_prechange_05 ( void );
1798 void our_prechange_1 ( void );
1799 void our_prechange_2 ( void );
1800 void our_prechange_3 ( void );
1801 void our_prechange_4 ( void );
1802 IOReturn parent_down_0 ( void );
0b4e3aa0
A
1803 IOReturn parent_down_02 ( void );
1804 void parent_down_04 ( void );
1c79356b
A
1805 void parent_down_05 ( void );
1806 IOReturn parent_down_1 ( void );
1807 IOReturn parent_down_2 ( void );
1808 void parent_down_3 ( void );
1809 void parent_down_4 ( void );
1810 void parent_down_5 ( void );
1811 void parent_down_6 ( void );
1812 void parent_up_0 ( void );
1813 IOReturn parent_up_1 ( void );
1814 IOReturn parent_up_2 ( void );
1815 IOReturn parent_up_3 ( void );
1816 void parent_up_4 ( void );
1817 void parent_up_5 ( void );
1818 void parent_up_6 ( void );
1819 void all_done ( void );
1820 void all_acked ( void );
1821 void driver_acked ( void );
1822 void start_ack_timer ( void );
1823 void stop_ack_timer ( void );
1824 unsigned long compute_settle_time ( void );
1825 IOReturn startSettleTimer ( unsigned long delay );
1826 IOReturn changeState ( void );
1827 IOReturn add_child_to_active_change ( IOPowerConnection * );
1828 IOReturn add_driver_to_active_change ( IOPMinformee * );
1829 IOReturn instruct_driver ( unsigned long newState );
1830 bool acquire_lock ( void );
1831 IOReturn start_parent_change ( unsigned long queue_head );
1832 void start_our_change ( unsigned long queue_head );
1833 IOReturn ask_parent ( unsigned long requestedState );
1834 bool checkForDone ( void );
1835 bool responseValid ( unsigned long x );
1836 IOReturn allowCancelCommon ( void );
0b4e3aa0 1837 void computeDesiredState ( void );
1c79356b
A
1838};
1839
1840#endif /* ! _IOKIT_IOSERVICE_H */