From: Andy Shevchenko <andy.shevchenko@gmail.com>
To: Wolfram Sang <wsa+renesas@sang-engineering.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux-Renesas <linux-renesas-soc@vger.kernel.org>,
Krzysztof Kozlowski <krzk@kernel.org>,
Oleksij Rempel <o.rempel@pengutronix.de>,
Marc Kleine-Budde <mkl@pengutronix.de>,
Thomas Gleixner <tglx@linutronix.de>
Subject: Re: [PATCH] lib: update DEBUG_SHIRQ docs to match reality
Date: Sat, 13 Jun 2020 14:11:30 +0300 [thread overview]
Message-ID: <CAHp75VdMPt60CKnP1HtkN8=3iY7+Kgrv6b9DTjcj-KMKaRknvw@mail.gmail.com> (raw)
In-Reply-To: <20200612124844.19422-1-wsa+renesas@sang-engineering.com>
On Fri, Jun 12, 2020 at 3:54 PM Wolfram Sang
<wsa+renesas@sang-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
next prev parent reply other threads:[~2020-06-13 11:11 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-12 12:48 [PATCH] lib: update DEBUG_SHIRQ docs to match reality Wolfram Sang
2020-06-12 13:15 ` Krzysztof Kozlowski
2020-06-13 11:11 ` Andy Shevchenko [this message]
2020-06-13 11:39 ` Wolfram Sang
2020-06-13 11:54 ` Andy Shevchenko
2020-06-22 15:56 ` Wolfram Sang
2020-06-22 16:01 ` Andy Shevchenko
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAHp75VdMPt60CKnP1HtkN8=3iY7+Kgrv6b9DTjcj-KMKaRknvw@mail.gmail.com' \
--to=andy.shevchenko@gmail.com \
--cc=krzk@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=mkl@pengutronix.de \
--cc=o.rempel@pengutronix.de \
--cc=tglx@linutronix.de \
--cc=wsa+renesas@sang-engineering.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).