* [PATCH v8 3/3] watchdog: zx2967: add watchdog controller driver for ZTE's zx2967 family
@ 2017-02-03 16:02 ` Mathieu Poirier
0 siblings, 0 replies; 19+ messages in thread
From: Mathieu Poirier @ 2017-02-03 16:02 UTC (permalink / raw)
To: linux-arm-kernel
On Fri, Feb 03, 2017 at 11:22:20AM +0800, Baoyou Xie wrote:
> This patch adds watchdog controller driver for ZTE's zx2967 family.
>
> Signed-off-by: Baoyou Xie <baoyou.xie@linaro.org>
> ---
> drivers/watchdog/Kconfig | 10 ++
> drivers/watchdog/Makefile | 1 +
> drivers/watchdog/zx2967_wdt.c | 285 ++++++++++++++++++++++++++++++++++++++++++
> 3 files changed, 296 insertions(+)
> create mode 100644 drivers/watchdog/zx2967_wdt.c
>
> diff --git a/drivers/watchdog/Kconfig b/drivers/watchdog/Kconfig
> index acb00b5..05093a2 100644
> --- a/drivers/watchdog/Kconfig
> +++ b/drivers/watchdog/Kconfig
> @@ -714,6 +714,16 @@ config ASPEED_WATCHDOG
> To compile this driver as a module, choose M here: the
> module will be called aspeed_wdt.
>
> +config ZX2967_WATCHDOG
> + tristate "ZTE zx2967 SoCs watchdog support"
> + depends on ARCH_ZX
> + select WATCHDOG_CORE
> + help
> + Say Y here to include support for the watchdog timer
> + in ZTE zx2967 SoCs.
> + To compile this driver as a module, choose M here: the
> + module will be called zx2967_wdt.
> +
> # AVR32 Architecture
>
> config AT32AP700X_WDT
> diff --git a/drivers/watchdog/Makefile b/drivers/watchdog/Makefile
> index 0c3d35e..bf2d296 100644
> --- a/drivers/watchdog/Makefile
> +++ b/drivers/watchdog/Makefile
> @@ -82,6 +82,7 @@ obj-$(CONFIG_BCM7038_WDT) += bcm7038_wdt.o
> obj-$(CONFIG_ATLAS7_WATCHDOG) += atlas7_wdt.o
> obj-$(CONFIG_RENESAS_WDT) += renesas_wdt.o
> obj-$(CONFIG_ASPEED_WATCHDOG) += aspeed_wdt.o
> +obj-$(CONFIG_ZX2967_WATCHDOG) += zx2967_wdt.o
>
> # AVR32 Architecture
> obj-$(CONFIG_AT32AP700X_WDT) += at32ap700x_wdt.o
> diff --git a/drivers/watchdog/zx2967_wdt.c b/drivers/watchdog/zx2967_wdt.c
> new file mode 100644
> index 0000000..2daaca2
> --- /dev/null
> +++ b/drivers/watchdog/zx2967_wdt.c
> @@ -0,0 +1,285 @@
> +/*
> + * watchdog driver for ZTE's zx2967 family
> + *
> + * Copyright (C) 2017 ZTE Ltd.
> + *
> + * Author: Baoyou Xie <baoyou.xie@linaro.org>
> + *
> + * License terms: GNU General Public License (GPL) version 2
> + */
> +
> +#include <linux/clk.h>
> +#include <linux/io.h>
> +#include <linux/mfd/syscon.h>
> +#include <linux/module.h>
> +#include <linux/of_address.h>
> +#include <linux/platform_device.h>
> +#include <linux/regmap.h>
> +#include <linux/reset.h>
> +#include <linux/watchdog.h>
> +
> +#define ZX2967_WDT_CFG_REG 0x4
> +#define ZX2967_WDT_LOAD_REG 0x8
> +#define ZX2967_WDT_REFRESH_REG 0x18
> +#define ZX2967_WDT_START_REG 0x1c
> +
> +#define ZX2967_WDT_REFRESH_MASK 0x3f
> +
> +#define ZX2967_WDT_CFG_DIV(n) ((((n) & 0xff) - 1) << 8)
> +#define ZX2967_WDT_START_EN 0x1
> +
> +/*
> + * Hardware magic number.
> + * When watchdog reg is written, the lowest 16 bits are valid, but
> + * the highest 16 bits should be always this number.
> + */
Thanks for the explanation, much better now.
> +#define ZX2967_WDT_WRITEKEY (0x1234 << 16)
> +
> +#define ZX2967_WDT_DIV_DEFAULT 16
> +#define ZX2967_WDT_DEFAULT_TIMEOUT 32
> +#define ZX2967_WDT_MIN_TIMEOUT 1
> +#define ZX2967_WDT_MAX_TIMEOUT 524
> +#define ZX2967_WDT_MAX_COUNT 0xffff
> +
> +#define ZX2967_WDT_CLK_FREQ 0x8000
> +
> +#define ZX2967_WDT_FLAG_REBOOT_MON BIT(0)
> +
> +struct zx2967_wdt {
> + struct watchdog_device wdt_device;
> + void __iomem *reg_base;
> + struct clk *clock;
> +};
> +
> +static inline u32 zx2967_wdt_readl(struct zx2967_wdt *wdt, u16 reg)
> +{
> + return readl_relaxed(wdt->reg_base + reg);
> +}
> +
> +static inline void zx2967_wdt_writel(struct zx2967_wdt *wdt, u16 reg, u16 val)
> +{
> + writel_relaxed(val | ZX2967_WDT_WRITEKEY, wdt->reg_base + reg);
> +}
You were correct with the u32 type. My comment was about making sure the value
of the value given to the function wasn't bigger than 65535 (0xffff), which
would have been corrupted by the OR'ing with ZX2967_WDT_WRITEKEY.
Going with a u16 forces you to manipulate u16 types in all the functions below
but the read operation is still a u32, leaving to the compiler the task of
stripping the top 16 bit.
My suggestion is to go back to a u32 for zx2967_wdt_writel() but to AND 'val'
with 0x0000ffff before OR'ing it with ZX2967_WDT_WRITEKEY.
> +
> +static void zx2967_wdt_refresh(struct zx2967_wdt *wdt)
> +{
> + u16 val;
> +
> + val = zx2967_wdt_readl(wdt, ZX2967_WDT_REFRESH_REG);
> + /*
> + * Bit 4-5, 1 and 2: refresh config info
> + * Bit 2-3, 1 and 2: refresh counter
> + * Bit 0-1, 1 and 2: refresh int-value
> + * we shift each group value between 1 and 2 to refresh all data.
> + */
> + val ^= ZX2967_WDT_REFRESH_MASK;
> + zx2967_wdt_writel(wdt, ZX2967_WDT_REFRESH_REG, val);
> +}
> +
> +static int
> +zx2967_wdt_set_timeout(struct watchdog_device *wdd, unsigned int timeout)
> +{
> + struct zx2967_wdt *wdt = watchdog_get_drvdata(wdd);
> + unsigned int divisor = ZX2967_WDT_DIV_DEFAULT;
> + u32 count;
> +
> + count = timeout * ZX2967_WDT_CLK_FREQ;
> + if (count > divisor * ZX2967_WDT_MAX_COUNT)
> + divisor = DIV_ROUND_UP(count, ZX2967_WDT_MAX_COUNT);
> + count = DIV_ROUND_UP(count, divisor);
> + zx2967_wdt_writel(wdt, ZX2967_WDT_CFG_REG, ZX2967_WDT_CFG_DIV(divisor));
> + zx2967_wdt_writel(wdt, ZX2967_WDT_LOAD_REG, count);
> + zx2967_wdt_refresh(wdt);
> + wdd->timeout = (count * divisor) / ZX2967_WDT_CLK_FREQ;
> +
> + return 0;
> +}
> +
> +static void __zx2967_wdt_start(struct zx2967_wdt *wdt)
> +{
> + u16 val;
> +
> + val = zx2967_wdt_readl(wdt, ZX2967_WDT_START_REG);
> + val |= ZX2967_WDT_START_EN;
> + zx2967_wdt_writel(wdt, ZX2967_WDT_START_REG, val);
> +}
> +
> +static void __zx2967_wdt_stop(struct zx2967_wdt *wdt)
> +{
> + u16 val;
> +
> + val = zx2967_wdt_readl(wdt, ZX2967_WDT_START_REG);
> + val &= ~ZX2967_WDT_START_EN;
> + zx2967_wdt_writel(wdt, ZX2967_WDT_START_REG, val);
> +}
> +
> +static int zx2967_wdt_start(struct watchdog_device *wdd)
> +{
> + struct zx2967_wdt *wdt = watchdog_get_drvdata(wdd);
> +
> + zx2967_wdt_set_timeout(wdd, wdd->timeout);
> + __zx2967_wdt_start(wdt);
> +
> + return 0;
> +}
> +
> +static int zx2967_wdt_stop(struct watchdog_device *wdd)
> +{
> + struct zx2967_wdt *wdt = watchdog_get_drvdata(wdd);
> +
> + __zx2967_wdt_stop(wdt);
> +
> + return 0;
> +}
> +
> +static int zx2967_wdt_keepalive(struct watchdog_device *wdd)
> +{
> + struct zx2967_wdt *wdt = watchdog_get_drvdata(wdd);
> +
> + zx2967_wdt_refresh(wdt);
> +
> + return 0;
> +}
> +
> +#define ZX2967_WDT_OPTIONS \
> + (WDIOF_SETTIMEOUT | WDIOF_KEEPALIVEPING | WDIOF_MAGICCLOSE)
> +static const struct watchdog_info zx2967_wdt_ident = {
> + .options = ZX2967_WDT_OPTIONS,
> + .identity = "zx2967 watchdog",
> +};
> +
> +static struct watchdog_ops zx2967_wdt_ops = {
> + .owner = THIS_MODULE,
> + .start = zx2967_wdt_start,
> + .stop = zx2967_wdt_stop,
> + .ping = zx2967_wdt_keepalive,
> + .set_timeout = zx2967_wdt_set_timeout,
> +};
> +
> +static void zx2967_wdt_reset_sysctrl(struct device *dev)
> +{
> + int ret;
> + void __iomem *regmap;
> + unsigned int offset, mask, config;
> + struct of_phandle_args out_args;
> +
> + ret = of_parse_phandle_with_fixed_args(dev->of_node,
> + "zte,wdt-reset-sysctrl", 3, 0, &out_args);
> + if (ret)
> + return;
> +
> + offset = out_args.args[0];
> + config = out_args.args[1];
> + mask = out_args.args[2];
> +
> + regmap = syscon_node_to_regmap(out_args.np);
> + if (IS_ERR(regmap)) {
> + of_node_put(out_args.np);
> + return;
> + }
> +
> + regmap_update_bits(regmap, offset, mask, config);
> + of_node_put(out_args.np);
> +}
> +
> +static int zx2967_wdt_probe(struct platform_device *pdev)
> +{
> + struct device *dev = &pdev->dev;
> + struct zx2967_wdt *wdt;
> + struct resource *base;
> + int ret;
> + struct reset_control *rstc;
> +
> + wdt = devm_kzalloc(dev, sizeof(*wdt), GFP_KERNEL);
> + if (!wdt)
> + return -ENOMEM;
> +
> + platform_set_drvdata(pdev, wdt);
> +
> + wdt->wdt_device.info = &zx2967_wdt_ident;
> + wdt->wdt_device.ops = &zx2967_wdt_ops;
> + wdt->wdt_device.timeout = ZX2967_WDT_DEFAULT_TIMEOUT;
> + wdt->wdt_device.max_timeout = ZX2967_WDT_MAX_TIMEOUT;
> + wdt->wdt_device.min_timeout = ZX2967_WDT_MIN_TIMEOUT;
> + wdt->wdt_device.parent = &pdev->dev;
> +
> + base = platform_get_resource(pdev, IORESOURCE_MEM, 0);
> + wdt->reg_base = devm_ioremap_resource(dev, base);
> + if (IS_ERR(wdt->reg_base)) {
> + dev_err(dev, "ioremap failed\n");
> + return PTR_ERR(wdt->reg_base);
> + }
> +
> + zx2967_wdt_reset_sysctrl(dev);
> +
> + wdt->clock = devm_clk_get(dev, NULL);
> + if (IS_ERR(wdt->clock)) {
> + dev_err(dev, "failed to find watchdog clock source\n");
> + return PTR_ERR(wdt->clock);
> + }
> +
> + ret = clk_prepare_enable(wdt->clock);
> + if (ret < 0) {
> + dev_err(dev, "failed to enable clock\n");
> + return ret;
> + }
> + clk_set_rate(wdt->clock, ZX2967_WDT_CLK_FREQ);
> +
> + rstc = devm_reset_control_get(dev, NULL);
> + if (IS_ERR(rstc)) {
> + dev_err(dev, "failed to get rstc");
> + ret = PTR_ERR(rstc);
> + goto err;
> + }
> +
> + reset_control_assert(rstc);
> + reset_control_deassert(rstc);
> +
> + watchdog_set_drvdata(&wdt->wdt_device, wdt);
> + watchdog_init_timeout(&wdt->wdt_device,
> + ZX2967_WDT_DEFAULT_TIMEOUT, dev);
> + watchdog_set_nowayout(&wdt->wdt_device, WATCHDOG_NOWAYOUT);
> +
> + ret = watchdog_register_device(&wdt->wdt_device);
> + if (ret)
> + goto err;
> +
> + dev_info(dev, "watchdog enabled (timeout=%d sec, nowayout=%d)",
> + wdt->wdt_device.timeout, WATCHDOG_NOWAYOUT);
> +
> + return 0;
> +
> +err:
> + clk_disable_unprepare(wdt->clock);
> + return ret;
> +}
> +
> +static int zx2967_wdt_remove(struct platform_device *pdev)
> +{
> + struct zx2967_wdt *wdt = platform_get_drvdata(pdev);
> +
> + watchdog_unregister_device(&wdt->wdt_device);
> + clk_disable_unprepare(wdt->clock);
> +
> + return 0;
> +}
> +
> +static const struct of_device_id zx2967_wdt_match[] = {
> + { .compatible = "zte,zx296718-wdt", },
> + {}
> +};
> +MODULE_DEVICE_TABLE(of, zx2967_wdt_match);
> +
> +static struct platform_driver zx2967_wdt_driver = {
> + .probe = zx2967_wdt_probe,
> + .remove = zx2967_wdt_remove,
> + .driver = {
> + .name = "zx2967-wdt",
> + .of_match_table = of_match_ptr(zx2967_wdt_match),
> + },
> +};
> +module_platform_driver(zx2967_wdt_driver);
> +
> +MODULE_AUTHOR("Baoyou Xie <baoyou.xie@linaro.org>");
> +MODULE_DESCRIPTION("ZTE zx2967 Watchdog Device Driver");
> +MODULE_LICENSE("GPL v2");
> --
> 2.7.4
>
^ permalink raw reply [flat|nested] 19+ messages in thread* Re: [PATCH v8 3/3] watchdog: zx2967: add watchdog controller driver for ZTE's zx2967 family
@ 2017-02-03 16:02 ` Mathieu Poirier
0 siblings, 0 replies; 19+ messages in thread
From: Mathieu Poirier @ 2017-02-03 16:02 UTC (permalink / raw)
To: Baoyou Xie
Cc: jun.nie-QSEj5FYQhm4dnm+yROfE0A, wim-IQzOog9fTRqzQB+pC5nmwQ,
linux-0h96xk9xTtrk1uMJSBkQmQ, robh+dt-DgEjT+Ai2ygdnm+yROfE0A,
mark.rutland-5wv7dgnIgG8,
linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r,
linux-watchdog-u79uwXL29TY76Z2rM5mHXA,
devicetree-u79uwXL29TY76Z2rM5mHXA,
linux-kernel-u79uwXL29TY76Z2rM5mHXA,
shawnguo-DgEjT+Ai2ygdnm+yROfE0A,
xie.baoyou-Th6q7B73Y6EnDS1+zs4M5A,
chen.chaokai-Th6q7B73Y6EnDS1+zs4M5A,
wang.qiang01-Th6q7B73Y6EnDS1+zs4M5A
On Fri, Feb 03, 2017 at 11:22:20AM +0800, Baoyou Xie wrote:
> This patch adds watchdog controller driver for ZTE's zx2967 family.
>
> Signed-off-by: Baoyou Xie <baoyou.xie-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>
> ---
> drivers/watchdog/Kconfig | 10 ++
> drivers/watchdog/Makefile | 1 +
> drivers/watchdog/zx2967_wdt.c | 285 ++++++++++++++++++++++++++++++++++++++++++
> 3 files changed, 296 insertions(+)
> create mode 100644 drivers/watchdog/zx2967_wdt.c
>
> diff --git a/drivers/watchdog/Kconfig b/drivers/watchdog/Kconfig
> index acb00b5..05093a2 100644
> --- a/drivers/watchdog/Kconfig
> +++ b/drivers/watchdog/Kconfig
> @@ -714,6 +714,16 @@ config ASPEED_WATCHDOG
> To compile this driver as a module, choose M here: the
> module will be called aspeed_wdt.
>
> +config ZX2967_WATCHDOG
> + tristate "ZTE zx2967 SoCs watchdog support"
> + depends on ARCH_ZX
> + select WATCHDOG_CORE
> + help
> + Say Y here to include support for the watchdog timer
> + in ZTE zx2967 SoCs.
> + To compile this driver as a module, choose M here: the
> + module will be called zx2967_wdt.
> +
> # AVR32 Architecture
>
> config AT32AP700X_WDT
> diff --git a/drivers/watchdog/Makefile b/drivers/watchdog/Makefile
> index 0c3d35e..bf2d296 100644
> --- a/drivers/watchdog/Makefile
> +++ b/drivers/watchdog/Makefile
> @@ -82,6 +82,7 @@ obj-$(CONFIG_BCM7038_WDT) += bcm7038_wdt.o
> obj-$(CONFIG_ATLAS7_WATCHDOG) += atlas7_wdt.o
> obj-$(CONFIG_RENESAS_WDT) += renesas_wdt.o
> obj-$(CONFIG_ASPEED_WATCHDOG) += aspeed_wdt.o
> +obj-$(CONFIG_ZX2967_WATCHDOG) += zx2967_wdt.o
>
> # AVR32 Architecture
> obj-$(CONFIG_AT32AP700X_WDT) += at32ap700x_wdt.o
> diff --git a/drivers/watchdog/zx2967_wdt.c b/drivers/watchdog/zx2967_wdt.c
> new file mode 100644
> index 0000000..2daaca2
> --- /dev/null
> +++ b/drivers/watchdog/zx2967_wdt.c
> @@ -0,0 +1,285 @@
> +/*
> + * watchdog driver for ZTE's zx2967 family
> + *
> + * Copyright (C) 2017 ZTE Ltd.
> + *
> + * Author: Baoyou Xie <baoyou.xie-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>
> + *
> + * License terms: GNU General Public License (GPL) version 2
> + */
> +
> +#include <linux/clk.h>
> +#include <linux/io.h>
> +#include <linux/mfd/syscon.h>
> +#include <linux/module.h>
> +#include <linux/of_address.h>
> +#include <linux/platform_device.h>
> +#include <linux/regmap.h>
> +#include <linux/reset.h>
> +#include <linux/watchdog.h>
> +
> +#define ZX2967_WDT_CFG_REG 0x4
> +#define ZX2967_WDT_LOAD_REG 0x8
> +#define ZX2967_WDT_REFRESH_REG 0x18
> +#define ZX2967_WDT_START_REG 0x1c
> +
> +#define ZX2967_WDT_REFRESH_MASK 0x3f
> +
> +#define ZX2967_WDT_CFG_DIV(n) ((((n) & 0xff) - 1) << 8)
> +#define ZX2967_WDT_START_EN 0x1
> +
> +/*
> + * Hardware magic number.
> + * When watchdog reg is written, the lowest 16 bits are valid, but
> + * the highest 16 bits should be always this number.
> + */
Thanks for the explanation, much better now.
> +#define ZX2967_WDT_WRITEKEY (0x1234 << 16)
> +
> +#define ZX2967_WDT_DIV_DEFAULT 16
> +#define ZX2967_WDT_DEFAULT_TIMEOUT 32
> +#define ZX2967_WDT_MIN_TIMEOUT 1
> +#define ZX2967_WDT_MAX_TIMEOUT 524
> +#define ZX2967_WDT_MAX_COUNT 0xffff
> +
> +#define ZX2967_WDT_CLK_FREQ 0x8000
> +
> +#define ZX2967_WDT_FLAG_REBOOT_MON BIT(0)
> +
> +struct zx2967_wdt {
> + struct watchdog_device wdt_device;
> + void __iomem *reg_base;
> + struct clk *clock;
> +};
> +
> +static inline u32 zx2967_wdt_readl(struct zx2967_wdt *wdt, u16 reg)
> +{
> + return readl_relaxed(wdt->reg_base + reg);
> +}
> +
> +static inline void zx2967_wdt_writel(struct zx2967_wdt *wdt, u16 reg, u16 val)
> +{
> + writel_relaxed(val | ZX2967_WDT_WRITEKEY, wdt->reg_base + reg);
> +}
You were correct with the u32 type. My comment was about making sure the value
of the value given to the function wasn't bigger than 65535 (0xffff), which
would have been corrupted by the OR'ing with ZX2967_WDT_WRITEKEY.
Going with a u16 forces you to manipulate u16 types in all the functions below
but the read operation is still a u32, leaving to the compiler the task of
stripping the top 16 bit.
My suggestion is to go back to a u32 for zx2967_wdt_writel() but to AND 'val'
with 0x0000ffff before OR'ing it with ZX2967_WDT_WRITEKEY.
> +
> +static void zx2967_wdt_refresh(struct zx2967_wdt *wdt)
> +{
> + u16 val;
> +
> + val = zx2967_wdt_readl(wdt, ZX2967_WDT_REFRESH_REG);
> + /*
> + * Bit 4-5, 1 and 2: refresh config info
> + * Bit 2-3, 1 and 2: refresh counter
> + * Bit 0-1, 1 and 2: refresh int-value
> + * we shift each group value between 1 and 2 to refresh all data.
> + */
> + val ^= ZX2967_WDT_REFRESH_MASK;
> + zx2967_wdt_writel(wdt, ZX2967_WDT_REFRESH_REG, val);
> +}
> +
> +static int
> +zx2967_wdt_set_timeout(struct watchdog_device *wdd, unsigned int timeout)
> +{
> + struct zx2967_wdt *wdt = watchdog_get_drvdata(wdd);
> + unsigned int divisor = ZX2967_WDT_DIV_DEFAULT;
> + u32 count;
> +
> + count = timeout * ZX2967_WDT_CLK_FREQ;
> + if (count > divisor * ZX2967_WDT_MAX_COUNT)
> + divisor = DIV_ROUND_UP(count, ZX2967_WDT_MAX_COUNT);
> + count = DIV_ROUND_UP(count, divisor);
> + zx2967_wdt_writel(wdt, ZX2967_WDT_CFG_REG, ZX2967_WDT_CFG_DIV(divisor));
> + zx2967_wdt_writel(wdt, ZX2967_WDT_LOAD_REG, count);
> + zx2967_wdt_refresh(wdt);
> + wdd->timeout = (count * divisor) / ZX2967_WDT_CLK_FREQ;
> +
> + return 0;
> +}
> +
> +static void __zx2967_wdt_start(struct zx2967_wdt *wdt)
> +{
> + u16 val;
> +
> + val = zx2967_wdt_readl(wdt, ZX2967_WDT_START_REG);
> + val |= ZX2967_WDT_START_EN;
> + zx2967_wdt_writel(wdt, ZX2967_WDT_START_REG, val);
> +}
> +
> +static void __zx2967_wdt_stop(struct zx2967_wdt *wdt)
> +{
> + u16 val;
> +
> + val = zx2967_wdt_readl(wdt, ZX2967_WDT_START_REG);
> + val &= ~ZX2967_WDT_START_EN;
> + zx2967_wdt_writel(wdt, ZX2967_WDT_START_REG, val);
> +}
> +
> +static int zx2967_wdt_start(struct watchdog_device *wdd)
> +{
> + struct zx2967_wdt *wdt = watchdog_get_drvdata(wdd);
> +
> + zx2967_wdt_set_timeout(wdd, wdd->timeout);
> + __zx2967_wdt_start(wdt);
> +
> + return 0;
> +}
> +
> +static int zx2967_wdt_stop(struct watchdog_device *wdd)
> +{
> + struct zx2967_wdt *wdt = watchdog_get_drvdata(wdd);
> +
> + __zx2967_wdt_stop(wdt);
> +
> + return 0;
> +}
> +
> +static int zx2967_wdt_keepalive(struct watchdog_device *wdd)
> +{
> + struct zx2967_wdt *wdt = watchdog_get_drvdata(wdd);
> +
> + zx2967_wdt_refresh(wdt);
> +
> + return 0;
> +}
> +
> +#define ZX2967_WDT_OPTIONS \
> + (WDIOF_SETTIMEOUT | WDIOF_KEEPALIVEPING | WDIOF_MAGICCLOSE)
> +static const struct watchdog_info zx2967_wdt_ident = {
> + .options = ZX2967_WDT_OPTIONS,
> + .identity = "zx2967 watchdog",
> +};
> +
> +static struct watchdog_ops zx2967_wdt_ops = {
> + .owner = THIS_MODULE,
> + .start = zx2967_wdt_start,
> + .stop = zx2967_wdt_stop,
> + .ping = zx2967_wdt_keepalive,
> + .set_timeout = zx2967_wdt_set_timeout,
> +};
> +
> +static void zx2967_wdt_reset_sysctrl(struct device *dev)
> +{
> + int ret;
> + void __iomem *regmap;
> + unsigned int offset, mask, config;
> + struct of_phandle_args out_args;
> +
> + ret = of_parse_phandle_with_fixed_args(dev->of_node,
> + "zte,wdt-reset-sysctrl", 3, 0, &out_args);
> + if (ret)
> + return;
> +
> + offset = out_args.args[0];
> + config = out_args.args[1];
> + mask = out_args.args[2];
> +
> + regmap = syscon_node_to_regmap(out_args.np);
> + if (IS_ERR(regmap)) {
> + of_node_put(out_args.np);
> + return;
> + }
> +
> + regmap_update_bits(regmap, offset, mask, config);
> + of_node_put(out_args.np);
> +}
> +
> +static int zx2967_wdt_probe(struct platform_device *pdev)
> +{
> + struct device *dev = &pdev->dev;
> + struct zx2967_wdt *wdt;
> + struct resource *base;
> + int ret;
> + struct reset_control *rstc;
> +
> + wdt = devm_kzalloc(dev, sizeof(*wdt), GFP_KERNEL);
> + if (!wdt)
> + return -ENOMEM;
> +
> + platform_set_drvdata(pdev, wdt);
> +
> + wdt->wdt_device.info = &zx2967_wdt_ident;
> + wdt->wdt_device.ops = &zx2967_wdt_ops;
> + wdt->wdt_device.timeout = ZX2967_WDT_DEFAULT_TIMEOUT;
> + wdt->wdt_device.max_timeout = ZX2967_WDT_MAX_TIMEOUT;
> + wdt->wdt_device.min_timeout = ZX2967_WDT_MIN_TIMEOUT;
> + wdt->wdt_device.parent = &pdev->dev;
> +
> + base = platform_get_resource(pdev, IORESOURCE_MEM, 0);
> + wdt->reg_base = devm_ioremap_resource(dev, base);
> + if (IS_ERR(wdt->reg_base)) {
> + dev_err(dev, "ioremap failed\n");
> + return PTR_ERR(wdt->reg_base);
> + }
> +
> + zx2967_wdt_reset_sysctrl(dev);
> +
> + wdt->clock = devm_clk_get(dev, NULL);
> + if (IS_ERR(wdt->clock)) {
> + dev_err(dev, "failed to find watchdog clock source\n");
> + return PTR_ERR(wdt->clock);
> + }
> +
> + ret = clk_prepare_enable(wdt->clock);
> + if (ret < 0) {
> + dev_err(dev, "failed to enable clock\n");
> + return ret;
> + }
> + clk_set_rate(wdt->clock, ZX2967_WDT_CLK_FREQ);
> +
> + rstc = devm_reset_control_get(dev, NULL);
> + if (IS_ERR(rstc)) {
> + dev_err(dev, "failed to get rstc");
> + ret = PTR_ERR(rstc);
> + goto err;
> + }
> +
> + reset_control_assert(rstc);
> + reset_control_deassert(rstc);
> +
> + watchdog_set_drvdata(&wdt->wdt_device, wdt);
> + watchdog_init_timeout(&wdt->wdt_device,
> + ZX2967_WDT_DEFAULT_TIMEOUT, dev);
> + watchdog_set_nowayout(&wdt->wdt_device, WATCHDOG_NOWAYOUT);
> +
> + ret = watchdog_register_device(&wdt->wdt_device);
> + if (ret)
> + goto err;
> +
> + dev_info(dev, "watchdog enabled (timeout=%d sec, nowayout=%d)",
> + wdt->wdt_device.timeout, WATCHDOG_NOWAYOUT);
> +
> + return 0;
> +
> +err:
> + clk_disable_unprepare(wdt->clock);
> + return ret;
> +}
> +
> +static int zx2967_wdt_remove(struct platform_device *pdev)
> +{
> + struct zx2967_wdt *wdt = platform_get_drvdata(pdev);
> +
> + watchdog_unregister_device(&wdt->wdt_device);
> + clk_disable_unprepare(wdt->clock);
> +
> + return 0;
> +}
> +
> +static const struct of_device_id zx2967_wdt_match[] = {
> + { .compatible = "zte,zx296718-wdt", },
> + {}
> +};
> +MODULE_DEVICE_TABLE(of, zx2967_wdt_match);
> +
> +static struct platform_driver zx2967_wdt_driver = {
> + .probe = zx2967_wdt_probe,
> + .remove = zx2967_wdt_remove,
> + .driver = {
> + .name = "zx2967-wdt",
> + .of_match_table = of_match_ptr(zx2967_wdt_match),
> + },
> +};
> +module_platform_driver(zx2967_wdt_driver);
> +
> +MODULE_AUTHOR("Baoyou Xie <baoyou.xie-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>");
> +MODULE_DESCRIPTION("ZTE zx2967 Watchdog Device Driver");
> +MODULE_LICENSE("GPL v2");
> --
> 2.7.4
>
--
To unsubscribe from this list: send the line "unsubscribe devicetree" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
^ permalink raw reply [flat|nested] 19+ messages in thread* Re: [PATCH v8 3/3] watchdog: zx2967: add watchdog controller driver for ZTE's zx2967 family
@ 2017-02-03 17:07 ` Guenter Roeck
0 siblings, 0 replies; 19+ messages in thread
From: Guenter Roeck @ 2017-02-03 17:07 UTC (permalink / raw)
To: Mathieu Poirier
Cc: Baoyou Xie, jun.nie, wim, robh+dt, mark.rutland,
linux-arm-kernel, linux-watchdog, devicetree, linux-kernel,
shawnguo, xie.baoyou, chen.chaokai, wang.qiang01
On Fri, Feb 03, 2017 at 09:02:57AM -0700, Mathieu Poirier wrote:
> On Fri, Feb 03, 2017 at 11:22:20AM +0800, Baoyou Xie wrote:
> > This patch adds watchdog controller driver for ZTE's zx2967 family.
> >
> > Signed-off-by: Baoyou Xie <baoyou.xie@linaro.org>
> > ---
> > drivers/watchdog/Kconfig | 10 ++
> > drivers/watchdog/Makefile | 1 +
> > drivers/watchdog/zx2967_wdt.c | 285 ++++++++++++++++++++++++++++++++++++++++++
> > 3 files changed, 296 insertions(+)
> > create mode 100644 drivers/watchdog/zx2967_wdt.c
> >
> > diff --git a/drivers/watchdog/Kconfig b/drivers/watchdog/Kconfig
> > index acb00b5..05093a2 100644
> > --- a/drivers/watchdog/Kconfig
> > +++ b/drivers/watchdog/Kconfig
> > @@ -714,6 +714,16 @@ config ASPEED_WATCHDOG
> > To compile this driver as a module, choose M here: the
> > module will be called aspeed_wdt.
> >
> > +config ZX2967_WATCHDOG
> > + tristate "ZTE zx2967 SoCs watchdog support"
> > + depends on ARCH_ZX
> > + select WATCHDOG_CORE
> > + help
> > + Say Y here to include support for the watchdog timer
> > + in ZTE zx2967 SoCs.
> > + To compile this driver as a module, choose M here: the
> > + module will be called zx2967_wdt.
> > +
> > # AVR32 Architecture
> >
> > config AT32AP700X_WDT
> > diff --git a/drivers/watchdog/Makefile b/drivers/watchdog/Makefile
> > index 0c3d35e..bf2d296 100644
> > --- a/drivers/watchdog/Makefile
> > +++ b/drivers/watchdog/Makefile
> > @@ -82,6 +82,7 @@ obj-$(CONFIG_BCM7038_WDT) += bcm7038_wdt.o
> > obj-$(CONFIG_ATLAS7_WATCHDOG) += atlas7_wdt.o
> > obj-$(CONFIG_RENESAS_WDT) += renesas_wdt.o
> > obj-$(CONFIG_ASPEED_WATCHDOG) += aspeed_wdt.o
> > +obj-$(CONFIG_ZX2967_WATCHDOG) += zx2967_wdt.o
> >
> > # AVR32 Architecture
> > obj-$(CONFIG_AT32AP700X_WDT) += at32ap700x_wdt.o
> > diff --git a/drivers/watchdog/zx2967_wdt.c b/drivers/watchdog/zx2967_wdt.c
> > new file mode 100644
> > index 0000000..2daaca2
> > --- /dev/null
> > +++ b/drivers/watchdog/zx2967_wdt.c
> > @@ -0,0 +1,285 @@
> > +/*
> > + * watchdog driver for ZTE's zx2967 family
> > + *
> > + * Copyright (C) 2017 ZTE Ltd.
> > + *
> > + * Author: Baoyou Xie <baoyou.xie@linaro.org>
> > + *
> > + * License terms: GNU General Public License (GPL) version 2
> > + */
> > +
> > +#include <linux/clk.h>
> > +#include <linux/io.h>
> > +#include <linux/mfd/syscon.h>
> > +#include <linux/module.h>
> > +#include <linux/of_address.h>
> > +#include <linux/platform_device.h>
> > +#include <linux/regmap.h>
> > +#include <linux/reset.h>
> > +#include <linux/watchdog.h>
> > +
> > +#define ZX2967_WDT_CFG_REG 0x4
> > +#define ZX2967_WDT_LOAD_REG 0x8
> > +#define ZX2967_WDT_REFRESH_REG 0x18
> > +#define ZX2967_WDT_START_REG 0x1c
> > +
> > +#define ZX2967_WDT_REFRESH_MASK 0x3f
> > +
> > +#define ZX2967_WDT_CFG_DIV(n) ((((n) & 0xff) - 1) << 8)
> > +#define ZX2967_WDT_START_EN 0x1
> > +
> > +/*
> > + * Hardware magic number.
> > + * When watchdog reg is written, the lowest 16 bits are valid, but
> > + * the highest 16 bits should be always this number.
> > + */
>
> Thanks for the explanation, much better now.
>
> > +#define ZX2967_WDT_WRITEKEY (0x1234 << 16)
> > +
> > +#define ZX2967_WDT_DIV_DEFAULT 16
> > +#define ZX2967_WDT_DEFAULT_TIMEOUT 32
> > +#define ZX2967_WDT_MIN_TIMEOUT 1
> > +#define ZX2967_WDT_MAX_TIMEOUT 524
> > +#define ZX2967_WDT_MAX_COUNT 0xffff
> > +
> > +#define ZX2967_WDT_CLK_FREQ 0x8000
> > +
> > +#define ZX2967_WDT_FLAG_REBOOT_MON BIT(0)
> > +
> > +struct zx2967_wdt {
> > + struct watchdog_device wdt_device;
> > + void __iomem *reg_base;
> > + struct clk *clock;
> > +};
> > +
> > +static inline u32 zx2967_wdt_readl(struct zx2967_wdt *wdt, u16 reg)
> > +{
> > + return readl_relaxed(wdt->reg_base + reg);
> > +}
> > +
> > +static inline void zx2967_wdt_writel(struct zx2967_wdt *wdt, u16 reg, u16 val)
> > +{
> > + writel_relaxed(val | ZX2967_WDT_WRITEKEY, wdt->reg_base + reg);
> > +}
>
> You were correct with the u32 type. My comment was about making sure the value
> of the value given to the function wasn't bigger than 65535 (0xffff), which
> would have been corrupted by the OR'ing with ZX2967_WDT_WRITEKEY.
>
> Going with a u16 forces you to manipulate u16 types in all the functions below
> but the read operation is still a u32, leaving to the compiler the task of
> stripping the top 16 bit.
>
> My suggestion is to go back to a u32 for zx2967_wdt_writel() but to AND 'val'
> with 0x0000ffff before OR'ing it with ZX2967_WDT_WRITEKEY.
>
For the record, I am fine either way, including not masking at all;
I considered that a theoretic problem that only applies if reading
a register can return a value other than 0 in the upper 16 bit.
So, ultimately, this patch series is now waiting for your Ack.
Guenter
^ permalink raw reply [flat|nested] 19+ messages in thread* [PATCH v8 3/3] watchdog: zx2967: add watchdog controller driver for ZTE's zx2967 family
@ 2017-02-03 17:07 ` Guenter Roeck
0 siblings, 0 replies; 19+ messages in thread
From: Guenter Roeck @ 2017-02-03 17:07 UTC (permalink / raw)
To: linux-arm-kernel
On Fri, Feb 03, 2017 at 09:02:57AM -0700, Mathieu Poirier wrote:
> On Fri, Feb 03, 2017 at 11:22:20AM +0800, Baoyou Xie wrote:
> > This patch adds watchdog controller driver for ZTE's zx2967 family.
> >
> > Signed-off-by: Baoyou Xie <baoyou.xie@linaro.org>
> > ---
> > drivers/watchdog/Kconfig | 10 ++
> > drivers/watchdog/Makefile | 1 +
> > drivers/watchdog/zx2967_wdt.c | 285 ++++++++++++++++++++++++++++++++++++++++++
> > 3 files changed, 296 insertions(+)
> > create mode 100644 drivers/watchdog/zx2967_wdt.c
> >
> > diff --git a/drivers/watchdog/Kconfig b/drivers/watchdog/Kconfig
> > index acb00b5..05093a2 100644
> > --- a/drivers/watchdog/Kconfig
> > +++ b/drivers/watchdog/Kconfig
> > @@ -714,6 +714,16 @@ config ASPEED_WATCHDOG
> > To compile this driver as a module, choose M here: the
> > module will be called aspeed_wdt.
> >
> > +config ZX2967_WATCHDOG
> > + tristate "ZTE zx2967 SoCs watchdog support"
> > + depends on ARCH_ZX
> > + select WATCHDOG_CORE
> > + help
> > + Say Y here to include support for the watchdog timer
> > + in ZTE zx2967 SoCs.
> > + To compile this driver as a module, choose M here: the
> > + module will be called zx2967_wdt.
> > +
> > # AVR32 Architecture
> >
> > config AT32AP700X_WDT
> > diff --git a/drivers/watchdog/Makefile b/drivers/watchdog/Makefile
> > index 0c3d35e..bf2d296 100644
> > --- a/drivers/watchdog/Makefile
> > +++ b/drivers/watchdog/Makefile
> > @@ -82,6 +82,7 @@ obj-$(CONFIG_BCM7038_WDT) += bcm7038_wdt.o
> > obj-$(CONFIG_ATLAS7_WATCHDOG) += atlas7_wdt.o
> > obj-$(CONFIG_RENESAS_WDT) += renesas_wdt.o
> > obj-$(CONFIG_ASPEED_WATCHDOG) += aspeed_wdt.o
> > +obj-$(CONFIG_ZX2967_WATCHDOG) += zx2967_wdt.o
> >
> > # AVR32 Architecture
> > obj-$(CONFIG_AT32AP700X_WDT) += at32ap700x_wdt.o
> > diff --git a/drivers/watchdog/zx2967_wdt.c b/drivers/watchdog/zx2967_wdt.c
> > new file mode 100644
> > index 0000000..2daaca2
> > --- /dev/null
> > +++ b/drivers/watchdog/zx2967_wdt.c
> > @@ -0,0 +1,285 @@
> > +/*
> > + * watchdog driver for ZTE's zx2967 family
> > + *
> > + * Copyright (C) 2017 ZTE Ltd.
> > + *
> > + * Author: Baoyou Xie <baoyou.xie@linaro.org>
> > + *
> > + * License terms: GNU General Public License (GPL) version 2
> > + */
> > +
> > +#include <linux/clk.h>
> > +#include <linux/io.h>
> > +#include <linux/mfd/syscon.h>
> > +#include <linux/module.h>
> > +#include <linux/of_address.h>
> > +#include <linux/platform_device.h>
> > +#include <linux/regmap.h>
> > +#include <linux/reset.h>
> > +#include <linux/watchdog.h>
> > +
> > +#define ZX2967_WDT_CFG_REG 0x4
> > +#define ZX2967_WDT_LOAD_REG 0x8
> > +#define ZX2967_WDT_REFRESH_REG 0x18
> > +#define ZX2967_WDT_START_REG 0x1c
> > +
> > +#define ZX2967_WDT_REFRESH_MASK 0x3f
> > +
> > +#define ZX2967_WDT_CFG_DIV(n) ((((n) & 0xff) - 1) << 8)
> > +#define ZX2967_WDT_START_EN 0x1
> > +
> > +/*
> > + * Hardware magic number.
> > + * When watchdog reg is written, the lowest 16 bits are valid, but
> > + * the highest 16 bits should be always this number.
> > + */
>
> Thanks for the explanation, much better now.
>
> > +#define ZX2967_WDT_WRITEKEY (0x1234 << 16)
> > +
> > +#define ZX2967_WDT_DIV_DEFAULT 16
> > +#define ZX2967_WDT_DEFAULT_TIMEOUT 32
> > +#define ZX2967_WDT_MIN_TIMEOUT 1
> > +#define ZX2967_WDT_MAX_TIMEOUT 524
> > +#define ZX2967_WDT_MAX_COUNT 0xffff
> > +
> > +#define ZX2967_WDT_CLK_FREQ 0x8000
> > +
> > +#define ZX2967_WDT_FLAG_REBOOT_MON BIT(0)
> > +
> > +struct zx2967_wdt {
> > + struct watchdog_device wdt_device;
> > + void __iomem *reg_base;
> > + struct clk *clock;
> > +};
> > +
> > +static inline u32 zx2967_wdt_readl(struct zx2967_wdt *wdt, u16 reg)
> > +{
> > + return readl_relaxed(wdt->reg_base + reg);
> > +}
> > +
> > +static inline void zx2967_wdt_writel(struct zx2967_wdt *wdt, u16 reg, u16 val)
> > +{
> > + writel_relaxed(val | ZX2967_WDT_WRITEKEY, wdt->reg_base + reg);
> > +}
>
> You were correct with the u32 type. My comment was about making sure the value
> of the value given to the function wasn't bigger than 65535 (0xffff), which
> would have been corrupted by the OR'ing with ZX2967_WDT_WRITEKEY.
>
> Going with a u16 forces you to manipulate u16 types in all the functions below
> but the read operation is still a u32, leaving to the compiler the task of
> stripping the top 16 bit.
>
> My suggestion is to go back to a u32 for zx2967_wdt_writel() but to AND 'val'
> with 0x0000ffff before OR'ing it with ZX2967_WDT_WRITEKEY.
>
For the record, I am fine either way, including not masking at all;
I considered that a theoretic problem that only applies if reading
a register can return a value other than 0 in the upper 16 bit.
So, ultimately, this patch series is now waiting for your Ack.
Guenter
^ permalink raw reply [flat|nested] 19+ messages in thread* Re: [PATCH v8 3/3] watchdog: zx2967: add watchdog controller driver for ZTE's zx2967 family
@ 2017-02-03 17:07 ` Guenter Roeck
0 siblings, 0 replies; 19+ messages in thread
From: Guenter Roeck @ 2017-02-03 17:07 UTC (permalink / raw)
To: Mathieu Poirier
Cc: Baoyou Xie, jun.nie-QSEj5FYQhm4dnm+yROfE0A,
wim-IQzOog9fTRqzQB+pC5nmwQ, robh+dt-DgEjT+Ai2ygdnm+yROfE0A,
mark.rutland-5wv7dgnIgG8,
linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r,
linux-watchdog-u79uwXL29TY76Z2rM5mHXA,
devicetree-u79uwXL29TY76Z2rM5mHXA,
linux-kernel-u79uwXL29TY76Z2rM5mHXA,
shawnguo-DgEjT+Ai2ygdnm+yROfE0A,
xie.baoyou-Th6q7B73Y6EnDS1+zs4M5A,
chen.chaokai-Th6q7B73Y6EnDS1+zs4M5A,
wang.qiang01-Th6q7B73Y6EnDS1+zs4M5A
On Fri, Feb 03, 2017 at 09:02:57AM -0700, Mathieu Poirier wrote:
> On Fri, Feb 03, 2017 at 11:22:20AM +0800, Baoyou Xie wrote:
> > This patch adds watchdog controller driver for ZTE's zx2967 family.
> >
> > Signed-off-by: Baoyou Xie <baoyou.xie-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>
> > ---
> > drivers/watchdog/Kconfig | 10 ++
> > drivers/watchdog/Makefile | 1 +
> > drivers/watchdog/zx2967_wdt.c | 285 ++++++++++++++++++++++++++++++++++++++++++
> > 3 files changed, 296 insertions(+)
> > create mode 100644 drivers/watchdog/zx2967_wdt.c
> >
> > diff --git a/drivers/watchdog/Kconfig b/drivers/watchdog/Kconfig
> > index acb00b5..05093a2 100644
> > --- a/drivers/watchdog/Kconfig
> > +++ b/drivers/watchdog/Kconfig
> > @@ -714,6 +714,16 @@ config ASPEED_WATCHDOG
> > To compile this driver as a module, choose M here: the
> > module will be called aspeed_wdt.
> >
> > +config ZX2967_WATCHDOG
> > + tristate "ZTE zx2967 SoCs watchdog support"
> > + depends on ARCH_ZX
> > + select WATCHDOG_CORE
> > + help
> > + Say Y here to include support for the watchdog timer
> > + in ZTE zx2967 SoCs.
> > + To compile this driver as a module, choose M here: the
> > + module will be called zx2967_wdt.
> > +
> > # AVR32 Architecture
> >
> > config AT32AP700X_WDT
> > diff --git a/drivers/watchdog/Makefile b/drivers/watchdog/Makefile
> > index 0c3d35e..bf2d296 100644
> > --- a/drivers/watchdog/Makefile
> > +++ b/drivers/watchdog/Makefile
> > @@ -82,6 +82,7 @@ obj-$(CONFIG_BCM7038_WDT) += bcm7038_wdt.o
> > obj-$(CONFIG_ATLAS7_WATCHDOG) += atlas7_wdt.o
> > obj-$(CONFIG_RENESAS_WDT) += renesas_wdt.o
> > obj-$(CONFIG_ASPEED_WATCHDOG) += aspeed_wdt.o
> > +obj-$(CONFIG_ZX2967_WATCHDOG) += zx2967_wdt.o
> >
> > # AVR32 Architecture
> > obj-$(CONFIG_AT32AP700X_WDT) += at32ap700x_wdt.o
> > diff --git a/drivers/watchdog/zx2967_wdt.c b/drivers/watchdog/zx2967_wdt.c
> > new file mode 100644
> > index 0000000..2daaca2
> > --- /dev/null
> > +++ b/drivers/watchdog/zx2967_wdt.c
> > @@ -0,0 +1,285 @@
> > +/*
> > + * watchdog driver for ZTE's zx2967 family
> > + *
> > + * Copyright (C) 2017 ZTE Ltd.
> > + *
> > + * Author: Baoyou Xie <baoyou.xie-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>
> > + *
> > + * License terms: GNU General Public License (GPL) version 2
> > + */
> > +
> > +#include <linux/clk.h>
> > +#include <linux/io.h>
> > +#include <linux/mfd/syscon.h>
> > +#include <linux/module.h>
> > +#include <linux/of_address.h>
> > +#include <linux/platform_device.h>
> > +#include <linux/regmap.h>
> > +#include <linux/reset.h>
> > +#include <linux/watchdog.h>
> > +
> > +#define ZX2967_WDT_CFG_REG 0x4
> > +#define ZX2967_WDT_LOAD_REG 0x8
> > +#define ZX2967_WDT_REFRESH_REG 0x18
> > +#define ZX2967_WDT_START_REG 0x1c
> > +
> > +#define ZX2967_WDT_REFRESH_MASK 0x3f
> > +
> > +#define ZX2967_WDT_CFG_DIV(n) ((((n) & 0xff) - 1) << 8)
> > +#define ZX2967_WDT_START_EN 0x1
> > +
> > +/*
> > + * Hardware magic number.
> > + * When watchdog reg is written, the lowest 16 bits are valid, but
> > + * the highest 16 bits should be always this number.
> > + */
>
> Thanks for the explanation, much better now.
>
> > +#define ZX2967_WDT_WRITEKEY (0x1234 << 16)
> > +
> > +#define ZX2967_WDT_DIV_DEFAULT 16
> > +#define ZX2967_WDT_DEFAULT_TIMEOUT 32
> > +#define ZX2967_WDT_MIN_TIMEOUT 1
> > +#define ZX2967_WDT_MAX_TIMEOUT 524
> > +#define ZX2967_WDT_MAX_COUNT 0xffff
> > +
> > +#define ZX2967_WDT_CLK_FREQ 0x8000
> > +
> > +#define ZX2967_WDT_FLAG_REBOOT_MON BIT(0)
> > +
> > +struct zx2967_wdt {
> > + struct watchdog_device wdt_device;
> > + void __iomem *reg_base;
> > + struct clk *clock;
> > +};
> > +
> > +static inline u32 zx2967_wdt_readl(struct zx2967_wdt *wdt, u16 reg)
> > +{
> > + return readl_relaxed(wdt->reg_base + reg);
> > +}
> > +
> > +static inline void zx2967_wdt_writel(struct zx2967_wdt *wdt, u16 reg, u16 val)
> > +{
> > + writel_relaxed(val | ZX2967_WDT_WRITEKEY, wdt->reg_base + reg);
> > +}
>
> You were correct with the u32 type. My comment was about making sure the value
> of the value given to the function wasn't bigger than 65535 (0xffff), which
> would have been corrupted by the OR'ing with ZX2967_WDT_WRITEKEY.
>
> Going with a u16 forces you to manipulate u16 types in all the functions below
> but the read operation is still a u32, leaving to the compiler the task of
> stripping the top 16 bit.
>
> My suggestion is to go back to a u32 for zx2967_wdt_writel() but to AND 'val'
> with 0x0000ffff before OR'ing it with ZX2967_WDT_WRITEKEY.
>
For the record, I am fine either way, including not masking at all;
I considered that a theoretic problem that only applies if reading
a register can return a value other than 0 in the upper 16 bit.
So, ultimately, this patch series is now waiting for your Ack.
Guenter
--
To unsubscribe from this list: send the line "unsubscribe linux-watchdog" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
^ permalink raw reply [flat|nested] 19+ messages in thread* Re: [PATCH v8 3/3] watchdog: zx2967: add watchdog controller driver for ZTE's zx2967 family
@ 2017-02-03 22:48 ` Mathieu Poirier
0 siblings, 0 replies; 19+ messages in thread
From: Mathieu Poirier @ 2017-02-03 22:48 UTC (permalink / raw)
To: Guenter Roeck
Cc: Baoyou Xie, Jun Nie, wim, Rob Herring, Mark Rutland,
linux-arm-kernel, linux-watchdog, devicetree, linux-kernel,
Shawn Guo, xie.baoyou, chen.chaokai, wang.qiang01
On 3 February 2017 at 10:07, Guenter Roeck <linux@roeck-us.net> wrote:
> On Fri, Feb 03, 2017 at 09:02:57AM -0700, Mathieu Poirier wrote:
>> On Fri, Feb 03, 2017 at 11:22:20AM +0800, Baoyou Xie wrote:
>> > This patch adds watchdog controller driver for ZTE's zx2967 family.
>> >
>> > Signed-off-by: Baoyou Xie <baoyou.xie@linaro.org>
>> > ---
>> > drivers/watchdog/Kconfig | 10 ++
>> > drivers/watchdog/Makefile | 1 +
>> > drivers/watchdog/zx2967_wdt.c | 285 ++++++++++++++++++++++++++++++++++++++++++
>> > 3 files changed, 296 insertions(+)
>> > create mode 100644 drivers/watchdog/zx2967_wdt.c
>> >
>> > diff --git a/drivers/watchdog/Kconfig b/drivers/watchdog/Kconfig
>> > index acb00b5..05093a2 100644
>> > --- a/drivers/watchdog/Kconfig
>> > +++ b/drivers/watchdog/Kconfig
>> > @@ -714,6 +714,16 @@ config ASPEED_WATCHDOG
>> > To compile this driver as a module, choose M here: the
>> > module will be called aspeed_wdt.
>> >
>> > +config ZX2967_WATCHDOG
>> > + tristate "ZTE zx2967 SoCs watchdog support"
>> > + depends on ARCH_ZX
>> > + select WATCHDOG_CORE
>> > + help
>> > + Say Y here to include support for the watchdog timer
>> > + in ZTE zx2967 SoCs.
>> > + To compile this driver as a module, choose M here: the
>> > + module will be called zx2967_wdt.
>> > +
>> > # AVR32 Architecture
>> >
>> > config AT32AP700X_WDT
>> > diff --git a/drivers/watchdog/Makefile b/drivers/watchdog/Makefile
>> > index 0c3d35e..bf2d296 100644
>> > --- a/drivers/watchdog/Makefile
>> > +++ b/drivers/watchdog/Makefile
>> > @@ -82,6 +82,7 @@ obj-$(CONFIG_BCM7038_WDT) += bcm7038_wdt.o
>> > obj-$(CONFIG_ATLAS7_WATCHDOG) += atlas7_wdt.o
>> > obj-$(CONFIG_RENESAS_WDT) += renesas_wdt.o
>> > obj-$(CONFIG_ASPEED_WATCHDOG) += aspeed_wdt.o
>> > +obj-$(CONFIG_ZX2967_WATCHDOG) += zx2967_wdt.o
>> >
>> > # AVR32 Architecture
>> > obj-$(CONFIG_AT32AP700X_WDT) += at32ap700x_wdt.o
>> > diff --git a/drivers/watchdog/zx2967_wdt.c b/drivers/watchdog/zx2967_wdt.c
>> > new file mode 100644
>> > index 0000000..2daaca2
>> > --- /dev/null
>> > +++ b/drivers/watchdog/zx2967_wdt.c
>> > @@ -0,0 +1,285 @@
>> > +/*
>> > + * watchdog driver for ZTE's zx2967 family
>> > + *
>> > + * Copyright (C) 2017 ZTE Ltd.
>> > + *
>> > + * Author: Baoyou Xie <baoyou.xie@linaro.org>
>> > + *
>> > + * License terms: GNU General Public License (GPL) version 2
>> > + */
>> > +
>> > +#include <linux/clk.h>
>> > +#include <linux/io.h>
>> > +#include <linux/mfd/syscon.h>
>> > +#include <linux/module.h>
>> > +#include <linux/of_address.h>
>> > +#include <linux/platform_device.h>
>> > +#include <linux/regmap.h>
>> > +#include <linux/reset.h>
>> > +#include <linux/watchdog.h>
>> > +
>> > +#define ZX2967_WDT_CFG_REG 0x4
>> > +#define ZX2967_WDT_LOAD_REG 0x8
>> > +#define ZX2967_WDT_REFRESH_REG 0x18
>> > +#define ZX2967_WDT_START_REG 0x1c
>> > +
>> > +#define ZX2967_WDT_REFRESH_MASK 0x3f
>> > +
>> > +#define ZX2967_WDT_CFG_DIV(n) ((((n) & 0xff) - 1) << 8)
>> > +#define ZX2967_WDT_START_EN 0x1
>> > +
>> > +/*
>> > + * Hardware magic number.
>> > + * When watchdog reg is written, the lowest 16 bits are valid, but
>> > + * the highest 16 bits should be always this number.
>> > + */
>>
>> Thanks for the explanation, much better now.
>>
>> > +#define ZX2967_WDT_WRITEKEY (0x1234 << 16)
>> > +
>> > +#define ZX2967_WDT_DIV_DEFAULT 16
>> > +#define ZX2967_WDT_DEFAULT_TIMEOUT 32
>> > +#define ZX2967_WDT_MIN_TIMEOUT 1
>> > +#define ZX2967_WDT_MAX_TIMEOUT 524
>> > +#define ZX2967_WDT_MAX_COUNT 0xffff
>> > +
>> > +#define ZX2967_WDT_CLK_FREQ 0x8000
>> > +
>> > +#define ZX2967_WDT_FLAG_REBOOT_MON BIT(0)
>> > +
>> > +struct zx2967_wdt {
>> > + struct watchdog_device wdt_device;
>> > + void __iomem *reg_base;
>> > + struct clk *clock;
>> > +};
>> > +
>> > +static inline u32 zx2967_wdt_readl(struct zx2967_wdt *wdt, u16 reg)
>> > +{
>> > + return readl_relaxed(wdt->reg_base + reg);
>> > +}
>> > +
>> > +static inline void zx2967_wdt_writel(struct zx2967_wdt *wdt, u16 reg, u16 val)
>> > +{
>> > + writel_relaxed(val | ZX2967_WDT_WRITEKEY, wdt->reg_base + reg);
>> > +}
>>
>> You were correct with the u32 type. My comment was about making sure the value
>> of the value given to the function wasn't bigger than 65535 (0xffff), which
>> would have been corrupted by the OR'ing with ZX2967_WDT_WRITEKEY.
>>
>> Going with a u16 forces you to manipulate u16 types in all the functions below
>> but the read operation is still a u32, leaving to the compiler the task of
>> stripping the top 16 bit.
>>
>> My suggestion is to go back to a u32 for zx2967_wdt_writel() but to AND 'val'
>> with 0x0000ffff before OR'ing it with ZX2967_WDT_WRITEKEY.
>>
>
> For the record, I am fine either way, including not masking at all;
> I considered that a theoretic problem that only applies if reading
> a register can return a value other than 0 in the upper 16 bit.
> So, ultimately, this patch series is now waiting for your Ack.
>
Now that there is sufficient comments in the code to understand what's
going on, I'm also fine either way. As long as
zx2967_wdt_readl/writel() are consistent with one another.
Mathieu
> Guenter
^ permalink raw reply [flat|nested] 19+ messages in thread* [PATCH v8 3/3] watchdog: zx2967: add watchdog controller driver for ZTE's zx2967 family
@ 2017-02-03 22:48 ` Mathieu Poirier
0 siblings, 0 replies; 19+ messages in thread
From: Mathieu Poirier @ 2017-02-03 22:48 UTC (permalink / raw)
To: linux-arm-kernel
On 3 February 2017 at 10:07, Guenter Roeck <linux@roeck-us.net> wrote:
> On Fri, Feb 03, 2017 at 09:02:57AM -0700, Mathieu Poirier wrote:
>> On Fri, Feb 03, 2017 at 11:22:20AM +0800, Baoyou Xie wrote:
>> > This patch adds watchdog controller driver for ZTE's zx2967 family.
>> >
>> > Signed-off-by: Baoyou Xie <baoyou.xie@linaro.org>
>> > ---
>> > drivers/watchdog/Kconfig | 10 ++
>> > drivers/watchdog/Makefile | 1 +
>> > drivers/watchdog/zx2967_wdt.c | 285 ++++++++++++++++++++++++++++++++++++++++++
>> > 3 files changed, 296 insertions(+)
>> > create mode 100644 drivers/watchdog/zx2967_wdt.c
>> >
>> > diff --git a/drivers/watchdog/Kconfig b/drivers/watchdog/Kconfig
>> > index acb00b5..05093a2 100644
>> > --- a/drivers/watchdog/Kconfig
>> > +++ b/drivers/watchdog/Kconfig
>> > @@ -714,6 +714,16 @@ config ASPEED_WATCHDOG
>> > To compile this driver as a module, choose M here: the
>> > module will be called aspeed_wdt.
>> >
>> > +config ZX2967_WATCHDOG
>> > + tristate "ZTE zx2967 SoCs watchdog support"
>> > + depends on ARCH_ZX
>> > + select WATCHDOG_CORE
>> > + help
>> > + Say Y here to include support for the watchdog timer
>> > + in ZTE zx2967 SoCs.
>> > + To compile this driver as a module, choose M here: the
>> > + module will be called zx2967_wdt.
>> > +
>> > # AVR32 Architecture
>> >
>> > config AT32AP700X_WDT
>> > diff --git a/drivers/watchdog/Makefile b/drivers/watchdog/Makefile
>> > index 0c3d35e..bf2d296 100644
>> > --- a/drivers/watchdog/Makefile
>> > +++ b/drivers/watchdog/Makefile
>> > @@ -82,6 +82,7 @@ obj-$(CONFIG_BCM7038_WDT) += bcm7038_wdt.o
>> > obj-$(CONFIG_ATLAS7_WATCHDOG) += atlas7_wdt.o
>> > obj-$(CONFIG_RENESAS_WDT) += renesas_wdt.o
>> > obj-$(CONFIG_ASPEED_WATCHDOG) += aspeed_wdt.o
>> > +obj-$(CONFIG_ZX2967_WATCHDOG) += zx2967_wdt.o
>> >
>> > # AVR32 Architecture
>> > obj-$(CONFIG_AT32AP700X_WDT) += at32ap700x_wdt.o
>> > diff --git a/drivers/watchdog/zx2967_wdt.c b/drivers/watchdog/zx2967_wdt.c
>> > new file mode 100644
>> > index 0000000..2daaca2
>> > --- /dev/null
>> > +++ b/drivers/watchdog/zx2967_wdt.c
>> > @@ -0,0 +1,285 @@
>> > +/*
>> > + * watchdog driver for ZTE's zx2967 family
>> > + *
>> > + * Copyright (C) 2017 ZTE Ltd.
>> > + *
>> > + * Author: Baoyou Xie <baoyou.xie@linaro.org>
>> > + *
>> > + * License terms: GNU General Public License (GPL) version 2
>> > + */
>> > +
>> > +#include <linux/clk.h>
>> > +#include <linux/io.h>
>> > +#include <linux/mfd/syscon.h>
>> > +#include <linux/module.h>
>> > +#include <linux/of_address.h>
>> > +#include <linux/platform_device.h>
>> > +#include <linux/regmap.h>
>> > +#include <linux/reset.h>
>> > +#include <linux/watchdog.h>
>> > +
>> > +#define ZX2967_WDT_CFG_REG 0x4
>> > +#define ZX2967_WDT_LOAD_REG 0x8
>> > +#define ZX2967_WDT_REFRESH_REG 0x18
>> > +#define ZX2967_WDT_START_REG 0x1c
>> > +
>> > +#define ZX2967_WDT_REFRESH_MASK 0x3f
>> > +
>> > +#define ZX2967_WDT_CFG_DIV(n) ((((n) & 0xff) - 1) << 8)
>> > +#define ZX2967_WDT_START_EN 0x1
>> > +
>> > +/*
>> > + * Hardware magic number.
>> > + * When watchdog reg is written, the lowest 16 bits are valid, but
>> > + * the highest 16 bits should be always this number.
>> > + */
>>
>> Thanks for the explanation, much better now.
>>
>> > +#define ZX2967_WDT_WRITEKEY (0x1234 << 16)
>> > +
>> > +#define ZX2967_WDT_DIV_DEFAULT 16
>> > +#define ZX2967_WDT_DEFAULT_TIMEOUT 32
>> > +#define ZX2967_WDT_MIN_TIMEOUT 1
>> > +#define ZX2967_WDT_MAX_TIMEOUT 524
>> > +#define ZX2967_WDT_MAX_COUNT 0xffff
>> > +
>> > +#define ZX2967_WDT_CLK_FREQ 0x8000
>> > +
>> > +#define ZX2967_WDT_FLAG_REBOOT_MON BIT(0)
>> > +
>> > +struct zx2967_wdt {
>> > + struct watchdog_device wdt_device;
>> > + void __iomem *reg_base;
>> > + struct clk *clock;
>> > +};
>> > +
>> > +static inline u32 zx2967_wdt_readl(struct zx2967_wdt *wdt, u16 reg)
>> > +{
>> > + return readl_relaxed(wdt->reg_base + reg);
>> > +}
>> > +
>> > +static inline void zx2967_wdt_writel(struct zx2967_wdt *wdt, u16 reg, u16 val)
>> > +{
>> > + writel_relaxed(val | ZX2967_WDT_WRITEKEY, wdt->reg_base + reg);
>> > +}
>>
>> You were correct with the u32 type. My comment was about making sure the value
>> of the value given to the function wasn't bigger than 65535 (0xffff), which
>> would have been corrupted by the OR'ing with ZX2967_WDT_WRITEKEY.
>>
>> Going with a u16 forces you to manipulate u16 types in all the functions below
>> but the read operation is still a u32, leaving to the compiler the task of
>> stripping the top 16 bit.
>>
>> My suggestion is to go back to a u32 for zx2967_wdt_writel() but to AND 'val'
>> with 0x0000ffff before OR'ing it with ZX2967_WDT_WRITEKEY.
>>
>
> For the record, I am fine either way, including not masking at all;
> I considered that a theoretic problem that only applies if reading
> a register can return a value other than 0 in the upper 16 bit.
> So, ultimately, this patch series is now waiting for your Ack.
>
Now that there is sufficient comments in the code to understand what's
going on, I'm also fine either way. As long as
zx2967_wdt_readl/writel() are consistent with one another.
Mathieu
> Guenter
^ permalink raw reply [flat|nested] 19+ messages in thread* Re: [PATCH v8 3/3] watchdog: zx2967: add watchdog controller driver for ZTE's zx2967 family
@ 2017-02-03 22:48 ` Mathieu Poirier
0 siblings, 0 replies; 19+ messages in thread
From: Mathieu Poirier @ 2017-02-03 22:48 UTC (permalink / raw)
To: Guenter Roeck
Cc: Baoyou Xie, Jun Nie, wim, Rob Herring, Mark Rutland,
linux-arm-kernel, linux-watchdog, devicetree, linux-kernel,
Shawn Guo, xie.baoyou, chen.chaokai, wang.qiang01
On 3 February 2017 at 10:07, Guenter Roeck <linux@roeck-us.net> wrote:
> On Fri, Feb 03, 2017 at 09:02:57AM -0700, Mathieu Poirier wrote:
>> On Fri, Feb 03, 2017 at 11:22:20AM +0800, Baoyou Xie wrote:
>> > This patch adds watchdog controller driver for ZTE's zx2967 family.
>> >
>> > Signed-off-by: Baoyou Xie <baoyou.xie@linaro.org>
>> > ---
>> > drivers/watchdog/Kconfig | 10 ++
>> > drivers/watchdog/Makefile | 1 +
>> > drivers/watchdog/zx2967_wdt.c | 285 ++++++++++++++++++++++++++++++++++++++++++
>> > 3 files changed, 296 insertions(+)
>> > create mode 100644 drivers/watchdog/zx2967_wdt.c
>> >
>> > diff --git a/drivers/watchdog/Kconfig b/drivers/watchdog/Kconfig
>> > index acb00b5..05093a2 100644
>> > --- a/drivers/watchdog/Kconfig
>> > +++ b/drivers/watchdog/Kconfig
>> > @@ -714,6 +714,16 @@ config ASPEED_WATCHDOG
>> > To compile this driver as a module, choose M here: the
>> > module will be called aspeed_wdt.
>> >
>> > +config ZX2967_WATCHDOG
>> > + tristate "ZTE zx2967 SoCs watchdog support"
>> > + depends on ARCH_ZX
>> > + select WATCHDOG_CORE
>> > + help
>> > + Say Y here to include support for the watchdog timer
>> > + in ZTE zx2967 SoCs.
>> > + To compile this driver as a module, choose M here: the
>> > + module will be called zx2967_wdt.
>> > +
>> > # AVR32 Architecture
>> >
>> > config AT32AP700X_WDT
>> > diff --git a/drivers/watchdog/Makefile b/drivers/watchdog/Makefile
>> > index 0c3d35e..bf2d296 100644
>> > --- a/drivers/watchdog/Makefile
>> > +++ b/drivers/watchdog/Makefile
>> > @@ -82,6 +82,7 @@ obj-$(CONFIG_BCM7038_WDT) += bcm7038_wdt.o
>> > obj-$(CONFIG_ATLAS7_WATCHDOG) += atlas7_wdt.o
>> > obj-$(CONFIG_RENESAS_WDT) += renesas_wdt.o
>> > obj-$(CONFIG_ASPEED_WATCHDOG) += aspeed_wdt.o
>> > +obj-$(CONFIG_ZX2967_WATCHDOG) += zx2967_wdt.o
>> >
>> > # AVR32 Architecture
>> > obj-$(CONFIG_AT32AP700X_WDT) += at32ap700x_wdt.o
>> > diff --git a/drivers/watchdog/zx2967_wdt.c b/drivers/watchdog/zx2967_wdt.c
>> > new file mode 100644
>> > index 0000000..2daaca2
>> > --- /dev/null
>> > +++ b/drivers/watchdog/zx2967_wdt.c
>> > @@ -0,0 +1,285 @@
>> > +/*
>> > + * watchdog driver for ZTE's zx2967 family
>> > + *
>> > + * Copyright (C) 2017 ZTE Ltd.
>> > + *
>> > + * Author: Baoyou Xie <baoyou.xie@linaro.org>
>> > + *
>> > + * License terms: GNU General Public License (GPL) version 2
>> > + */
>> > +
>> > +#include <linux/clk.h>
>> > +#include <linux/io.h>
>> > +#include <linux/mfd/syscon.h>
>> > +#include <linux/module.h>
>> > +#include <linux/of_address.h>
>> > +#include <linux/platform_device.h>
>> > +#include <linux/regmap.h>
>> > +#include <linux/reset.h>
>> > +#include <linux/watchdog.h>
>> > +
>> > +#define ZX2967_WDT_CFG_REG 0x4
>> > +#define ZX2967_WDT_LOAD_REG 0x8
>> > +#define ZX2967_WDT_REFRESH_REG 0x18
>> > +#define ZX2967_WDT_START_REG 0x1c
>> > +
>> > +#define ZX2967_WDT_REFRESH_MASK 0x3f
>> > +
>> > +#define ZX2967_WDT_CFG_DIV(n) ((((n) & 0xff) - 1) << 8)
>> > +#define ZX2967_WDT_START_EN 0x1
>> > +
>> > +/*
>> > + * Hardware magic number.
>> > + * When watchdog reg is written, the lowest 16 bits are valid, but
>> > + * the highest 16 bits should be always this number.
>> > + */
>>
>> Thanks for the explanation, much better now.
>>
>> > +#define ZX2967_WDT_WRITEKEY (0x1234 << 16)
>> > +
>> > +#define ZX2967_WDT_DIV_DEFAULT 16
>> > +#define ZX2967_WDT_DEFAULT_TIMEOUT 32
>> > +#define ZX2967_WDT_MIN_TIMEOUT 1
>> > +#define ZX2967_WDT_MAX_TIMEOUT 524
>> > +#define ZX2967_WDT_MAX_COUNT 0xffff
>> > +
>> > +#define ZX2967_WDT_CLK_FREQ 0x8000
>> > +
>> > +#define ZX2967_WDT_FLAG_REBOOT_MON BIT(0)
>> > +
>> > +struct zx2967_wdt {
>> > + struct watchdog_device wdt_device;
>> > + void __iomem *reg_base;
>> > + struct clk *clock;
>> > +};
>> > +
>> > +static inline u32 zx2967_wdt_readl(struct zx2967_wdt *wdt, u16 reg)
>> > +{
>> > + return readl_relaxed(wdt->reg_base + reg);
>> > +}
>> > +
>> > +static inline void zx2967_wdt_writel(struct zx2967_wdt *wdt, u16 reg, u16 val)
>> > +{
>> > + writel_relaxed(val | ZX2967_WDT_WRITEKEY, wdt->reg_base + reg);
>> > +}
>>
>> You were correct with the u32 type. My comment was about making sure the value
>> of the value given to the function wasn't bigger than 65535 (0xffff), which
>> would have been corrupted by the OR'ing with ZX2967_WDT_WRITEKEY.
>>
>> Going with a u16 forces you to manipulate u16 types in all the functions below
>> but the read operation is still a u32, leaving to the compiler the task of
>> stripping the top 16 bit.
>>
>> My suggestion is to go back to a u32 for zx2967_wdt_writel() but to AND 'val'
>> with 0x0000ffff before OR'ing it with ZX2967_WDT_WRITEKEY.
>>
>
> For the record, I am fine either way, including not masking at all;
> I considered that a theoretic problem that only applies if reading
> a register can return a value other than 0 in the upper 16 bit.
> So, ultimately, this patch series is now waiting for your Ack.
>
Now that there is sufficient comments in the code to understand what's
going on, I'm also fine either way. As long as
zx2967_wdt_readl/writel() are consistent with one another.
Mathieu
> Guenter
^ permalink raw reply [flat|nested] 19+ messages in thread* Re: [PATCH v8 3/3] watchdog: zx2967: add watchdog controller driver for ZTE's zx2967 family
@ 2017-02-03 22:48 ` Mathieu Poirier
0 siblings, 0 replies; 19+ messages in thread
From: Mathieu Poirier @ 2017-02-03 22:48 UTC (permalink / raw)
To: Guenter Roeck
Cc: Baoyou Xie, Jun Nie, wim-IQzOog9fTRqzQB+pC5nmwQ, Rob Herring,
Mark Rutland, linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r,
linux-watchdog-u79uwXL29TY76Z2rM5mHXA,
devicetree-u79uwXL29TY76Z2rM5mHXA,
linux-kernel-u79uwXL29TY76Z2rM5mHXA, Shawn Guo, xie.baoyou,
chen.chaokai-Th6q7B73Y6EnDS1+zs4M5A,
wang.qiang01-Th6q7B73Y6EnDS1+zs4M5A
On 3 February 2017 at 10:07, Guenter Roeck <linux-0h96xk9xTtrk1uMJSBkQmQ@public.gmane.org> wrote:
> On Fri, Feb 03, 2017 at 09:02:57AM -0700, Mathieu Poirier wrote:
>> On Fri, Feb 03, 2017 at 11:22:20AM +0800, Baoyou Xie wrote:
>> > This patch adds watchdog controller driver for ZTE's zx2967 family.
>> >
>> > Signed-off-by: Baoyou Xie <baoyou.xie-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>
>> > ---
>> > drivers/watchdog/Kconfig | 10 ++
>> > drivers/watchdog/Makefile | 1 +
>> > drivers/watchdog/zx2967_wdt.c | 285 ++++++++++++++++++++++++++++++++++++++++++
>> > 3 files changed, 296 insertions(+)
>> > create mode 100644 drivers/watchdog/zx2967_wdt.c
>> >
>> > diff --git a/drivers/watchdog/Kconfig b/drivers/watchdog/Kconfig
>> > index acb00b5..05093a2 100644
>> > --- a/drivers/watchdog/Kconfig
>> > +++ b/drivers/watchdog/Kconfig
>> > @@ -714,6 +714,16 @@ config ASPEED_WATCHDOG
>> > To compile this driver as a module, choose M here: the
>> > module will be called aspeed_wdt.
>> >
>> > +config ZX2967_WATCHDOG
>> > + tristate "ZTE zx2967 SoCs watchdog support"
>> > + depends on ARCH_ZX
>> > + select WATCHDOG_CORE
>> > + help
>> > + Say Y here to include support for the watchdog timer
>> > + in ZTE zx2967 SoCs.
>> > + To compile this driver as a module, choose M here: the
>> > + module will be called zx2967_wdt.
>> > +
>> > # AVR32 Architecture
>> >
>> > config AT32AP700X_WDT
>> > diff --git a/drivers/watchdog/Makefile b/drivers/watchdog/Makefile
>> > index 0c3d35e..bf2d296 100644
>> > --- a/drivers/watchdog/Makefile
>> > +++ b/drivers/watchdog/Makefile
>> > @@ -82,6 +82,7 @@ obj-$(CONFIG_BCM7038_WDT) += bcm7038_wdt.o
>> > obj-$(CONFIG_ATLAS7_WATCHDOG) += atlas7_wdt.o
>> > obj-$(CONFIG_RENESAS_WDT) += renesas_wdt.o
>> > obj-$(CONFIG_ASPEED_WATCHDOG) += aspeed_wdt.o
>> > +obj-$(CONFIG_ZX2967_WATCHDOG) += zx2967_wdt.o
>> >
>> > # AVR32 Architecture
>> > obj-$(CONFIG_AT32AP700X_WDT) += at32ap700x_wdt.o
>> > diff --git a/drivers/watchdog/zx2967_wdt.c b/drivers/watchdog/zx2967_wdt.c
>> > new file mode 100644
>> > index 0000000..2daaca2
>> > --- /dev/null
>> > +++ b/drivers/watchdog/zx2967_wdt.c
>> > @@ -0,0 +1,285 @@
>> > +/*
>> > + * watchdog driver for ZTE's zx2967 family
>> > + *
>> > + * Copyright (C) 2017 ZTE Ltd.
>> > + *
>> > + * Author: Baoyou Xie <baoyou.xie-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>
>> > + *
>> > + * License terms: GNU General Public License (GPL) version 2
>> > + */
>> > +
>> > +#include <linux/clk.h>
>> > +#include <linux/io.h>
>> > +#include <linux/mfd/syscon.h>
>> > +#include <linux/module.h>
>> > +#include <linux/of_address.h>
>> > +#include <linux/platform_device.h>
>> > +#include <linux/regmap.h>
>> > +#include <linux/reset.h>
>> > +#include <linux/watchdog.h>
>> > +
>> > +#define ZX2967_WDT_CFG_REG 0x4
>> > +#define ZX2967_WDT_LOAD_REG 0x8
>> > +#define ZX2967_WDT_REFRESH_REG 0x18
>> > +#define ZX2967_WDT_START_REG 0x1c
>> > +
>> > +#define ZX2967_WDT_REFRESH_MASK 0x3f
>> > +
>> > +#define ZX2967_WDT_CFG_DIV(n) ((((n) & 0xff) - 1) << 8)
>> > +#define ZX2967_WDT_START_EN 0x1
>> > +
>> > +/*
>> > + * Hardware magic number.
>> > + * When watchdog reg is written, the lowest 16 bits are valid, but
>> > + * the highest 16 bits should be always this number.
>> > + */
>>
>> Thanks for the explanation, much better now.
>>
>> > +#define ZX2967_WDT_WRITEKEY (0x1234 << 16)
>> > +
>> > +#define ZX2967_WDT_DIV_DEFAULT 16
>> > +#define ZX2967_WDT_DEFAULT_TIMEOUT 32
>> > +#define ZX2967_WDT_MIN_TIMEOUT 1
>> > +#define ZX2967_WDT_MAX_TIMEOUT 524
>> > +#define ZX2967_WDT_MAX_COUNT 0xffff
>> > +
>> > +#define ZX2967_WDT_CLK_FREQ 0x8000
>> > +
>> > +#define ZX2967_WDT_FLAG_REBOOT_MON BIT(0)
>> > +
>> > +struct zx2967_wdt {
>> > + struct watchdog_device wdt_device;
>> > + void __iomem *reg_base;
>> > + struct clk *clock;
>> > +};
>> > +
>> > +static inline u32 zx2967_wdt_readl(struct zx2967_wdt *wdt, u16 reg)
>> > +{
>> > + return readl_relaxed(wdt->reg_base + reg);
>> > +}
>> > +
>> > +static inline void zx2967_wdt_writel(struct zx2967_wdt *wdt, u16 reg, u16 val)
>> > +{
>> > + writel_relaxed(val | ZX2967_WDT_WRITEKEY, wdt->reg_base + reg);
>> > +}
>>
>> You were correct with the u32 type. My comment was about making sure the value
>> of the value given to the function wasn't bigger than 65535 (0xffff), which
>> would have been corrupted by the OR'ing with ZX2967_WDT_WRITEKEY.
>>
>> Going with a u16 forces you to manipulate u16 types in all the functions below
>> but the read operation is still a u32, leaving to the compiler the task of
>> stripping the top 16 bit.
>>
>> My suggestion is to go back to a u32 for zx2967_wdt_writel() but to AND 'val'
>> with 0x0000ffff before OR'ing it with ZX2967_WDT_WRITEKEY.
>>
>
> For the record, I am fine either way, including not masking at all;
> I considered that a theoretic problem that only applies if reading
> a register can return a value other than 0 in the upper 16 bit.
> So, ultimately, this patch series is now waiting for your Ack.
>
Now that there is sufficient comments in the code to understand what's
going on, I'm also fine either way. As long as
zx2967_wdt_readl/writel() are consistent with one another.
Mathieu
> Guenter
--
To unsubscribe from this list: send the line "unsubscribe devicetree" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
^ permalink raw reply [flat|nested] 19+ messages in thread* Re: [PATCH v8 3/3] watchdog: zx2967: add watchdog controller driver for ZTE's zx2967 family
2017-02-03 22:48 ` Mathieu Poirier
` (2 preceding siblings ...)
(?)
@ 2017-02-04 0:29 ` Baoyou Xie
-1 siblings, 0 replies; 19+ messages in thread
From: Baoyou Xie @ 2017-02-04 0:29 UTC (permalink / raw)
To: Mathieu Poirier
Cc: Guenter Roeck, Jun Nie, wim, Rob Herring, Mark Rutland,
linux-arm-kernel, linux-watchdog, devicetree, linux-kernel,
Shawn Guo, xie.baoyou, chen.chaokai, wang.qiang01
[-- Attachment #1: Type: text/plain, Size: 6023 bytes --]
On 4 February 2017 at 06:48, Mathieu Poirier <mathieu.poirier@linaro.org>
wrote:
> On 3 February 2017 at 10:07, Guenter Roeck <linux@roeck-us.net> wrote:
> > On Fri, Feb 03, 2017 at 09:02:57AM -0700, Mathieu Poirier wrote:
> >> On Fri, Feb 03, 2017 at 11:22:20AM +0800, Baoyou Xie wrote:
> >> > This patch adds watchdog controller driver for ZTE's zx2967 family.
> >> >
> >> > Signed-off-by: Baoyou Xie <baoyou.xie@linaro.org>
> >> > ---
> >> > drivers/watchdog/Kconfig | 10 ++
> >> > drivers/watchdog/Makefile | 1 +
> >> > drivers/watchdog/zx2967_wdt.c | 285 ++++++++++++++++++++++++++++++
> ++++++++++++
> >> > 3 files changed, 296 insertions(+)
> >> > create mode 100644 drivers/watchdog/zx2967_wdt.c
> >> >
> >> > diff --git a/drivers/watchdog/Kconfig b/drivers/watchdog/Kconfig
> >> > index acb00b5..05093a2 100644
> >> > --- a/drivers/watchdog/Kconfig
> >> > +++ b/drivers/watchdog/Kconfig
> >> > @@ -714,6 +714,16 @@ config ASPEED_WATCHDOG
> >> > To compile this driver as a module, choose M here: the
> >> > module will be called aspeed_wdt.
> >> >
> >> > +config ZX2967_WATCHDOG
> >> > + tristate "ZTE zx2967 SoCs watchdog support"
> >> > + depends on ARCH_ZX
> >> > + select WATCHDOG_CORE
> >> > + help
> >> > + Say Y here to include support for the watchdog timer
> >> > + in ZTE zx2967 SoCs.
> >> > + To compile this driver as a module, choose M here: the
> >> > + module will be called zx2967_wdt.
> >> > +
> >> > # AVR32 Architecture
> >> >
> >> > config AT32AP700X_WDT
> >> > diff --git a/drivers/watchdog/Makefile b/drivers/watchdog/Makefile
> >> > index 0c3d35e..bf2d296 100644
> >> > --- a/drivers/watchdog/Makefile
> >> > +++ b/drivers/watchdog/Makefile
> >> > @@ -82,6 +82,7 @@ obj-$(CONFIG_BCM7038_WDT) += bcm7038_wdt.o
> >> > obj-$(CONFIG_ATLAS7_WATCHDOG) += atlas7_wdt.o
> >> > obj-$(CONFIG_RENESAS_WDT) += renesas_wdt.o
> >> > obj-$(CONFIG_ASPEED_WATCHDOG) += aspeed_wdt.o
> >> > +obj-$(CONFIG_ZX2967_WATCHDOG) += zx2967_wdt.o
> >> >
> >> > # AVR32 Architecture
> >> > obj-$(CONFIG_AT32AP700X_WDT) += at32ap700x_wdt.o
> >> > diff --git a/drivers/watchdog/zx2967_wdt.c
> b/drivers/watchdog/zx2967_wdt.c
> >> > new file mode 100644
> >> > index 0000000..2daaca2
> >> > --- /dev/null
> >> > +++ b/drivers/watchdog/zx2967_wdt.c
> >> > @@ -0,0 +1,285 @@
> >> > +/*
> >> > + * watchdog driver for ZTE's zx2967 family
> >> > + *
> >> > + * Copyright (C) 2017 ZTE Ltd.
> >> > + *
> >> > + * Author: Baoyou Xie <baoyou.xie@linaro.org>
> >> > + *
> >> > + * License terms: GNU General Public License (GPL) version 2
> >> > + */
> >> > +
> >> > +#include <linux/clk.h>
> >> > +#include <linux/io.h>
> >> > +#include <linux/mfd/syscon.h>
> >> > +#include <linux/module.h>
> >> > +#include <linux/of_address.h>
> >> > +#include <linux/platform_device.h>
> >> > +#include <linux/regmap.h>
> >> > +#include <linux/reset.h>
> >> > +#include <linux/watchdog.h>
> >> > +
> >> > +#define ZX2967_WDT_CFG_REG 0x4
> >> > +#define ZX2967_WDT_LOAD_REG 0x8
> >> > +#define ZX2967_WDT_REFRESH_REG 0x18
> >> > +#define ZX2967_WDT_START_REG 0x1c
> >> > +
> >> > +#define ZX2967_WDT_REFRESH_MASK 0x3f
> >> > +
> >> > +#define ZX2967_WDT_CFG_DIV(n) ((((n) & 0xff) -
> 1) << 8)
> >> > +#define ZX2967_WDT_START_EN 0x1
> >> > +
> >> > +/*
> >> > + * Hardware magic number.
> >> > + * When watchdog reg is written, the lowest 16 bits are valid, but
> >> > + * the highest 16 bits should be always this number.
> >> > + */
> >>
> >> Thanks for the explanation, much better now.
> >>
> >> > +#define ZX2967_WDT_WRITEKEY (0x1234 << 16)
> >> > +
> >> > +#define ZX2967_WDT_DIV_DEFAULT 16
> >> > +#define ZX2967_WDT_DEFAULT_TIMEOUT 32
> >> > +#define ZX2967_WDT_MIN_TIMEOUT 1
> >> > +#define ZX2967_WDT_MAX_TIMEOUT 524
> >> > +#define ZX2967_WDT_MAX_COUNT 0xffff
> >> > +
> >> > +#define ZX2967_WDT_CLK_FREQ 0x8000
> >> > +
> >> > +#define ZX2967_WDT_FLAG_REBOOT_MON BIT(0)
> >> > +
> >> > +struct zx2967_wdt {
> >> > + struct watchdog_device wdt_device;
> >> > + void __iomem *reg_base;
> >> > + struct clk *clock;
> >> > +};
> >> > +
> >> > +static inline u32 zx2967_wdt_readl(struct zx2967_wdt *wdt, u16 reg)
> >> > +{
> >> > + return readl_relaxed(wdt->reg_base + reg);
> >> > +}
> >> > +
> >> > +static inline void zx2967_wdt_writel(struct zx2967_wdt *wdt, u16
> reg, u16 val)
> >> > +{
> >> > + writel_relaxed(val | ZX2967_WDT_WRITEKEY, wdt->reg_base + reg);
> >> > +}
> >>
> >> You were correct with the u32 type. My comment was about making sure
> the value
> >> of the value given to the function wasn't bigger than 65535 (0xffff),
> which
> >> would have been corrupted by the OR'ing with ZX2967_WDT_WRITEKEY.
> >>
> >> Going with a u16 forces you to manipulate u16 types in all the
> functions below
> >> but the read operation is still a u32, leaving to the compiler the task
> of
> >> stripping the top 16 bit.
> >>
> >> My suggestion is to go back to a u32 for zx2967_wdt_writel() but to AND
> 'val'
> >> with 0x0000ffff before OR'ing it with ZX2967_WDT_WRITEKEY.
> >>
> >
> > For the record, I am fine either way, including not masking at all;
> > I considered that a theoretic problem that only applies if reading
> > a register can return a value other than 0 in the upper 16 bit.
> > So, ultimately, this patch series is now waiting for your Ack.
> >
>
> Now that there is sufficient comments in the code to understand what's
> going on, I'm also fine either way. As long as
> zx2967_wdt_readl/writel() are consistent with one another.
>
>
Please wait for my next version patch. I will modify it with u32 for
zx2967_wdt_writel() but to AND 'val'
with 0x0000ffff before OR'ing it with ZX2967_WDT_WRITEKEY.
> Mathieu
>
> > Guenter
>
[-- Attachment #2: Type: text/html, Size: 8639 bytes --]
^ permalink raw reply [flat|nested] 19+ messages in thread