Next: 2.19 InterruptDisable() Up: 2. WD_xxx PCI/PCMCIA/ISA Functions Previous: 2.17 WD_PcmciaControl() Contents

2.18 InterruptEnable()

PURPOSE

$\bullet$ A convenient function for setting up interrupt handling.

PROTOTYPE

DWORD InterruptEnable(
    HANDLE *phThread,
    HANDLE hWD,
    WD_INTERRUPT *pInt,
    INT_HANDLER func,
    PVOID pData);

PARAMETERS

Name Type Input/Output

$\bullet$ phThread HANDLE* Output

$\bullet$ hWD HANDLE Input

$\bullet$ pInt WD_INTERRUPT*

$\gg$ hInterrupt DWORD Input

$\gg$ dwOptions DWORD Input

$\gg$ Cmd WD_TRANSFER* Input

$\gg$ dwCmds DWORD Input

$\gg$ kpCall WD_KERNEL_PLUGIN_CALL

$\diamond$ hKernelPlugIn DWORD Input

$\diamond$ dwMessage DWORD N/A

$\diamond$ pData PVOID N/A

$\diamond$ dwResult DWORD N/A

$\gg$ fEnableOk DWORD N/A

$\gg$ dwCounter DWORD N/A

$\gg$ dwLost DWORD N/A

$\gg$ fStopped DWORD N/A

$\gg$ dwLastMessage DWORD N/A

$\gg$ dwEnabledIntType DWORD Output

$\bullet$ func typedef void (*INT_HANDLER)(
PVOID pData); Input

$\bullet$ pData PVOID Input

Name	Type	Input/Output
$\bullet$ phThread	HANDLE*	Output
$\bullet$ hWD	HANDLE	Input
$\bullet$ pInt	WD_INTERRUPT*
$\gg$ hInterrupt	DWORD	Input
$\gg$ dwOptions	DWORD	Input
$\gg$ Cmd	WD_TRANSFER*	Input
$\gg$ dwCmds	DWORD	Input
$\gg$ kpCall	WD_KERNEL_PLUGIN_CALL
$\diamond$ hKernelPlugIn	DWORD	Input
$\diamond$ dwMessage	DWORD	N/A
$\diamond$ pData	PVOID	N/A
$\diamond$ dwResult	DWORD	N/A
$\gg$ fEnableOk	DWORD	N/A
$\gg$ dwCounter	DWORD	N/A
$\gg$ dwLost	DWORD	N/A
$\gg$ fStopped	DWORD	N/A
$\gg$ dwLastMessage	DWORD	N/A
$\gg$ dwEnabledIntType	DWORD	Output
$\bullet$ func	typedef void (*INT_HANDLER)( PVOID pData);	Input
$\bullet$ pData	PVOID	Input

DESCRIPTION

Name Description

phThread Pointer to the handle to the spawned interrupt thread, which should be passed to InterruptDisable() [2.19] when disabling the interrupt

hWD Handle to WinDriver's kernel-mode driver as received from WD_Open() [5.2]

pInt Pointer to an interrupt information structure:

$\bullet$ hInterrupt Internal interrupt handle, as received from WD_CardRegister() [2.8] in I.Int.hInterrupt

$\bullet$ dwOptions Interrupt options bit-mask. Can be set to zero or to:
$\bullet$ INTERRUPT_CMD_COPY: if set, WinDriver will copy the data received from the read commands that were used to acknowledge the interrupt, in the kernel mode, back to the user mode. The data will be available to the user when the interrupt handler routine (func) is called.

$\bullet$ Cmd An array of transfer commands information structures that define the operations to be performed at the kernel level upon the detection of an interrupt, or NULL if no transfer commands are required.

NOTE: When handling level sensitive interrupts (such as PCI interrupts) in the user mode (without a Kernel PlugIn driver), you must use this array to define the hardware-specific commands for acknowledging the interrupts in the kernel, immediately when they are received.

The commands in the array can be either of the following:

$\bullet$ A read/write transfer command that conforms to the following format: <dir><p>_[S]<size> - see the description of pTrans->cmdTrans in section 2.11.

