From: joshc@codeaurora.org (Josh Cartwright)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] pinctrl: qcom: use restart_notifier mechanism for ps_hold
Date: Thu, 18 Sep 2014 17:49:04 -0500 [thread overview]
Message-ID: <20140918224904.GD3749@joshc.qualcomm.com> (raw)
In-Reply-To: <11F1E440-6BD4-46F1-A399-4334FBA2C3B6@codeaurora.org>
On Thu, Sep 18, 2014 at 03:47:20PM -0700, Kumar Gala wrote:
> On Sep 18, 2014, at 3:32 PM, Josh Cartwright <joshc@codeaurora.org> wrote:
>
> > By converting to the restart_notifier mechanism for restart, we allow
> > for other mechanisms, like the watchdog, to be used for restart in the
> > case where PS_HOLD has failed to reset the chip.
> >
> > Choose priority 128, as according to documentation, this mechanism "is
> > sufficient to restart the entire system?.
>
> Will we use a higher priority for watchdog? or how would we fail over to watchdog?
The registered restart handlers are called in (descending) priority
order. This driver registers as 128, but conceivably there could be
some super-board-specific restart mechanism that can register itself as
higher priority than this and it will be attempted first.
If PS_HOLD doesn't work, the lower priority restart handlers will
continue to be called, including the watchdog, which is registering with
the lowest priority (0).
--
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
hosted by The Linux Foundation
next prev parent reply other threads:[~2014-09-18 22:49 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-18 22:32 [PATCH] pinctrl: qcom: use restart_notifier mechanism for ps_hold Josh Cartwright
2014-09-18 22:47 ` Kumar Gala
2014-09-18 22:49 ` Josh Cartwright [this message]
2014-09-18 23:02 ` Kumar Gala
2014-09-19 2:54 ` Guenter Roeck
2014-09-19 3:34 ` Guenter Roeck
2014-09-19 15:19 ` Josh Cartwright
2014-09-19 15:09 ` Josh Cartwright
2014-09-19 12:28 ` Pramod Gurav
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=20140918224904.GD3749@joshc.qualcomm.com \
--to=joshc@codeaurora.org \
--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).