This IRQ storm is very likely what bites you. The GPIO IRQ does not seem
to be properly masked upon arrival, or maybe re-enabled too early,

Hi, thanks for the helpful explanation. Together with hint from

http://blackfin.uclinux.org/gf/forummessage/96808

this lead me to comment out the check for the interrupt trigger type in
mach-common/ints_priority.c:bfin_gpio_mask_ack_irq so that
set_gpio_data(gpionr, 0) is called in any case.

At least, that helps so that my system doesn't freeze and I can read "keyboard" 
 events generated by gpio-keys from /dev/input/event0

Kolja

_______________________________________________
Xenomai-help mailing list
[email protected]
https://mail.gna.org/listinfo/xenomai-help

Reply via email to