public inbox for linux-arm-kernel@lists.infradead.org
 help / color / mirror / Atom feed
From: andrew@lunn.ch (Andrew Lunn)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 2/2] Watchdog: fix clearing of the watchdog interrupt
Date: Tue, 18 Jun 2013 19:14:52 +0200	[thread overview]
Message-ID: <20130618171452.GB31360@lunn.ch> (raw)
In-Reply-To: <E1Uoye0-0001Cw-Po@rmk-PC.arm.linux.org.uk>

On Tue, Jun 18, 2013 at 05:20:32PM +0100, Russell King wrote:
> The bits in BRIDGE_CAUSE are documented as RW0C - read, write 0 to
> clear.  If we read the register, mask off the watchdog bit, and
> write it back, we're actually clearing every interrupt which wasn't
> pending at the time we read the register - and that is racy.
> 
> Fix this to only write ~WATCHDOG_BIT to the register, which means
> we write as zero only the watchdog bit.
> 
> Signed-off-by: Russell King <rmk+kernel@arm.linux.org.uk>
> ---
>  drivers/watchdog/orion_wdt.c |    4 +---
>  1 files changed, 1 insertions(+), 3 deletions(-)
> 
> diff --git a/drivers/watchdog/orion_wdt.c b/drivers/watchdog/orion_wdt.c
> index 4074244..4ea5fcc 100644
> --- a/drivers/watchdog/orion_wdt.c
> +++ b/drivers/watchdog/orion_wdt.c
> @@ -70,9 +70,7 @@ static int orion_wdt_start(struct watchdog_device *wdt_dev)
>  	writel(wdt_tclk * wdt_dev->timeout, wdt_reg + WDT_VAL);
>  
>  	/* Clear watchdog timer interrupt */
> -	reg = readl(BRIDGE_CAUSE);
> -	reg &= ~WDT_INT_REQ;
> -	writel(reg, BRIDGE_CAUSE);
> +	writel(~WDT_INT_REQ, BRIDGE_CAUSE);
>  
>  	/* Enable watchdog timer */
>  	reg = readl(wdt_reg + TIMER_CTRL);
> -- 
> 1.7.4.4


Hi Russell

For this, and patch 1/2:

Tested-by: Andrew Lunn <andrew@lunn.ch>

On a kirkwood.

   Andrew

      parent reply	other threads:[~2013-06-18 17:14 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-18 16:20 [PATCH 2/2] Watchdog: fix clearing of the watchdog interrupt Russell King
2013-06-18 16:32 ` Jason Cooper
2013-06-18 17:14 ` Andrew Lunn [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=20130618171452.GB31360@lunn.ch \
    --to=andrew@lunn.ch \
    --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