From: Thomas Gleixner <tglx@linutronix.de>
To: "fixed-term.Oleksij.Rempel" <fixed-term.Oleksij.Rempel@de.bosch.com>
Cc: Daniel Lezcano <daniel.lezcano@linaro.org>,
linux-kernel@vger.kernel.org,
"Dirk.Behme" <Dirk.Behme@de.bosch.com>
Subject: Re: clockevent driver as source for pretimout watchdog interrupt
Date: Thu, 21 Apr 2016 10:45:38 +0200 (CEST) [thread overview]
Message-ID: <alpine.DEB.2.11.1604211044440.3941@nanos> (raw)
In-Reply-To: <57186D9B.6000006@de.bosch.com>
On Thu, 21 Apr 2016, fixed-term.Oleksij.Rempel wrote:
> i'm doing research on proper implementation for watchdog pretimout
> interrupt for devices which do not provide this functionality.
>
> Some watchdog controllers like Freescale iMX6 can generate an interrupt
> for some configured time before watchdog will reset the system.
> Suddenly most watchdog controllers don't have this functionality.
>
> My idea is to reuse some count down (one shot?) timer:
> - configure it to generate an interrupt for a time less then watchdog
> deadline.
> - reset it each time we get a ping, before an interrupt is generated.
> - interrupt should executed one of governors from pretimout patchset,
> see the link:
> https://www.mail-archive.com/linux-watchdog@vger.kernel.org/msg02394.html
>
> I assume clocksource framework is kind of suitable for this purpose? Is
> it correct assumption?
> Any other ideas? Suggestions?
What's wrong with simply using a hrtimer for this? The extra clockevent is not
buying you anything AFAICT.
Thanks,
tglx
parent reply other threads:[~2016-04-21 8:47 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <57186D9B.6000006@de.bosch.com>]
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=alpine.DEB.2.11.1604211044440.3941@nanos \
--to=tglx@linutronix.de \
--cc=Dirk.Behme@de.bosch.com \
--cc=daniel.lezcano@linaro.org \
--cc=fixed-term.Oleksij.Rempel@de.bosch.com \
--cc=linux-kernel@vger.kernel.org \
/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
all inboxes | Powered by JetHome®