[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAHp75VdMPt60CKnP1HtkN8=3iY7+Kgrv6b9DTjcj-KMKaRknvw@mail.gmail.com>
Date: Sat, 13 Jun 2020 14:11:30 +0300
From: Andy Shevchenko <andy.shevchenko@...il.com>
To: Wolfram Sang <wsa+renesas@...g-engineering.com>
Cc: Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Linux-Renesas <linux-renesas-soc@...r.kernel.org>,
Krzysztof Kozlowski <krzk@...nel.org>,
Oleksij Rempel <o.rempel@...gutronix.de>,
Marc Kleine-Budde <mkl@...gutronix.de>,
Thomas Gleixner <tglx@...utronix.de>
Subject: Re: [PATCH] lib: update DEBUG_SHIRQ docs to match reality
On Fri, Jun 12, 2020 at 3:54 PM Wolfram Sang
<wsa+renesas@...g-engineering.com> wrote:
>
> There is no extra interrupt when registering a shared interrupt handler
> since 2011. Update the Kconfig text to make it clear and to avoid wrong
> assumptions when debugging issues found by it.
>
I'm not sure.
I have recently fixed a bug in the IIO sensor during ->probe() due to
an issued test interrupt exactly as soon as the handler is registered.
...
> - Enable this to generate a spurious interrupt as soon as a shared
> - interrupt handler is registered, and just before one is deregistered.
> - Drivers ought to be able to handle interrupts coming in at those
> - points; some don't and need to be caught.
> + Enable this to generate a spurious interrupt just before a shared
> + interrupt handler is deregistered (generating one when registering
> + is currently disabled). Drivers need to handle this correctly. Some
> + don't and need to be caught.
--
With Best Regards,
Andy Shevchenko
Powered by blists - more mailing lists