From: cavokz@gmail.com (Domenico Andreoli)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v4 4/4] ARM: bcm4760: Add restart hook
Date: Mon, 30 Sep 2013 16:02:46 +0200 [thread overview]
Message-ID: <20130930140246.GA25992@glitch> (raw)
In-Reply-To: <13398230.iOE1HhgZy2@wuerfel>
Hi Wim,
On Mon, Sep 16, 2013 at 10:01:08PM +0200, Arnd Bergmann wrote:
> On Monday 16 September 2013 14:00:01 Wim Van Sebroeck wrote:
> >
> > I remember that the Cobalt Devices have no ability to reboot themselves.
> > That's why the driver uses the reboot_notifier for rebooting the device.
> > See drivers/watchdog/alim7101_wdt.c .
>
> Hmm, a notifier seems the wrong approach here, because we really want
> to handle all reboot_notifiers before actually rebooting, and we'd enter
> the wdt driver at a random point in the notifier chain. It probably works
> by chance if the watchdog reboots a second after its notifier is called,
> and all other calls are done as well, but it doesn't seem like a clean
> solution.
>
> > I'll have a look to have an extra ops that adds this functionality in the framework.
I'd like to do something here.
I'm thinking at a simple "atomic_reset()" wdt op which purpose it to use
the specific watchdog to trigger a HW reset. As the name implies, the call
needs to be callable in atomic context. Any other constrains I'm missing?
At this point a DT attribute in the wdt stanzas could be used to register
the reboot hook at runtime.
thanks,
Domenico
prev parent reply other threads:[~2013-09-30 14:02 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-14 15:20 [PATCH v4 0/4] ARM: Broadcom BCM4760 support Domenico Andreoli
2013-09-14 15:20 ` [PATCH v4 1/4] ARM: bcm4760: Add platform infrastructure Domenico Andreoli
2013-09-15 18:03 ` Arnd Bergmann
2013-09-14 15:20 ` [PATCH v4 2/4] ARM: bcm4760: Add system timer Domenico Andreoli
2013-09-14 15:20 ` [PATCH v4 3/4] ARM: bcm4760: Add ripple counter Domenico Andreoli
2013-09-14 15:20 ` [PATCH v4 4/4] ARM: bcm4760: Add restart hook Domenico Andreoli
2013-09-15 18:09 ` Arnd Bergmann
2013-09-15 18:52 ` Domenico Andreoli
2013-09-15 20:10 ` Arnd Bergmann
2013-09-16 7:18 ` Domenico Andreoli
2013-09-16 8:45 ` Arnd Bergmann
[not found] ` <20130916120001.GE401@spo001.leaseweb.com>
2013-09-16 20:01 ` Arnd Bergmann
2013-09-30 14:02 ` Domenico Andreoli [this message]
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=20130930140246.GA25992@glitch \
--to=cavokz@gmail.com \
--cc=linux-arm-kernel@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).