$\bullet$ CMD_MASK: an interrupt mask command for determining the source of the interrupt: When this command is set, upon the arrival of an interrupt in the kernel WinDriver masks the value of the previous read command in the WD_TRANSFER commands array with the mask that is set in the relevant Data field union member of the mask transfer command. For example, for a Cmd WD_TRANSFER array, if Cmd[i-1].cmdTrans is RM_BYTE, WinDriver performs the following mask: Cmd[i-1].Data.Byte & Cmd[i].Data.Byte. If the mask is successful, the driver claims ownership of the interrupt and when the control is returned to the user mode, the interrupt handler routine that was passed to the interrupt enable function is invoked; otherwise, the driver rejects ownership of the interrupt, the interrupt handler routine is not invoked and the subsequent transfer commands in the array are not executed.
(Acceptance and rejection of the interrupt is relevant only when handling legacy interrupts; since MSI/MSI-X interrupts are not shared, WinDriver will always accept control of such interrupts.)
NOTE: A CMD_MASK command must be preceded by a read transfer command (RM_XXX / RP_XXX).

$\bullet$ dwCmds Number of transfer commands in the Cmd array

$\bullet$ kpCall Kernel PlugIn message information structure:

$\gg$ hKernelPlugIn Handle to Kernel PlugIn returned from WD_KernelPlugInOpen() [6.1].

$\bullet$ dwEnabledIntType Updated by the function to indicate the type of interrupt enabled for the device. Can be set to any of the following values:
$\bullet$ INTERRUPT_MESSAGE_X: Extended Message-Signaled Interrups (MSI-X). $^{\scriptsize {*}}$
$\bullet$ INTERRUPT_MESSAGE: Message-Signaled Interrups (MSI). $^{\scriptsize {*}}$
$\bullet$ INTERRUPT_LEVEL_SENSITIVE: legacy level sensitive interrupts.
$\bullet$ 0: Default interrupt type - legacy edge trigerred interrupts.

NOTE:
$^{\scriptsize {*}}$ The Windows APIs do not distinguish between MSI and MSI-X; therefore, on this OS the WinDriver functions set the INTERRUPT_MESSAGE flag for both MSI and MSI-X.
$^{\scriptsize {**}}$ This field normally relevant only in the case of PCI devices that support more than one type of interrupt.

func The interrupt handler routine, which will be called once for every interrupt occurrence. (Note: The INT_HANDLER function type is defined in windrvr_int_thread.h).

pData Pointer to the data to be passed as the argument to the interrupt handler routine (func)

Name	Description
phThread	Pointer to the handle to the spawned interrupt thread, which should be passed to `InterruptDisable()` [2.19] when disabling the interrupt
hWD	Handle to WinDriver's kernel-mode driver as received from `WD_Open()` [5.2]
pInt	Pointer to an interrupt information structure:
$\bullet$ hInterrupt	Internal interrupt handle, as received from `WD_CardRegister()` [2.8] in `I.Int.hInterrupt`
$\bullet$ dwOptions	Interrupt options bit-mask. Can be set to zero or to: $\bullet$ INTERRUPT_CMD_COPY: if set, WinDriver will copy the data received from the read commands that were used to acknowledge the interrupt, in the kernel mode, back to the user mode. The data will be available to the user when the interrupt handler routine (func) is called.
$\bullet$ Cmd	An array of transfer commands information structures that define the operations to be performed at the kernel level upon the detection of an interrupt, or `NULL` if no transfer commands are required. NOTE: When handling level sensitive interrupts (such as PCI interrupts) in the user mode (without a Kernel PlugIn driver), you must use this array to define the hardware-specific commands for acknowledging the interrupts in the kernel, immediately when they are received. The commands in the array can be either of the following: $\bullet$ A read/write transfer command that conforms to the following format: <dir><p>_[S]<size> - see the description of `pTrans->cmdTrans` in section 2.11. $\bullet$ CMD_MASK: an interrupt mask command for determining the source of the interrupt: When this command is set, upon the arrival of an interrupt in the kernel WinDriver masks the value of the previous read command in the `WD_TRANSFER` commands array with the mask that is set in the relevant `Data` field union member of the mask transfer command. For example, for a `Cmd WD_TRANSFER` array, if `Cmd[i-1].cmdTrans` is `RM_BYTE`, WinDriver performs the following mask: `Cmd[i-1].Data.Byte & Cmd[i].Data.Byte`. If the mask is successful, the driver claims ownership of the interrupt and when the control is returned to the user mode, the interrupt handler routine that was passed to the interrupt enable function is invoked; otherwise, the driver rejects ownership of the interrupt, the interrupt handler routine is not invoked and the subsequent transfer commands in the array are not executed. (Acceptance and rejection of the interrupt is relevant only when handling legacy interrupts; since MSI/MSI-X interrupts are not shared, WinDriver will always accept control of such interrupts.) NOTE: A `CMD_MASK` command must be preceded by a read transfer command (`RM_XXX / RP_XXX`).
$\bullet$ dwCmds	Number of transfer commands in the Cmd array
$\bullet$ kpCall	Kernel PlugIn message information structure:
$\gg$ hKernelPlugIn	Handle to Kernel PlugIn returned from `WD_KernelPlugInOpen()` [6.1].
$\bullet$ dwEnabledIntType	Updated by the function to indicate the type of interrupt enabled for the device. Can be set to any of the following values: $\bullet$ INTERRUPT_MESSAGE_X: Extended Message-Signaled Interrups (MSI-X). $^{\scriptsize {}}$ $\bullet$ INTERRUPT_MESSAGE: Message-Signaled Interrups (MSI). $^{\scriptsize {}}$ $\bullet$ INTERRUPT_LEVEL_SENSITIVE: legacy level sensitive interrupts. $\bullet$ 0: Default interrupt type - legacy edge trigerred interrupts. NOTE: $^{\scriptsize {}}$ The Windows* APIs do not distinguish between MSI and MSI-X; therefore, on this OS the WinDriver functions set the INTERRUPT_MESSAGE flag for both MSI and MSI-X. $^{\scriptsize {**}}$ This field normally relevant only in the case of PCI devices that support more than one type of interrupt.
func	The interrupt handler routine, which will be called once for every interrupt occurrence. (Note: The `INT_HANDLER` function type is defined in windrvr_int_thread.h).
pData	Pointer to the data to be passed as the argument to the interrupt handler routine (func)

