From: Guenter Roeck <linux@roeck-us.net>
To: Jayachandran C <jnair@caviumnetworks.com>,
Wim Van Sebroeck <wim@linux-watchdog.org>,
linux-watchdog@vger.kernel.org
Cc: Fu Wei <fu.wei@linaro.org>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] watchdog: sbsa: use 32-bit read for WCV
Date: Wed, 28 Feb 2018 06:35:42 -0800 [thread overview]
Message-ID: <265c171f-8a08-2799-53b5-c6e3a5bf44b5@roeck-us.net> (raw)
In-Reply-To: <1519815140-5336-1-git-send-email-jnair@caviumnetworks.com>
On 02/28/2018 02:52 AM, Jayachandran C wrote:
> According to SBSA spec v3.1 section 5.3:
> All registers are 32 bits in size and should be accessed using
> 32-bit reads and writes. If an access size other than 32 bits
> is used then the results are IMPLEMENTATION DEFINED.
> [...]
> The Generic Watchdog is little-endian
>
> The current code uses readq to read the watchdog compare register
> which does a 64-bit access. This fails on ThunderX2 which does not
> implement 64-bit access to this register.
>
> Fix this by using lo_hi_readq() that does two 32-bit reads.
>
> Signed-off-by: Jayachandran C <jnair@caviumnetworks.com>
Reviewed-by: Guenter Roeck <linux@roeck-us.net>
> ---
> drivers/watchdog/sbsa_gwdt.c | 3 ++-
> 1 file changed, 2 insertions(+), 1 deletion(-)
>
> diff --git a/drivers/watchdog/sbsa_gwdt.c b/drivers/watchdog/sbsa_gwdt.c
> index 316c2eb..e8bd988 100644
> --- a/drivers/watchdog/sbsa_gwdt.c
> +++ b/drivers/watchdog/sbsa_gwdt.c
> @@ -50,6 +50,7 @@
> */
>
> #include <linux/io.h>
> +#include <linux/io-64-nonatomic-lo-hi.h>
> #include <linux/interrupt.h>
> #include <linux/module.h>
> #include <linux/moduleparam.h>
> @@ -159,7 +160,7 @@ static unsigned int sbsa_gwdt_get_timeleft(struct watchdog_device *wdd)
> !(readl(gwdt->control_base + SBSA_GWDT_WCS) & SBSA_GWDT_WCS_WS0))
> timeleft += readl(gwdt->control_base + SBSA_GWDT_WOR);
>
> - timeleft += readq(gwdt->control_base + SBSA_GWDT_WCV) -
> + timeleft += lo_hi_readq(gwdt->control_base + SBSA_GWDT_WCV) -
> arch_counter_get_cntvct();
>
> do_div(timeleft, gwdt->clk);
>
next prev parent reply other threads:[~2018-02-28 14:35 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-28 10:52 Jayachandran C
2018-02-28 14:35 ` Guenter Roeck [this message]
2018-03-07 10:04 ` Robert Richter
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=265c171f-8a08-2799-53b5-c6e3a5bf44b5@roeck-us.net \
--to=linux@roeck-us.net \
--cc=fu.wei@linaro.org \
--cc=jnair@caviumnetworks.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-watchdog@vger.kernel.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®