On Wed, Jul 18, 2018 at 1:13 AM, Alexandre Belloni <alexandre.belloni@xxxxxxxxxxx> wrote: > On 18/07/2018 00:54:21+0300, Andy Shevchenko wrote: >> On Wed, Jul 18, 2018 at 12:42 AM, Alexandre Belloni >> <alexandre.belloni@xxxxxxxxxxx> wrote: >> > On 18/07/2018 00:30:49+0300, Andy Shevchenko wrote: >> > Well, I'm not sure how far this can be backported. It also seems nobody >> > ever hit that while our hardware will hit it at every boot. >> No-one enabled CONFIG_DEBUG_SHIRQ? > Nope, this is a real HW IRQ. I meant find out up to when it can be > sanely backported. I meant that before your case no-one tested with that option enabled which will behave like you describe (IRQ gets fired as soon as being registered). -- With Best Regards, Andy Shevchenko
