On Mon, Jul 29, 2013 at 2:40 PM, Javier Martinez Canillas <javier.martinez@xxxxxxxxxxxxxxx> wrote: > On 29/07/2013, at 13:43, Linus Walleij <linus.walleij@xxxxxxxxxx> wrote: >> So I'm drafting an RFC to indicate how I think this should >> be solved. >> > > Great, I hope we can finally have a good solution for this long standing issue. I have sent out this RFC patch, subject: "RFC: interrupt consistency check for OF GPIO IRQs" Please review the general concept of this patch and whether it would help solving the OMAP situation for v3.12. The patch as it stands will not work, and I cannot create a proper test here because I have no test target system (I am technically on vacation), but I will get to it as I get back. And folks: you shouldn't feel bad about this. The problem is not OMAPs at all, the problem has been there all the time and we have discussed it for some time, it just happened that OMAP was the first system that tried to come up with some kind of fix for it, and for this you should be thanked, even if we need to take another path in the end. Yours, Linus Walleij -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
