Many thanks for your repost of the debugging messages. Emil Naepflein writes: > As far as I unterstood, both gpioirq() and debiirq() share state. To > work correctly the state prepared by gpioirq() has to be processed later > with a debiirq(). If a other gpioirq() comes in between we get the GPIO0 > irq oops. You can see above different variants of this race. > > To fix this the processing of new gpio interrupts have to be delayed > until the debi interrupt has been processed.
Yes, but they should not happen in the first place. We will need some more detailed debugging info to find the position when e.g. the gpioirq() interrupts the debi processing. It should not be able to happen before the mailbox register in DPRAM is cleared. The firmware simply should not set a new interrupt before that. I'll see if I have the time to take a closer look. Ralph -- Info: To unsubscribe send a mail to [EMAIL PROTECTED] with "unsubscribe linux-dvb" as subject.
