From: Linus Walleij <linus.walleij@linaro.org>
To: Daniel Lezcano <daniel.lezcano@linaro.org>
Cc: "Thomas Gleixner" <tglx@linutronix.de>,
linux-kernel <linux-kernel@vger.kernel.org>,
"Cédric Le Goater" <clg@kaod.org>,
"Joel Stanley" <joel@jms.id.au>
Subject: Re: [PATCH 2/2] clocksource/drivers/fttmr010: Be stricter on IRQs
Date: Fri, 20 Aug 2021 15:39:41 +0200 [thread overview]
Message-ID: <CACRpkdYh6E+gCihouapFYX33U-ccJk7DF1oHax5vUS2CiqDOrg@mail.gmail.com> (raw)
In-Reply-To: <e997cca5-e6d4-1aac-4e0c-de15d7664a1b@linaro.org>
On Fri, Aug 20, 2021 at 10:53 AM Daniel Lezcano
<daniel.lezcano@linaro.org> wrote:
>
> On 25/07/2021 00:44, Linus Walleij wrote:
> > Make sure we check that the right interrupt occurred before
> > calling the event handler for timer 1. Report spurious IRQs
> > as IRQ_NONE.
>
> Does it not mean there is something wrong with the initial setup ?
No it is not occurring. This is just to protect against ordinary
spurious interrupts (return from sleep glitches in electronics,
quantum effects...)
Yours,
Linus Walleij
next prev parent reply other threads:[~2021-08-20 13:39 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-24 22:44 [PATCH 1/2] clocksource/drivers/fttmr010: Pass around less pointers Linus Walleij
2021-07-24 22:44 ` [PATCH 2/2] clocksource/drivers/fttmr010: Be stricter on IRQs Linus Walleij
2021-08-20 8:53 ` Daniel Lezcano
2021-08-20 13:39 ` Linus Walleij [this message]
2021-08-20 14:16 ` Daniel Lezcano
2021-08-21 4:20 ` Guenter Roeck
2021-08-21 8:04 ` Daniel Lezcano
2021-08-27 22:01 ` Linus Walleij
2021-08-27 22:31 ` Guenter Roeck
2021-08-28 3:37 ` Guenter Roeck
2021-08-28 8:08 ` Cédric Le Goater
2021-08-30 4:16 ` Andrew Jeffery
2021-08-30 4:58 ` [PATCH 2/2]: Be stric clocksource/drivers/fttmr010ter " Guenter Roeck
2021-08-30 6:30 ` Andrew Jeffery
2021-08-30 7:47 ` [PATCH 2/2]: Be stric clocksource/drivers/fttmr010 " Cédric Le Goater
2021-08-30 15:24 ` Guenter Roeck
2021-09-01 23:38 ` [PATCH 2/2] clocksource/drivers/fttmr010: Be stricter " Joel Stanley
2021-08-26 16:25 ` [tip: timers/core] clocksource/drivers/fttmr010: Pass around less pointers tip-bot2 for Linus Walleij
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=CACRpkdYh6E+gCihouapFYX33U-ccJk7DF1oHax5vUS2CiqDOrg@mail.gmail.com \
--to=linus.walleij@linaro.org \
--cc=clg@kaod.org \
--cc=daniel.lezcano@linaro.org \
--cc=joel@jms.id.au \
--cc=linux-kernel@vger.kernel.org \
--cc=tglx@linutronix.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.