All of lore.kernel.org
 help / color / mirror / Atom feed
From: Christoph Niedermaier <cniedermaier@dh-electronics.com>
To: Andrej Picej <andrej.picej@norik.com>,
	"support.opensource@diasemi.com" <support.opensource@diasemi.com>,
	"linux@roeck-us.net" <linux@roeck-us.net>,
	"linux-watchdog@vger.kernel.org" <linux-watchdog@vger.kernel.org>
Cc: "wim@linux-watchdog.org" <wim@linux-watchdog.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"robh+dt@kernel.org" <robh+dt@kernel.org>,
	"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
	"shawnguo@kernel.org" <shawnguo@kernel.org>,
	"s.hauer@pengutronix.de" <s.hauer@pengutronix.de>,
	"kernel@pengutronix.de" <kernel@pengutronix.de>,
	"festevam@gmail.com" <festevam@gmail.com>,
	"linux-imx@nxp.com" <linux-imx@nxp.com>,
	"linux-arm-kernel@lists.infradead.org"
	<linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH v3 2/4] watchdog: da9062: reset board on watchdog timeout
Date: Wed, 1 Dec 2021 14:11:51 +0000	[thread overview]
Message-ID: <13e0b9047f114722a0b4ebb4c1d24f2b@dh-electronics.com> (raw)
In-Reply-To: <20211201081512.3580837-2-andrej.picej@norik.com>

From: Andrej Picej
Sent: Wednesday, December 1, 2021 9:15 AM
> Implement a method to change watchdog timeout configuration based on DT
> binding ("dlg,wdt-sd"). There is a possibility to change the bahaviour
> of watchdog reset. Setting WATCHDOG_SD bit enables SHUTDOWN mode, and
> clearing it enables POWERDOWN mode on watchdog timeout.
> 
> If no DT binding is specified the WATCHDOG_SD bit stays in default
> configuration, not breaking behaviour of devices which might depend on
> default fuse configuration.
> 
> Note: This patch requires that the config register CONFIG_I is
> configured as writable in the da9062 multi function device.
> 
> Signed-off-by: Andrej Picej <andrej.picej@norik.com>
> ---
> Changes in v3:
>  - no changes
> 
> Changes in v2:
>  - don't force the "reset" for all da9062-watchdog users, instead add DT
>    binding where the behavior can be selected
> ---
>  drivers/watchdog/da9062_wdt.c | 25 +++++++++++++++++++++++++
>  1 file changed, 25 insertions(+)
> 
> diff --git a/drivers/watchdog/da9062_wdt.c b/drivers/watchdog/da9062_wdt.c
> index f02cbd530538..e342e9e50cb1 100644
> --- a/drivers/watchdog/da9062_wdt.c
> +++ b/drivers/watchdog/da9062_wdt.c
> @@ -85,8 +85,33 @@ static int da9062_wdt_start(struct watchdog_device *wdd)
>  {
>         struct da9062_watchdog *wdt = watchdog_get_drvdata(wdd);
>         unsigned int selector;
> +       unsigned int mask;
> +       u32 val;
>         int ret;
> 
> +       /* Configure what happens on watchdog timeout. Can be specified with
> +        * "dlg,wdt-sd" dt-binding (0 -> POWERDOWN, 1 -> SHUTDOWN).
> +        * If "dlg,wdt-sd" dt-binding is NOT set use the default.
> +        */
> +       ret = device_property_read_u32(wdd->parent, "dlg,wdt-sd", &val);
> +       if (!ret) {
> +               if (val)
> +                       /* Use da9062's SHUTDOWN mode */
> +                       mask = DA9062AA_WATCHDOG_SD_MASK;
> +               else
> +                       /* Use da9062's POWERDOWN mode. */
> +                       mask = 0x0;
> +
> +               ret = regmap_update_bits(wdt->hw->regmap,
> +                                               DA9062AA_CONFIG_I,
> +                                               DA9062AA_WATCHDOG_SD_MASK,
> +                                               mask);
> +
> +               if (ret)
> +                       dev_err(wdt->hw->dev, "failed to set wdt reset mode:
> %d\n",
> +                               ret);
> +       }
> +
>         selector = da9062_wdt_timeout_to_sel(wdt->wdtdev.timeout);
>         ret = da9062_wdt_update_timeout_register(wdt, selector);
>         if (ret)
> --
> 2.25.1
>

I have a question how to correctly restart the system after
watchdog timeout.
If I understand it correct after watchdog timeout the system
restarts only if WATCHDOG_SD (Bit 3) in register CONFIG_I is
set.
What is the difference if WATCHDOG_SD isn't set, but WAKE_UP
(Bit 2) in register CONTROL_F is set? From outside on my
system I observe the same behavior. After watchdog timeout
my system restarts. So where are the differences?
It would be nice if you could answer this question, as you
certainly know this chip very well.

Regards
Christoph
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

  reply	other threads:[~2021-12-01 14:15 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-01  8:15 [PATCH v3 1/4] mfd: da9062: make register CONFIG_I writable Andrej Picej
2021-12-01  8:15 ` Andrej Picej
2021-12-01  8:15 ` [PATCH v3 2/4] watchdog: da9062: reset board on watchdog timeout Andrej Picej
2021-12-01  8:15   ` Andrej Picej
2021-12-01 14:11   ` Christoph Niedermaier [this message]
2021-12-02  7:43     ` Andrej Picej
2021-12-02  7:43       ` Andrej Picej
2021-12-02 12:12       ` Adam Thomson
2021-12-02 12:12         ` Adam Thomson
2021-12-02 15:46         ` Christoph Niedermaier
2021-12-02 15:37       ` Christoph Niedermaier
2021-12-01 20:05   ` Adam Thomson
2021-12-01 20:05     ` Adam Thomson
2021-12-02  8:31     ` Andrej Picej
2021-12-02  8:31       ` Andrej Picej
2021-12-01 21:26   ` Guenter Roeck
2021-12-01 21:26     ` Guenter Roeck
2021-12-02  8:34     ` Andrej Picej
2021-12-02  8:34       ` Andrej Picej
2021-12-01  8:15 ` [PATCH v3 3/4] dt-bindings: watchdog: da9062: add watchdog timeout mode Andrej Picej
2021-12-01  8:15   ` Andrej Picej
2021-12-01  8:15 ` [PATCH v3 4/4] ARM: dts: imx6: phycore-som: set watchdog timeout mode to shutdown Andrej Picej
2021-12-01  8:15   ` Andrej Picej

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=13e0b9047f114722a0b4ebb4c1d24f2b@dh-electronics.com \
    --to=cniedermaier@dh-electronics.com \
    --cc=andrej.picej@norik.com \
    --cc=devicetree@vger.kernel.org \
    --cc=festevam@gmail.com \
    --cc=kernel@pengutronix.de \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-imx@nxp.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-watchdog@vger.kernel.org \
    --cc=linux@roeck-us.net \
    --cc=robh+dt@kernel.org \
    --cc=s.hauer@pengutronix.de \
    --cc=shawnguo@kernel.org \
    --cc=support.opensource@diasemi.com \
    --cc=wim@linux-watchdog.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.