Linux Watchdog driver development
 help / color / mirror / Atom feed
From: Guenter Roeck <linux@roeck-us.net>
To: Cor Peters <cpeters@victronenergy.com>, linux-omap@vger.kernel.org
Cc: linux-watchdog@vger.kernel.org
Subject: Re: [PATCH 1/2] Watchdog: omap_wdt: Retrieve bootstatus via syscon
Date: Tue, 15 Nov 2016 06:09:16 -0800	[thread overview]
Message-ID: <bb5ceb32-80a7-2caa-ea70-26a24100b769@roeck-us.net> (raw)
In-Reply-To: <2736782.ivGPcGWbll@corpeters>

On 11/15/2016 12:44 AM, Cor Peters wrote:
> The current way to retrieve the bootstatus does not work with
> device-tree based systems. This patch uses syscon to retrieve the
> watchdog boot status from the PRM_DEV registers.
>
> Signed-off-by: Cor Peters <cpeters@victronenergy.com>

For the subject: Patch 2/2 seems to be missing (or I wasn't copied).

> ---
>  drivers/watchdog/omap_wdt.c | 16 ++++++++++++++--
>  1 file changed, 14 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/watchdog/omap_wdt.c b/drivers/watchdog/omap_wdt.c
> index 1b02bfa..fed3f9c 100644
> --- a/drivers/watchdog/omap_wdt.c
> +++ b/drivers/watchdog/omap_wdt.c
> @@ -41,6 +41,8 @@
>  #include <linux/slab.h>
>  #include <linux/pm_runtime.h>
>  #include <linux/platform_data/omap-wd-timer.h>
> +#include <linux/regmap.h>
> +#include <linux/mfd/syscon.h>
>
>  #include "omap_wdt.h"
>
> @@ -230,9 +232,11 @@ static unsigned int omap_wdt_get_timeleft(struct watchdog_device *wdog)
>  static int omap_wdt_probe(struct platform_device *pdev)
>  {
>         struct omap_wd_timer_platform_data *pdata = dev_get_platdata(&pdev->dev);
> +       struct regmap *rm = syscon_regmap_lookup_by_compatible("ti,omap3-prcm-dev");
>         struct resource *res;
>         struct omap_wdt_dev *wdev;
>         int ret;
> +       u32 rs = 0;
>
>         wdev = devm_kzalloc(&pdev->dev, sizeof(*wdev), GFP_KERNEL);
>         if (!wdev)
> @@ -267,9 +271,17 @@ static int omap_wdt_probe(struct platform_device *pdev)
>
>         if (pdata && pdata->read_reset_sources) {
>                 u32 rs = pdata->read_reset_sources();

You are still declaring rs here, meaning the new instance of rs is hidden.

> -               if (rs & (1 << OMAP_MPU_WD_RST_SRC_ID_SHIFT))
> -                       wdev->wdog.bootstatus = WDIOF_CARDRESET;
>         }
> +       else if (!IS_ERR(rm)) {
> +               if (regmap_read(rm, 2 * sizeof(u32), &rs) >= 0) {

Can you use a define instead of "2 * sizeof(u32)" here ? If the register is 0x0008
it should be defined as 0x0008; the register address does not depend on the size
of an u32.

> +                       /* reset register */
> +                       regmap_write(rm, 2 * sizeof(u32),
> +                               (1 << OMAP_MPU_WD_RST_SRC_ID_SHIFT) );

extra space between '')'.

Why reset this register ? That isn't done for the non-DT case.

Also, unless I misunderstand the code, OMAP_MPU_WD_RST_SRC_ID_SHIFT is a
standardized "soft" value and does not reflect the physical reset bit in
the SoC. I don't think you can just use that value and assume that it
is the correct register bit to use.

Guenter


      reply	other threads:[~2016-11-15 14:09 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-15  8:44 [PATCH 1/2] Watchdog: omap_wdt: Retrieve bootstatus via syscon Cor Peters
2016-11-15 14:09 ` Guenter Roeck [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=bb5ceb32-80a7-2caa-ea70-26a24100b769@roeck-us.net \
    --to=linux@roeck-us.net \
    --cc=cpeters@victronenergy.com \
    --cc=linux-omap@vger.kernel.org \
    --cc=linux-watchdog@vger.kernel.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