Share via

CARD_ISR (Windows Embedded CE 6.0)

  • Article

1/6/2010

This structure stores context data specified by CardRequestIRQ. 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_ISR prototype.

Syntax

typedef void (*CARD_ISR)( 
  UINT32 uISRContextData 
);

Members

  • uISRContextData
    Contains context data specified by the CardRequestIRQ function that the driver can interpret as needed. This member is usually a pointer to a structure representing the state of the socket and function pair.

Remarks

When a PC Card generates an interrupt, card services first determines which function caused the interrupt, and 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 CardRequestIRQ to 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

Header cardserv.h
Windows Embedded CE Windows CE 1.0 and later

See Also

Reference

PCMCIA Legacy Compatiblity Layer Structures
CardReleaseIRQ
CardRequestIRQ