[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAHp75VfvP7s-ud0XRUfESjTNRdbaZH_qKRpXbkCzKqp8j5e6kg@mail.gmail.com>
Date: Wed, 18 Jul 2018 13:33:39 +0300
From: Andy Shevchenko <andy.shevchenko@...il.com>
To: Alexandre Belloni <alexandre.belloni@...tlin.com>
Cc: Mark Brown <broonie@...nel.org>, James Hogan <jhogan@...nel.org>,
Paul Burton <paul.burton@...s.com>,
linux-spi <linux-spi@...r.kernel.org>,
devicetree <devicetree@...r.kernel.org>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Linux MIPS Mailing List <linux-mips@...ux-mips.org>,
Thomas Petazzoni <thomas.petazzoni@...tlin.com>,
Allan Nielsen <allan.nielsen@...rosemi.com>
Subject: Re: [PATCH 1/5] spi: dw: fix possible race condition
On Wed, Jul 18, 2018 at 1:13 AM, Alexandre Belloni
<alexandre.belloni@...tlin.com> 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@...tlin.com> 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
Powered by blists - more mailing lists