equal
deleted
inserted
replaced
58 Queues the timer to expire in the specified number of nanokernel ticks. The |
58 Queues the timer to expire in the specified number of nanokernel ticks. The |
59 actual wait time will be at least that much and may be up to one tick more. |
59 actual wait time will be at least that much and may be up to one tick more. |
60 The expiry handler will be called in either ISR context or in the context |
60 The expiry handler will be called in either ISR context or in the context |
61 of the nanokernel timer thread (DfcThread1). |
61 of the nanokernel timer thread (DfcThread1). |
62 |
62 |
63 Note that NKern::TimerTicks() can be used to convert milliseconds to ticks. |
63 Note that NKern::TimerTicks() can be used to convert milliseconds to ticks. |
|
64 |
|
65 Be aware that if you are being called back in DFC context then the DFC thread |
|
66 involved (DfcThread1) will be shared with both the kernel and other device |
|
67 drivers. YOU MUST DO YOUR WORK AND RETURN AS QUICKLY AS POSSIBLE in order to |
|
68 not interfere with the internal workings of the kernel and with other device |
|
69 drivers. If you need to do anything more complex than signalling a semaphore |
|
70 or similar short term processing then you may want to consider using your own |
|
71 DFC queue. Failure to follow these rules WILL LEAD TO INSTABILITY OF THE PHONE. |
64 |
72 |
65 @param aTime Timeout in nanokernel ticks |
73 @param aTime Timeout in nanokernel ticks |
66 @param aDfc TRUE if DFC callback required, FALSE if ISR callback required. |
74 @param aDfc TRUE if DFC callback required, FALSE if ISR callback required. |
67 |
75 |
68 @return KErrNone if no error; KErrInUse if timer is already active. |
76 @return KErrNone if no error; KErrInUse if timer is already active. |