From: Guenter Roeck <linux@roeck-us.net>
To: Primoz Fiser <primoz.fiser@norik.com>,
linux-watchdog@vger.kernel.org,
Wim Van Sebroeck <wim@linux-watchdog.org>,
Support Opensource <support.opensource@diasemi.com>
Cc: Tero Kristo <t-kristo@ti.com>,
Stefan Riedmueller <s.riedmueller@phytec.de>,
Wolfram Sang <wsa+renesas@sang-engineering.com>
Subject: Re: [PATCH] watchdog: da9062: da9063: prevent watchdog pings ahead of reboot
Date: Tue, 6 Jul 2021 06:28:16 -0700 [thread overview]
Message-ID: <4fc1998d-ed3b-6934-9d05-62ac68659744@roeck-us.net> (raw)
In-Reply-To: <20210706112103.1687587-1-primoz.fiser@norik.com>
On 7/6/21 4:21 AM, Primoz Fiser wrote:
> Proper machine resets via da9062/da9063 PMICs are very tricky as they
> require special i2c atomic transfers when interrupts are not available
> anymore. This is also a reason why both PMIC's restart handlers do not
> use regmap but instead opt for i2c_smbus_write_byte_data() which does
> i2c transfer in atomic manner. Under the hood, this function tries to
> obtain i2c bus lock with call to i2c_adapter_trylock_bus() which will
> return -EAGAIN (-11) if lock is not available.
>
> Since commit 982bb70517aef ("watchdog: reset last_hw_keepalive time at
> start") occasional restart handler failures with "Failed to shutdown
> (err = -11)" error messages were observed, indicating that some
> process is holding the i2c bus lock. Investigation into the matter
> uncovered that sometimes during reboot sequence watchdog ping is issued
> late into reboot phase which didn't happen before mentioned commit
> (usually watchdog ping happened immediately as commit message suggests).
> As of now, when watchdog ping usually happens late into reboot stage
> when interrupts are not available anymore, i2c bus lock cannot be
> released anymore and pending restart handler in turn fails.
>
> Thus, to prevent such late watchdog pings from happening ahead of
> pending machine restart and consequently locking up the i2c bus, install
> a reboot notifier callback in both PMIC's watchdog drivers. When reboot
> notifier is called, it will raise the restart_pending flag signaling to
> the watchdog ping handler to not send pings anymore.
>
> Signed-off-by: Primoz Fiser <primoz.fiser@norik.com>
> ---
> drivers/watchdog/da9062_wdt.c | 26 ++++++++++++++++++++++++++
> drivers/watchdog/da9063_wdt.c | 22 ++++++++++++++++++++++
> include/linux/mfd/da9063/core.h | 3 +++
> 3 files changed, 51 insertions(+)
>
> diff --git a/drivers/watchdog/da9062_wdt.c b/drivers/watchdog/da9062_wdt.c
> index 706fb09c2f24..ebb45d445d87 100644
> --- a/drivers/watchdog/da9062_wdt.c
> +++ b/drivers/watchdog/da9062_wdt.c
> @@ -19,6 +19,7 @@
> #include <linux/property.h>
> #include <linux/regmap.h>
> #include <linux/of.h>
> +#include <linux/reboot.h>
>
> static const unsigned int wdt_timeout[] = { 0, 2, 4, 8, 16, 32, 65, 131 };
> #define DA9062_TWDSCALE_DISABLE 0
> @@ -33,6 +34,9 @@ struct da9062_watchdog {
> struct da9062 *hw;
> struct watchdog_device wdtdev;
> bool use_sw_pm;
> +
> + struct notifier_block reboot_nb;
> + bool restart_pending;
> };
>
> static unsigned int da9062_wdt_read_timeout(struct da9062_watchdog *wdt)
> @@ -117,6 +121,9 @@ static int da9062_wdt_ping(struct watchdog_device *wdd)
> struct da9062_watchdog *wdt = watchdog_get_drvdata(wdd);
> int ret;
>
> + if (wdt->restart_pending)
> + return 0;
> +
> ret = da9062_reset_watchdog_timer(wdt);
> if (ret)
> dev_err(wdt->hw->dev, "Failed to ping the watchdog (err = %d)\n",
> @@ -143,6 +150,22 @@ static int da9062_wdt_set_timeout(struct watchdog_device *wdd,
> return ret;
> }
>
> +static int da9062_wdt_reboot_notifier(struct notifier_block *nb,
> + unsigned long code, void *unused)
> +{
> + struct da9062_watchdog *wdt =
> + container_of(nb, struct da9062_watchdog, reboot_nb);
> +
> + /*
> + * Use reboot notifer to raise flag and in turn prevent watchdog pings
> + * from occurring late in system reboot sequence and possibly locking
> + * out restart handler from accessing i2c bus.
> + */
> + wdt->restart_pending = true;
> +
> + return NOTIFY_DONE;
> +}
> +
> static int da9062_wdt_restart(struct watchdog_device *wdd, unsigned long action,
> void *data)
> {
> @@ -229,6 +252,9 @@ static int da9062_wdt_probe(struct platform_device *pdev)
> set_bit(WDOG_HW_RUNNING, &wdt->wdtdev.status);
> }
>
> + wdt->reboot_nb.notifier_call = da9062_wdt_reboot_notifier;
> + devm_register_reboot_notifier(dev, &wdt->reboot_nb);
> +
> return devm_watchdog_register_device(dev, &wdt->wdtdev);
> }
>
> diff --git a/drivers/watchdog/da9063_wdt.c b/drivers/watchdog/da9063_wdt.c
> index 423584252606..bea2ba62dff2 100644
> --- a/drivers/watchdog/da9063_wdt.c
> +++ b/drivers/watchdog/da9063_wdt.c
> @@ -18,6 +18,7 @@
> #include <linux/mfd/da9063/registers.h>
> #include <linux/mfd/da9063/core.h>
> #include <linux/regmap.h>
> +#include <linux/reboot.h>
>
> /*
> * Watchdog selector to timeout in seconds.
> @@ -121,6 +122,9 @@ static int da9063_wdt_ping(struct watchdog_device *wdd)
> struct da9063 *da9063 = watchdog_get_drvdata(wdd);
> int ret;
>
> + if (da9063->restart_pending)
> + return 0;
> +
Why all that complexity and not just check system_state here ?
Guenter
> ret = regmap_write(da9063->regmap, DA9063_REG_CONTROL_F,
> DA9063_WATCHDOG);
> if (ret)
> @@ -158,6 +162,21 @@ static int da9063_wdt_set_timeout(struct watchdog_device *wdd,
> return ret;
> }
>
> +static int da9063_wdt_reboot_notifier(struct notifier_block *nb,
> + unsigned long code, void *unused)
> +{
> + struct da9063 *da9063 = container_of(nb, struct da9063, reboot_nb);
> +
> + /*
> + * Use reboot notifer to raise flag and in turn prevent watchdog pings
> + * from occurring late in system reboot sequence and possibly locking
> + * out restart handler from accessing i2c bus.
> + */
> + da9063->restart_pending = true;
> +
> + return NOTIFY_DONE;
> +}
> +
> static int da9063_wdt_restart(struct watchdog_device *wdd, unsigned long action,
> void *data)
> {
> @@ -233,6 +252,9 @@ static int da9063_wdt_probe(struct platform_device *pdev)
> set_bit(WDOG_HW_RUNNING, &wdd->status);
> }
>
> + da9063->reboot_nb.notifier_call = da9063_wdt_reboot_notifier;
> + devm_register_reboot_notifier(dev, &da9063->reboot_nb);
> +
> return devm_watchdog_register_device(dev, wdd);
> }
>
> diff --git a/include/linux/mfd/da9063/core.h b/include/linux/mfd/da9063/core.h
> index fa7a43f02f27..6be39fd9300d 100644
> --- a/include/linux/mfd/da9063/core.h
> +++ b/include/linux/mfd/da9063/core.h
> @@ -85,6 +85,9 @@ struct da9063 {
> int chip_irq;
> unsigned int irq_base;
> struct regmap_irq_chip_data *regmap_irq;
> +
> + struct notifier_block reboot_nb;
> + bool restart_pending;
> };
>
> int da9063_device_init(struct da9063 *da9063, unsigned int irq);
>
next prev parent reply other threads:[~2021-07-06 13:28 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-06 11:21 [PATCH] watchdog: da9062: da9063: prevent watchdog pings ahead of reboot Primoz Fiser
2021-07-06 13:28 ` Guenter Roeck [this message]
2021-07-07 4:39 ` Primoz Fiser
2021-07-08 8:21 ` [PATCH v2] watchdog: da9062: da9063: prevent pings ahead of machine reset Primoz Fiser
2021-07-08 14:00 ` Guenter Roeck
2021-07-08 14:15 ` Adam Thomson
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=4fc1998d-ed3b-6934-9d05-62ac68659744@roeck-us.net \
--to=linux@roeck-us.net \
--cc=linux-watchdog@vger.kernel.org \
--cc=primoz.fiser@norik.com \
--cc=s.riedmueller@phytec.de \
--cc=support.opensource@diasemi.com \
--cc=t-kristo@ti.com \
--cc=wim@linux-watchdog.org \
--cc=wsa+renesas@sang-engineering.com \
/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).