Re: [Xenomai] GPIO Interrupts problem with RTDM

[Gilles Chanteperdrix <gilles.chanteperdrix@xenomai.org>]

On 01/19/2013 04:46 PM, Pierre LE COZ wrote:

>> Add some debug messages in the areas you request resources and then use
>> dmesg - The most likely source of error is either attempting to use a
>> resource that has been claimed or not releasing when you have finished
>> with it.
>>
> 
> Here's my entire init :
> 
> static int __init exemple_init (void)
> {
>         int err;
> 
>         printk(KERN_INFO "Requesting GPIO %d\n",GPIO_IN);
>                 if((err = gpio_request_one(GPIO_IN, GPIOF_DIR_IN,
> THIS_MODULE->name)) !=0) {
>                 printk(KERN_INFO "error %d: could not request gpio: %d\n",
> err, GPIO_IN);
>                 return err;
>         }
> 
>         printk(KERN_INFO "Setting the irq type to trigger rising\n");
>         irq_set_irq_type(BUTTON_IRQ,  IRQF_TRIGGER_RISING);
> 
> 
>         printk(KERN_INFO "Requesting irq %d\n", BUTTON_IRQ);
>         if((err = rtdm_irq_request(& irq_exemple, BUTTON_IRQ,
> exemple_handler, 0, THIS_MODULE->name,  NULL)) !=0) {
>                 printk(KERN_INFO "error %d: could not request irq: %d\n",
> err, GPIO_IN);
>                 gpio_free(GPIO_IN);
>                 return err;
>         }
> 
>         printk(KERN_INFO "Enabling irq %d\n", BUTTON_IRQ);
> 
>         // enable_irq(BUTTON_IRQ);
>         rtdm_irq_enable(& irq_exemple);
>         return 0;
> }
> 
> The module is running well, but still no interrupt detected  :
> # insmod rpi-rtdm.ko
> 
> Requesting GPIO 23
> Setting the irq type to trigger rising
> Requesting irq 108
> Enabling irq 108
> /MyDEV/06_GPIO_rtdm_livre # cat /proc/xenomai/irq
> IRQ         CPU0
>   3:        3491         [timer]
> 108:           0         rpi_rtdm
> 259:           0         [virtual]
> /MyDEV/06_GPIO_rtdm_livre #
> 
> When replacing "rtdm_irq_enable(& irq_exemple);" with
> "enable_irq(BUTTON_IRQ);" to try to enable the irq, the module fails :
> # insmod rpi-rtdm.ko
> Requesting GPIO 23
> Setting the irq type to trigger rising
> Requesting irq 108
> Enabling irq 108
> ------------[ cut here ]------------
> WARNING: at kernel/irq/manage.c:421 enable_irq+0x50/0x6c()
> Unbalanced enable for IRQ 108
> Modules linked in: rpi_rtdm(O+)
> [<c00136bc>] (unwind_backtrace+0x0/0xe4) from [<c0021c6c>]
> (warn_slowpath_common+0x4c/0x64)
> [<c0021c6c>] (warn_slowpath_common+0x4c/0x64) from [<c0021d04>]
> (warn_slowpath_fmt+0x2c/0x3c)
> [<c0021d04>] (warn_slowpath_fmt+0x2c/0x3c) from [<c0060c50>]
> (enable_irq+0x50/0x6c)
> [<c0060c50>] (enable_irq+0x50/0x6c) from [<bf0020b4>]
> (exemple_init+0xb4/0xe0 [rpi_rtdm])
> [<bf0020b4>] (exemple_init+0xb4/0xe0 [rpi_rtdm]) from [<c00086a8>]
> (do_one_initcall+0x9c/0x17c)
> [<c00086a8>] (do_one_initcall+0x9c/0x17c) from [<c0051a5c>]
> (sys_init_module+0x1658/0x1830)
> [<c0051a5c>] (sys_init_module+0x1658/0x1830) from [<c000dbe0>]
> (ret_fast_syscall+0x0/0x30)
> ---[ end trace d3f5d198ddeaf1cf ]---
> 
> 
>  About the fact that interrupts are not detected :
> 
> This may be a generic issue, which I thought was fixed, but may not be.
>> Could you try the following patch?
>>
> 
> http://git.xenomai.org/?p=ipipe-gch.git;a=commit;h=c14c79d29fed82267560c7bf26d628ef4d39f5b7
> 
> 
> Thank you Gilles for the patch. I tried it but I could not rebuild my
> kernel :


I do not know what you took. What you were supposed to apply is this diff:

http://git.xenomai.org/?p=ipipe-gch.git;a=commitdiff;h=c14c79d29fed82267560c7bf26d628ef4d39f5b7;hp=3b3b1d3969106b561ec5fee6c0006eff2f1bc1bb

Which should not cause any such issue.

-- 
                                                                Gilles.