中断与事件绑定总报错！为何？interruptInitialize

chou

中断与事件绑定总报错！为何？interruptInitialize [复制链接]

各位仁兄好：
    我在Kernel\oal\intr.c中的Enabel Disable done中分别添加了对GPIO106、15、95、107的中断处理ISR
   
    1、我在驱动中用kernelIoControl动态申请了一个中断号，然后用interruptInitialize跟事件绑定
       if(!KernelIoControl(IOCTL_HAL_REQUEST_SYSINTR,&g_KeyIrq1,sizeof(UINT32),&g_KeySysIntr1,sizeof(UINT32),NULL))
        {
                RETAILMSG(1,(TEXT("KEYPAD::KernelIoControl Allocate SYSINTR fault!\r\n")));
                goto EXIT;
        }
        RETAILMSG(1,(TEXT("KEYPAD:: KernelIoControl :: g_KeySysIntr1 = %d\r\n"),g_KeySysIntr1));
        if(!InterruptInitialize(g_KeySysIntr1,g_KeyEvent1,0,0))
        {
                RETAILMSG(1,(TEXT("KEYPAD::InterruptInitialize1 fault!\r\n")));
                goto EXIT;
        }
       通过打印信息看，申请到的中断号为16 ，然后InterruptInitialize返回了一个NULL，
       打印出：KEYPAD::InterruptInitialize1 fault!

2、我又在Kernel\oal\intr.c中添加了
         OALIntrStaticTranslate(SYSINTR_KEYPAD1,IRQ_GPIOXX_2_KEY106);
        OALIntrStaticTranslate(SYSINTR_KEYPAD2,IRQ_GPIOXX_2_KEY15);
        OALIntrStaticTranslate(SYSINTR_KEYPAD3,IRQ_GPIOXX_2_KEY95);
        OALIntrStaticTranslate(SYSINTR_KEYPAD4,IRQ_GPIOXX_2_KEY107);
   并在SRC\INC\bsp_cfg.h中添加
#define SYSINTR_KEYPAD1      (SYSINTR_FIRMWARE+4)  //20
#define SYSINTR_KEYPAD2      (SYSINTR_FIRMWARE+7)  //23
#define SYSINTR_KEYPAD3      (SYSINTR_FIRMWARE+8)  //24
#define SYSINTR_KEYPAD4      (SYSINTR_FIRMWARE+9)  //25
然后在驱动中吧kernelIoControl部分去掉
直接将g_KeySysIntr1 = SYSINTR_KEYPAD1 ；
   RETAILMSG(1,(TEXT("KEYPAD:: KernelIoControl :: g_KeySysIntr1 = %d\r\n"),g_KeySysIntr1));
        if(!InterruptInitialize(g_KeySysIntr1,g_KeyEvent1,0,0))
        {
                RETAILMSG(1,(TEXT("KEYPAD::InterruptInitialize1 fault!\r\n")));
                goto EXIT;
        }
这下打印信息g_KeySysIntr1 = 20 ；
但是InterruptInitialize 依然没有成功，打印出：KEYPAD::InterruptInitialize1 fault!
（注：绑定的事件肯定是创建成功了）
请问：
InterruptInitialize总不成功是什么意思啊？人品问题？   

zgyzsq

BOOL InterruptInitialize(
  DWORD idInt,
  HANDLE hEvent,
  LPVOID pvData,
  DWORD cbData
);
Parameters
idInt
[in] Interrupt identifier to be associated with this interrupt service thread (IST).
hEvent
[in] Event to be signaled when the interrupt is triggered.
pvData
[in] This parameter can be used as a pointer to a block of data that is passed to OEMInterruptEnable. The block of data can be initialization data, scratch space, and so on.
cbData
[in] Size of data pointed to by pvData.
Return Values
TRUE indicates success; FALSE indicates failure.

jangseohee

if (!InterruptInitialize(pPublicSpi->dwSpiSysIntr, pPublicSpi->hSpiEvent, NULL, 0))
        {
            RETAILMSG(SPI_INIT,(TEXT("[SPI] SPI Interrupt Initialization failed!!!\n")));
            bResult = FALSE;
            break;
        }

xiejian24919

InterruptInitialize的第3个参数不要用成0看看!!!

liwei3290

OEMInterruptEnable return FALSE with associated SYSINTR_xxx.

Please check your kernel code to ensure the OEMInterruptEnable return value.

Paul, Chao @ Techware

tencom

找到了
我的IRQ值超过了IRQ_MAINSTONEII_GPIOXX_2_MAX
.......