linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: joshc@codeaurora.org (Josh Cartwright)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 3/3] watchdog: qcom: register a restart notifier
Date: Thu, 18 Sep 2014 22:32:02 -0500	[thread overview]
Message-ID: <20140919033202.GF3749@joshc.qualcomm.com> (raw)
In-Reply-To: <541B995A.6000609@roeck-us.net>

On Thu, Sep 18, 2014 at 07:47:54PM -0700, Guenter Roeck wrote:
> On 09/18/2014 03:27 PM, Josh Cartwright wrote:
> >The WDT's BITE_TIME warm-reset behavior can be leveraged as a last
> >resort mechanism for triggering chip reset.  Usually, other restart
> >methods (such as PS_HOLD) are preferrable for issuing a more complete
> >reset of the chip.  As such, keep the priority of the watchdog notifier
> >low.
> >
> >Signed-off-by: Josh Cartwright <joshc@codeaurora.org>
[..]
> >+static int qcom_wdt_restart(struct notifier_block *nb, unsigned long action,
> >+			    void *data)
> >+{
> >+	struct qcom_wdt *wdt = container_of(nb, struct qcom_wdt, restart_nb);
> >+
> >+	/*
> >+	 * Trigger watchdog bite:
> >+	 *    Setup BITE_TIME to be very low, and enable WDT.
> >+	 */
> >+	mutex_lock(&wdt->wdd.lock);
> 
> At this time you don't need to worry about locks.
> 
> Actually, this might be dangerous if the lock happens to be taken,
> as it won't be released (there is no other code running anymore
> when this function is called).

Ah, great.  I'll drop the locking.

> >+	writel_relaxed(0, wdt->base + WDT_EN);
> >+	writel_relaxed(1, wdt->base + WDT_RST);
> >+	writel_relaxed(0x31F3, wdt->base + WDT_BITE_TIME);
> 
> What is the magic here, ie what does 0x31F3 stand for ?

Nothing magic, it's just a reasonably low value to set the bite time
counter at.  It also happens to be the value at reset.

> >+	writel_relaxed(1, wdt->base + WDT_EN);
> >+	mutex_unlock(&wdt->wdd.lock);
> >+	return NOTIFY_DONE;
> >+}
> >+
> >  static int qcom_watchdog_probe(struct platform_device *pdev)
> >  {
> >  	struct qcom_wdt *wdt;
> >@@ -121,6 +141,17 @@ static int qcom_watchdog_probe(struct platform_device *pdev)
> >  		return ret;
> >  	}
> >
> >+	/*
> >+	 * WDT restart notifier has priority 0 (use as a last resort)
> >+	 */
> >+	wdt->restart_nb.notifier_call = qcom_wdt_restart;
> >+	ret = register_restart_handler(&wdt->restart_nb);
> >+	if (ret) {
> >+		dev_err(&pdev->dev, "failed to setup restart handler\n");
> >+		watchdog_unregister_device(&wdt->wdd);
> >+		return ret;
> 
> Sure you want to return an error here ? The watchdog itself is still working,
> and this is supposed to be a restart method of last resort. Causing the driver
> to fail loading because it can not register its restart handler seems to be
> a bit aggressive.

It is a bit aggressive.  I'll at least drop it to a dev_warn(); even
though it is a "last resort", on some boards it's the only available
mechanism for reliable restart.

Thanks!
  Josh

-- 
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
hosted by The Linux Foundation

  reply	other threads:[~2014-09-19  3:32 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-18 22:26 [PATCH 0/3] watchdog: add support for QCOM WDT Josh Cartwright
2014-09-18 22:26 ` [PATCH 1/3] watchdog: qcom: add support for KPSS WDT Josh Cartwright
2014-09-19  2:41   ` Guenter Roeck
2014-09-19  3:24     ` Josh Cartwright
2014-09-19  3:41       ` Guenter Roeck
2014-09-19 16:25         ` Josh Cartwright
2014-09-19 16:56           ` Guenter Roeck
2014-09-18 22:27 ` [PATCH 2/3] watchdog: qcom: document device tree bindings Josh Cartwright
2014-09-18 22:27 ` [PATCH 3/3] watchdog: qcom: register a restart notifier Josh Cartwright
2014-09-19  2:47   ` Guenter Roeck
2014-09-19  3:32     ` Josh Cartwright [this message]
2014-09-19  4:03       ` Guenter Roeck
2014-09-19 16:29         ` Josh Cartwright
2014-09-19 12:47   ` 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=20140919033202.GF3749@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).