RETURN VALUE

Returns WD_STATUS_SUCCESS (0) on success, or an appropriate error code otherwise [A].

REMARKS

You can view the implementation of this function in WinDriver/src/wdapi/windrvr_int_thread.c.
InterruptEnable() uses the low-level WD_IntEnable() [3.2], WD_IntWait() [3.3] and WD_IntCount() [3.4] functions and replaces the need to call these functions separately, although this is still possible.
To improve the interrupt handling rate on Windows 98/Me/2000/XP/Server 2003/Vista, Linux and Solaris, consider using WinDriver's Kernel PlugIn feature (see the WinDriver PCI Manual).

EXAMPLE

VOID DLLCALLCONV interrupt_handler(PVOID pData)
{
    WD_INTERRUPT *pIntrp = (WD_INTERRUPT *)pData;
    /* Implement your interrupt handler routine here */
   
    printf("Got interrupt %d\n", pIntrp->dwCounter);
}

....
main()
{
    WD_CARD_REGISTER cardReg;
    WD_INTERRUPT Intrp;
    HANDLE hWD, thread_handle;

    ....
    hWD = WD_Open();
    BZERO(cardReg);
    cardReg.Card.dwItems = 1;
    cardReg.Card.Item[0].item = ITEM_INTERRUPT;
    cardReg.Card.Item[0].fNotSharable = TRUE;
    cardReg.Card.Item[0].I.Int.dwInterrupt = MY_IRQ;
    cardReg.Card.Item[0].I.Int.dwOptions = 0;
    ....
    WD_CardRegister(hWd, &cardReg);
    ....
    PVOID pdata = NULL;
    BZERO (Intrp);
    Intrp.hInterrupt = cardReg.Card.Item[0].I.Int.hInterrupt;
    Intrp.Cmd = NULL;
    Intrp.dwCmds = 0;
    Intrp.dwOptions = 0;
    printf("starting interrupt thread\n");
    pData = &Intrp;

    if (!InterruptEnable(&thread_handle, hWD, &Intrp,
        interrupt_handler, pdata))
    {
        printf ("failed enabling interrupt\n")
    }
    else
    { 
        printf("Press Enter to uninstall interrupt\n");
        fgets(line, sizeof(line), stdin);
        InterruptDisable(thread_handle); /* Calls WD_IntDisable() */
    }
    WD_CardUnregister(hWD, &cardReg);
    ....
}

Next: 2.19 InterruptDisable() Up: 2. WD_xxx PCI/PCMCIA/ISA Functions Previous: 2.17 WD_PcmciaControl() Contents