![]() |
---|
This is retired content. This content is outdated and is no longer being maintained. It is provided as a courtesy for individuals who are still using these technologies. This content may contain URLs that were valid when originally published, but now link to sites or pages that no longer exist. |
When a PC Card generates an interrupt on the PC Card interrupt line, Card Services calls the interrupt handler that is associated with a specified socket and function pair. Interrupt handlers must conform to the CARD_ISRprototype.
typedef void (*CARD_ISR)( UINT32 uISRContextData );
Members
Remarks
When a PC Card generates an interrupt, Card Services first determines which function caused the interrupt, then calls the associated interrupt service function with the specified socket and function pair. For single function cards, the function number is 0.
A stream interface driver calls CardRequestIRQto register an interrupt service routine (ISR) for a specified socket and function pair. Card Services clears the interrupt condition in the card configuration registers when the interrupt callback function returns.
The interrupt callback function must clear the function interrupt request source on the PC Card and return as quickly as possible. If more time is required for processing the interrupt, the callback function should spawn a thread for further processing of the interrupt.
The interrupt handler is not a true kernel-mode ISR. Rather, it is a user-mode callback function that Card Services calls directly.
Requirements
Runs on | Versions | Defined in | Include | Link to |
---|---|---|---|---|
Windows CE OS | 1.0 and later |
Note This API is part of the complete Windows CE OS package as provided by Microsoft. The functionality of a particular platform is determined by the original equipment manufacturer (OEM) and some devices may not support this API.
See Also
CARD_ISR, CardReleaseIRQ, CardRequestIRQ
Last updated on Tuesday, July 13, 2004