* Re: [alsa-devel] [PATCH v2 2/4] watchdog: mtk_wdt: mt8183: Add reset controller
2019-09-27 10:31 ` [alsa-devel] [PATCH v2 2/4] watchdog: mtk_wdt: mt8183: Add reset controller Jiaxin Yu
@ 2019-09-28 17:49 ` Guenter Roeck
2019-09-30 8:17 ` Yingjoe Chen
2019-10-03 13:49 ` Guenter Roeck
2019-10-05 5:50 ` Yingjoe Chen
2 siblings, 1 reply; 16+ messages in thread
From: Guenter Roeck @ 2019-09-28 17:49 UTC (permalink / raw)
To: Jiaxin Yu
Cc: mark.rutland, alsa-devel, yong.liang, lgirdwood, robh+dt,
tzungbi, broonie, linux-mediatek, eason.yen, wim,
linux-arm-kernel
On Fri, Sep 27, 2019 at 06:31:55PM +0800, Jiaxin Yu wrote:
> From: "yong.liang" <yong.liang@mediatek.com>
>
> Provide assert/deassert/reset API in watchdog driver.
> Register reset controller for toprgu device in watchdog probe.
>
> Signed-off-by: yong.liang <yong.liang@mediatek.com>
> ---
> drivers/watchdog/Kconfig | 1 +
> drivers/watchdog/mtk_wdt.c | 110 ++++++++++++++++++++++++++++++++++++-
> 2 files changed, 110 insertions(+), 1 deletion(-)
>
> diff --git a/drivers/watchdog/Kconfig b/drivers/watchdog/Kconfig
> index 2e07caab9db2..629249fe5305 100644
> --- a/drivers/watchdog/Kconfig
> +++ b/drivers/watchdog/Kconfig
> @@ -717,6 +717,7 @@ config MEDIATEK_WATCHDOG
> tristate "Mediatek SoCs watchdog support"
> depends on ARCH_MEDIATEK || COMPILE_TEST
> select WATCHDOG_CORE
> + select RESET_CONTROLLER
> help
> Say Y here to include support for the watchdog timer
> in Mediatek SoCs.
> diff --git a/drivers/watchdog/mtk_wdt.c b/drivers/watchdog/mtk_wdt.c
> index 9c3d0033260d..660fb0e48d8e 100644
> --- a/drivers/watchdog/mtk_wdt.c
> +++ b/drivers/watchdog/mtk_wdt.c
> @@ -20,6 +20,10 @@
> #include <linux/types.h>
> #include <linux/watchdog.h>
> #include <linux/delay.h>
> +#include <linux/reset-controller.h>
> +#include <linux/slab.h>
> +#include <linux/reset.h>
> +#include <linux/of_device.h>
>
> #define WDT_MAX_TIMEOUT 31
> #define WDT_MIN_TIMEOUT 1
> @@ -44,17 +48,113 @@
> #define WDT_SWRST 0x14
> #define WDT_SWRST_KEY 0x1209
>
> +#define WDT_SWSYSRST 0x18U
> +#define WDT_SWSYS_RST_KEY 0x88000000
> +
> #define DRV_NAME "mtk-wdt"
> #define DRV_VERSION "1.0"
>
> static bool nowayout = WATCHDOG_NOWAYOUT;
> static unsigned int timeout;
>
> +struct toprgu_reset {
> + spinlock_t lock; /* Protects reset_controller access */
> + void __iomem *toprgu_swrst_base;
> + int regofs;
> + struct reset_controller_dev rcdev;
> +};
> +
> struct mtk_wdt_dev {
> struct watchdog_device wdt_dev;
> void __iomem *wdt_base;
> + struct toprgu_reset reset_controller;
> + const struct mtk_wdt_compatible *dev_comp;
> +};
> +
> +struct mtk_wdt_compatible {
> + int sw_rst_num;
> +};
> +
> +static int toprgu_reset_assert(struct reset_controller_dev *rcdev,
> + unsigned long id)
> +{
> + unsigned int tmp;
> + unsigned long flags;
> + struct toprgu_reset *data = container_of(rcdev,
> + struct toprgu_reset, rcdev);
> +
> + spin_lock_irqsave(&data->lock, flags);
> +
> + tmp = __raw_readl(data->toprgu_swrst_base + data->regofs);
> + tmp |= BIT(id);
> + tmp |= WDT_SWSYS_RST_KEY;
> + writel(tmp, data->toprgu_swrst_base + data->regofs);
> +
> + spin_unlock_irqrestore(&data->lock, flags);
> +
> + return 0;
> +}
> +
> +static int toprgu_reset_deassert(struct reset_controller_dev *rcdev,
> + unsigned long id)
> +{
> + unsigned int tmp;
> + unsigned long flags;
> + struct toprgu_reset *data = container_of(rcdev,
> + struct toprgu_reset, rcdev);
> +
> + spin_lock_irqsave(&data->lock, flags);
> +
> + tmp = __raw_readl(data->toprgu_swrst_base + data->regofs);
> + tmp &= ~BIT(id);
> + tmp |= WDT_SWSYS_RST_KEY;
> + writel(tmp, data->toprgu_swrst_base + data->regofs);
> +
> + spin_unlock_irqrestore(&data->lock, flags);
> +
> + return 0;
> +}
> +
> +static int toprgu_reset(struct reset_controller_dev *rcdev,
> + unsigned long id)
> +{
> + int ret;
> +
> + ret = toprgu_reset_assert(rcdev, id);
> + if (ret)
> + return ret;
> +
> + return toprgu_reset_deassert(rcdev, id);
> +}
> +
> +static struct reset_control_ops toprgu_reset_ops = {
> + .assert = toprgu_reset_assert,
> + .deassert = toprgu_reset_deassert,
> + .reset = toprgu_reset,
> };
>
> +static void toprgu_register_reset_controller(struct platform_device *pdev,
> + int regofs)
> +{
> + int ret;
> + struct mtk_wdt_dev *mtk_wdt = platform_get_drvdata(pdev);
> +
> + spin_lock_init(&mtk_wdt->reset_controller.lock);
> +
> + mtk_wdt->dev_comp = of_device_get_match_data(&pdev->dev);
> + mtk_wdt->reset_controller.toprgu_swrst_base = mtk_wdt->wdt_base;
> + mtk_wdt->reset_controller.regofs = regofs;
> + mtk_wdt->reset_controller.rcdev.owner = THIS_MODULE;
> + mtk_wdt->reset_controller.rcdev.nr_resets =
> + mtk_wdt->dev_comp->sw_rst_num;
> + mtk_wdt->reset_controller.rcdev.ops = &toprgu_reset_ops;
> + mtk_wdt->reset_controller.rcdev.of_node = pdev->dev.of_node;
> + ret = reset_controller_register(&mtk_wdt->reset_controller.rcdev);
> + if (ret != 0)
> + dev_err(&pdev->dev,
> + "couldn't register wdt reset controller: %d\n", ret);
> +}
> +
> static int mtk_wdt_restart(struct watchdog_device *wdt_dev,
> unsigned long action, void *data)
> {
> @@ -187,9 +287,12 @@ static int mtk_wdt_probe(struct platform_device *pdev)
> if (unlikely(err))
> return err;
>
> - dev_info(dev, "Watchdog enabled (timeout=%d sec, nowayout=%d)\n",
> + dev_info(&pdev->dev, "Watchdog enabled (timeout=%d sec, nowayout=%d)\n",
> mtk_wdt->wdt_dev.timeout, nowayout);
>
> + mtk_wdt->dev_comp = of_device_get_match_data(&pdev->dev);
> + if (mtk_wdt->dev_comp)
> + toprgu_register_reset_controller(pdev, WDT_SWSYSRST);
Please explain why you can not use the watchdog device built-in support
for handling system resets.
Guenter
> return 0;
> }
>
> @@ -217,7 +320,12 @@ static int mtk_wdt_resume(struct device *dev)
> }
> #endif
>
> +static const struct mtk_wdt_compatible mt8183_compat = {
> + .sw_rst_num = 18,
> +};
> +
> static const struct of_device_id mtk_wdt_dt_ids[] = {
> + { .compatible = "mediatek,mt8183-wdt", .data = &mt8183_compat },
> { .compatible = "mediatek,mt6589-wdt" },
> { /* sentinel */ }
> };
> --
> 2.18.0
>
_______________________________________________
Alsa-devel mailing list
Alsa-devel@alsa-project.org
https://mailman.alsa-project.org/mailman/listinfo/alsa-devel
^ permalink raw reply [flat|nested] 16+ messages in thread* Re: [alsa-devel] [PATCH v2 2/4] watchdog: mtk_wdt: mt8183: Add reset controller
2019-09-28 17:49 ` Guenter Roeck
@ 2019-09-30 8:17 ` Yingjoe Chen
0 siblings, 0 replies; 16+ messages in thread
From: Yingjoe Chen @ 2019-09-30 8:17 UTC (permalink / raw)
To: Guenter Roeck
Cc: mark.rutland, alsa-devel, wim, broonie, yong.liang, Jiaxin Yu,
lgirdwood, tzungbi, robh+dt, linux-mediatek, Philipp Zabel,
eason.yen, linux-arm-kernel
On Sat, 2019-09-28 at 10:49 -0700, Guenter Roeck wrote:
> On Fri, Sep 27, 2019 at 06:31:55PM +0800, Jiaxin Yu wrote:
> > From: "yong.liang" <yong.liang@mediatek.com>
> >
> > Provide assert/deassert/reset API in watchdog driver.
> > Register reset controller for toprgu device in watchdog probe.
> >
> > Signed-off-by: yong.liang <yong.liang@mediatek.com>
> > ---
> > drivers/watchdog/Kconfig | 1 +
> > drivers/watchdog/mtk_wdt.c | 110 ++++++++++++++++++++++++++++++++++++-
> > 2 files changed, 110 insertions(+), 1 deletion(-)
> >
> > diff --git a/drivers/watchdog/Kconfig b/drivers/watchdog/Kconfig
> > index 2e07caab9db2..629249fe5305 100644
> > --- a/drivers/watchdog/Kconfig
> > +++ b/drivers/watchdog/Kconfig
> > @@ -717,6 +717,7 @@ config MEDIATEK_WATCHDOG
> > tristate "Mediatek SoCs watchdog support"
> > depends on ARCH_MEDIATEK || COMPILE_TEST
> > select WATCHDOG_CORE
> > + select RESET_CONTROLLER
> > help
> > Say Y here to include support for the watchdog timer
> > in Mediatek SoCs.
<...snip...>
> > +static void toprgu_register_reset_controller(struct platform_device *pdev,
> > + int regofs)
> > +{
> > + int ret;
> > + struct mtk_wdt_dev *mtk_wdt = platform_get_drvdata(pdev);
> > +
> > + spin_lock_init(&mtk_wdt->reset_controller.lock);
> > +
> > + mtk_wdt->dev_comp = of_device_get_match_data(&pdev->dev);
> > + mtk_wdt->reset_controller.toprgu_swrst_base = mtk_wdt->wdt_base;
> > + mtk_wdt->reset_controller.regofs = regofs;
> > + mtk_wdt->reset_controller.rcdev.owner = THIS_MODULE;
> > + mtk_wdt->reset_controller.rcdev.nr_resets =
> > + mtk_wdt->dev_comp->sw_rst_num;
> > + mtk_wdt->reset_controller.rcdev.ops = &toprgu_reset_ops;
> > + mtk_wdt->reset_controller.rcdev.of_node = pdev->dev.of_node;
> > + ret = reset_controller_register(&mtk_wdt->reset_controller.rcdev);
> > + if (ret != 0)
> > + dev_err(&pdev->dev,
> > + "couldn't register wdt reset controller: %d\n", ret);
> > +}
> > +
> > static int mtk_wdt_restart(struct watchdog_device *wdt_dev,
> > unsigned long action, void *data)
> > {
> > @@ -187,9 +287,12 @@ static int mtk_wdt_probe(struct platform_device *pdev)
> > if (unlikely(err))
> > return err;
> >
> > - dev_info(dev, "Watchdog enabled (timeout=%d sec, nowayout=%d)\n",
> > + dev_info(&pdev->dev, "Watchdog enabled (timeout=%d sec, nowayout=%d)\n",
> > mtk_wdt->wdt_dev.timeout, nowayout);
> >
> > + mtk_wdt->dev_comp = of_device_get_match_data(&pdev->dev);
> > + if (mtk_wdt->dev_comp)
> > + toprgu_register_reset_controller(pdev, WDT_SWSYSRST);
>
> Please explain why you can not use the watchdog device built-in support
> for handling system resets.
Guenter,
This is not about system reset.
Besides watchdog, MTK toprgu module also provide sub-system (eg, audio,
camera, codec and connectivity) software reset functionality. Software
can use this to reset specific sub-system.
This patch add support for this using reset controller framework. We
follow the case of drivers/clk/mediatek/reset.c to add this
functionality in watchdog driver.
Joe.C
_______________________________________________
Alsa-devel mailing list
Alsa-devel@alsa-project.org
https://mailman.alsa-project.org/mailman/listinfo/alsa-devel
^ permalink raw reply [flat|nested] 16+ messages in thread
* Re: [alsa-devel] [PATCH v2 2/4] watchdog: mtk_wdt: mt8183: Add reset controller
2019-09-27 10:31 ` [alsa-devel] [PATCH v2 2/4] watchdog: mtk_wdt: mt8183: Add reset controller Jiaxin Yu
2019-09-28 17:49 ` Guenter Roeck
@ 2019-10-03 13:49 ` Guenter Roeck
2019-10-05 5:59 ` Yingjoe Chen
2019-10-05 5:50 ` Yingjoe Chen
2 siblings, 1 reply; 16+ messages in thread
From: Guenter Roeck @ 2019-10-03 13:49 UTC (permalink / raw)
To: Jiaxin Yu, broonie, mark.rutland, robh+dt, wim
Cc: alsa-devel, yong.liang, lgirdwood, tzungbi, linux-mediatek,
eason.yen, linux-arm-kernel
On 9/27/19 3:31 AM, Jiaxin Yu wrote:
> From: "yong.liang" <yong.liang@mediatek.com>
>
> Provide assert/deassert/reset API in watchdog driver.
> Register reset controller for toprgu device in watchdog probe.
>
> Signed-off-by: yong.liang <yong.liang@mediatek.com>
> ---
> drivers/watchdog/Kconfig | 1 +
> drivers/watchdog/mtk_wdt.c | 110 ++++++++++++++++++++++++++++++++++++-
> 2 files changed, 110 insertions(+), 1 deletion(-)
>
> diff --git a/drivers/watchdog/Kconfig b/drivers/watchdog/Kconfig
> index 2e07caab9db2..629249fe5305 100644
> --- a/drivers/watchdog/Kconfig
> +++ b/drivers/watchdog/Kconfig
> @@ -717,6 +717,7 @@ config MEDIATEK_WATCHDOG
> tristate "Mediatek SoCs watchdog support"
> depends on ARCH_MEDIATEK || COMPILE_TEST
> select WATCHDOG_CORE
> + select RESET_CONTROLLER
> help
> Say Y here to include support for the watchdog timer
> in Mediatek SoCs.
> diff --git a/drivers/watchdog/mtk_wdt.c b/drivers/watchdog/mtk_wdt.c
> index 9c3d0033260d..660fb0e48d8e 100644
> --- a/drivers/watchdog/mtk_wdt.c
> +++ b/drivers/watchdog/mtk_wdt.c
> @@ -20,6 +20,10 @@
> #include <linux/types.h>
> #include <linux/watchdog.h>
> #include <linux/delay.h>
> +#include <linux/reset-controller.h>
> +#include <linux/slab.h>
> +#include <linux/reset.h>
> +#include <linux/of_device.h>
>
> #define WDT_MAX_TIMEOUT 31
> #define WDT_MIN_TIMEOUT 1
> @@ -44,17 +48,113 @@
> #define WDT_SWRST 0x14
> #define WDT_SWRST_KEY 0x1209
>
> +#define WDT_SWSYSRST 0x18U
> +#define WDT_SWSYS_RST_KEY 0x88000000
> +
> #define DRV_NAME "mtk-wdt"
> #define DRV_VERSION "1.0"
>
> static bool nowayout = WATCHDOG_NOWAYOUT;
> static unsigned int timeout;
>
> +struct toprgu_reset {
> + spinlock_t lock; /* Protects reset_controller access */
> + void __iomem *toprgu_swrst_base;
> + int regofs;
> + struct reset_controller_dev rcdev;
> +};
> +
> struct mtk_wdt_dev {
> struct watchdog_device wdt_dev;
> void __iomem *wdt_base;
> + struct toprgu_reset reset_controller;
> + const struct mtk_wdt_compatible *dev_comp;
"dev_comp" suggests that this would be a device name. In practice,
the only value there is sw_rst_num, and the value is only
used in toprgu_register_reset_controller(). Might as well pass
it as argument and drop this pointer.
> +};
> +
> +struct mtk_wdt_compatible {
> + int sw_rst_num;
> +};
> +
"compatible" is an odd name for this structure. I would suggest
to select a more common name such as "mtk_wdt_data".
> +static int toprgu_reset_assert(struct reset_controller_dev *rcdev,
> + unsigned long id)
> +{
> + unsigned int tmp;
> + unsigned long flags;
> + struct toprgu_reset *data = container_of(rcdev,
> + struct toprgu_reset, rcdev);
> +
> + spin_lock_irqsave(&data->lock, flags);
> +
> + tmp = __raw_readl(data->toprgu_swrst_base + data->regofs);
> + tmp |= BIT(id);
> + tmp |= WDT_SWSYS_RST_KEY;
> + writel(tmp, data->toprgu_swrst_base + data->regofs);
> +
> + spin_unlock_irqrestore(&data->lock, flags);
> +
> + return 0;
> +}
> +
> +static int toprgu_reset_deassert(struct reset_controller_dev *rcdev,
> + unsigned long id)
> +{
> + unsigned int tmp;
> + unsigned long flags;
> + struct toprgu_reset *data = container_of(rcdev,
> + struct toprgu_reset, rcdev);
> +
> + spin_lock_irqsave(&data->lock, flags);
> +
> + tmp = __raw_readl(data->toprgu_swrst_base + data->regofs);
> + tmp &= ~BIT(id);
> + tmp |= WDT_SWSYS_RST_KEY;
> + writel(tmp, data->toprgu_swrst_base + data->regofs);
> +
> + spin_unlock_irqrestore(&data->lock, flags);
> +
> + return 0;
> +}
> +
> +static int toprgu_reset(struct reset_controller_dev *rcdev,
> + unsigned long id)
> +{
> + int ret;
> +
> + ret = toprgu_reset_assert(rcdev, id);
> + if (ret)
> + return ret;
> +
> + return toprgu_reset_deassert(rcdev, id);
Unless there is additional synchronization elsewhere, parallel calls
to the -> assert, and ->reset callbacks may result in the reset being
deasserted while at least one caller (the one who called the ->assert
function) believes that it is still asserted.
[ ... and if there _is_ additional synchronization elsewhere, the
local spinlock would be unnecessary ]
> +}
> +
> +static struct reset_control_ops toprgu_reset_ops = {
> + .assert = toprgu_reset_assert,
> + .deassert = toprgu_reset_deassert,
> + .reset = toprgu_reset,
> };
>
> +static void toprgu_register_reset_controller(struct platform_device *pdev,
> + int regofs)
Since there is only one well defined offset, it seems unnecessary to pass
regofs as parameter.
> +{
> + int ret;
> + struct mtk_wdt_dev *mtk_wdt = platform_get_drvdata(pdev);
> +
> + spin_lock_init(&mtk_wdt->reset_controller.lock);
> +
> + mtk_wdt->dev_comp = of_device_get_match_data(&pdev->dev);
Duplicate, and not really needed. Just pass sw_rst_num as argument.
> + mtk_wdt->reset_controller.toprgu_swrst_base = mtk_wdt->wdt_base;
> + mtk_wdt->reset_controller.regofs = regofs;
> + mtk_wdt->reset_controller.rcdev.owner = THIS_MODULE;
> + mtk_wdt->reset_controller.rcdev.nr_resets =
> + mtk_wdt->dev_comp->sw_rst_num;
> + mtk_wdt->reset_controller.rcdev.ops = &toprgu_reset_ops;
> + mtk_wdt->reset_controller.rcdev.of_node = pdev->dev.of_node;
> + ret = reset_controller_register(&mtk_wdt->reset_controller.rcdev);
> + if (ret != 0)
> + dev_err(&pdev->dev,
> + "couldn't register wdt reset controller: %d\n", ret);
> +}
> +
> static int mtk_wdt_restart(struct watchdog_device *wdt_dev,
> unsigned long action, void *data)
> {
> @@ -187,9 +287,12 @@ static int mtk_wdt_probe(struct platform_device *pdev)
> if (unlikely(err))
> return err;
>
> - dev_info(dev, "Watchdog enabled (timeout=%d sec, nowayout=%d)\n",
> + dev_info(&pdev->dev, "Watchdog enabled (timeout=%d sec, nowayout=%d)\n",
> mtk_wdt->wdt_dev.timeout, nowayout);
>
> + mtk_wdt->dev_comp = of_device_get_match_data(&pdev->dev);
> + if (mtk_wdt->dev_comp)
> + toprgu_register_reset_controller(pdev, WDT_SWSYSRST);
> return 0;
> }
>
> @@ -217,7 +320,12 @@ static int mtk_wdt_resume(struct device *dev)
> }
> #endif
>
> +static const struct mtk_wdt_compatible mt8183_compat = {
> + .sw_rst_num = 18,
Please no such magic numbers. This should be a define in an include file.
> +};
> +
> static const struct of_device_id mtk_wdt_dt_ids[] = {
> + { .compatible = "mediatek,mt8183-wdt", .data = &mt8183_compat },
> { .compatible = "mediatek,mt6589-wdt" },
> { /* sentinel */ }
> };
>
_______________________________________________
Alsa-devel mailing list
Alsa-devel@alsa-project.org
https://mailman.alsa-project.org/mailman/listinfo/alsa-devel
^ permalink raw reply [flat|nested] 16+ messages in thread* Re: [alsa-devel] [PATCH v2 2/4] watchdog: mtk_wdt: mt8183: Add reset controller
2019-10-03 13:49 ` Guenter Roeck
@ 2019-10-05 5:59 ` Yingjoe Chen
2019-10-05 14:46 ` Guenter Roeck
0 siblings, 1 reply; 16+ messages in thread
From: Yingjoe Chen @ 2019-10-05 5:59 UTC (permalink / raw)
To: Guenter Roeck
Cc: mark.rutland, alsa-devel, broonie, yong.liang, Jiaxin Yu,
lgirdwood, tzungbi, robh+dt, linux-mediatek, Philipp Zabel,
eason.yen, wim, linux-arm-kernel
On Thu, 2019-10-03 at 06:49 -0700, Guenter Roeck wrote:
> On 9/27/19 3:31 AM, Jiaxin Yu wrote:
<snip..>
> > +static int toprgu_reset_assert(struct reset_controller_dev *rcdev,
> > + unsigned long id)
> > +{
> > + unsigned int tmp;
> > + unsigned long flags;
> > + struct toprgu_reset *data = container_of(rcdev,
> > + struct toprgu_reset, rcdev);
> > +
> > + spin_lock_irqsave(&data->lock, flags);
> > +
> > + tmp = __raw_readl(data->toprgu_swrst_base + data->regofs);
> > + tmp |= BIT(id);
> > + tmp |= WDT_SWSYS_RST_KEY;
> > + writel(tmp, data->toprgu_swrst_base + data->regofs);
> > +
> > + spin_unlock_irqrestore(&data->lock, flags);
> > +
> > + return 0;
> > +}
> > +
> > +static int toprgu_reset_deassert(struct reset_controller_dev *rcdev,
> > + unsigned long id)
> > +{
> > + unsigned int tmp;
> > + unsigned long flags;
> > + struct toprgu_reset *data = container_of(rcdev,
> > + struct toprgu_reset, rcdev);
> > +
> > + spin_lock_irqsave(&data->lock, flags);
> > +
> > + tmp = __raw_readl(data->toprgu_swrst_base + data->regofs);
> > + tmp &= ~BIT(id);
> > + tmp |= WDT_SWSYS_RST_KEY;
> > + writel(tmp, data->toprgu_swrst_base + data->regofs);
> > +
> > + spin_unlock_irqrestore(&data->lock, flags);
> > +
> > + return 0;
> > +}
> > +
> > +static int toprgu_reset(struct reset_controller_dev *rcdev,
> > + unsigned long id)
> > +{
> > + int ret;
> > +
> > + ret = toprgu_reset_assert(rcdev, id);
> > + if (ret)
> > + return ret;
> > +
> > + return toprgu_reset_deassert(rcdev, id);
>
> Unless there is additional synchronization elsewhere, parallel calls
> to the -> assert, and ->reset callbacks may result in the reset being
> deasserted while at least one caller (the one who called the ->assert
> function) believes that it is still asserted.
>
> [ ... and if there _is_ additional synchronization elsewhere, the
> local spinlock would be unnecessary ]
>
I'm not sure if this count as additional synchronization, but you could
get exclusive control to the reset by calling
reset_control_get_exclusive so others won't try to reset the component
while you are using it.
In this case, you still need spinlock because other drivers might trying
to reset their components and they share same register.
Joe.C
_______________________________________________
Alsa-devel mailing list
Alsa-devel@alsa-project.org
https://mailman.alsa-project.org/mailman/listinfo/alsa-devel
^ permalink raw reply [flat|nested] 16+ messages in thread* Re: [alsa-devel] [PATCH v2 2/4] watchdog: mtk_wdt: mt8183: Add reset controller
2019-10-05 5:59 ` Yingjoe Chen
@ 2019-10-05 14:46 ` Guenter Roeck
2019-10-08 14:08 ` Philipp Zabel
0 siblings, 1 reply; 16+ messages in thread
From: Guenter Roeck @ 2019-10-05 14:46 UTC (permalink / raw)
To: Yingjoe Chen
Cc: mark.rutland, alsa-devel, broonie, yong.liang, Jiaxin Yu,
lgirdwood, tzungbi, robh+dt, linux-mediatek, Philipp Zabel,
eason.yen, wim, linux-arm-kernel
On 10/4/19 10:59 PM, Yingjoe Chen wrote:
> On Thu, 2019-10-03 at 06:49 -0700, Guenter Roeck wrote:
>> On 9/27/19 3:31 AM, Jiaxin Yu wrote:
>
> <snip..>
>
>
>>> +static int toprgu_reset_assert(struct reset_controller_dev *rcdev,
>>> + unsigned long id)
>>> +{
>>> + unsigned int tmp;
>>> + unsigned long flags;
>>> + struct toprgu_reset *data = container_of(rcdev,
>>> + struct toprgu_reset, rcdev);
>>> +
>>> + spin_lock_irqsave(&data->lock, flags);
>>> +
>>> + tmp = __raw_readl(data->toprgu_swrst_base + data->regofs);
>>> + tmp |= BIT(id);
>>> + tmp |= WDT_SWSYS_RST_KEY;
>>> + writel(tmp, data->toprgu_swrst_base + data->regofs);
>>> +
>>> + spin_unlock_irqrestore(&data->lock, flags);
>>> +
>>> + return 0;
>>> +}
>>> +
>>> +static int toprgu_reset_deassert(struct reset_controller_dev *rcdev,
>>> + unsigned long id)
>>> +{
>>> + unsigned int tmp;
>>> + unsigned long flags;
>>> + struct toprgu_reset *data = container_of(rcdev,
>>> + struct toprgu_reset, rcdev);
>>> +
>>> + spin_lock_irqsave(&data->lock, flags);
>>> +
>>> + tmp = __raw_readl(data->toprgu_swrst_base + data->regofs);
>>> + tmp &= ~BIT(id);
>>> + tmp |= WDT_SWSYS_RST_KEY;
>>> + writel(tmp, data->toprgu_swrst_base + data->regofs);
>>> +
>>> + spin_unlock_irqrestore(&data->lock, flags);
>>> +
>>> + return 0;
>>> +}
>>> +
>>> +static int toprgu_reset(struct reset_controller_dev *rcdev,
>>> + unsigned long id)
>>> +{
>>> + int ret;
>>> +
>>> + ret = toprgu_reset_assert(rcdev, id);
>>> + if (ret)
>>> + return ret;
>>> +
>>> + return toprgu_reset_deassert(rcdev, id);
>>
>> Unless there is additional synchronization elsewhere, parallel calls
>> to the -> assert, and ->reset callbacks may result in the reset being
>> deasserted while at least one caller (the one who called the ->assert
>> function) believes that it is still asserted.
>>
>> [ ... and if there _is_ additional synchronization elsewhere, the
>> local spinlock would be unnecessary ]
>>
>
> I'm not sure if this count as additional synchronization, but you could
> get exclusive control to the reset by calling
> reset_control_get_exclusive so others won't try to reset the component
> while you are using it.
>
> In this case, you still need spinlock because other drivers might trying
> to reset their components and they share same register.
>
That isn't what I meant. I referred to synchronization in the reset
controller core. AFAICS the reset controller core prevents parallel
calls into the same reset controller driver using atomics. Unfortunately,
it is not well defined if additional synchronization on driver level
is needed - some drivers implement it, some drivers don't, and I don't
find a documentation. Maybe Philip can provide guidance.
Thanks,
Guenter
_______________________________________________
Alsa-devel mailing list
Alsa-devel@alsa-project.org
https://mailman.alsa-project.org/mailman/listinfo/alsa-devel
^ permalink raw reply [flat|nested] 16+ messages in thread* Re: [alsa-devel] [PATCH v2 2/4] watchdog: mtk_wdt: mt8183: Add reset controller
2019-10-05 14:46 ` Guenter Roeck
@ 2019-10-08 14:08 ` Philipp Zabel
0 siblings, 0 replies; 16+ messages in thread
From: Philipp Zabel @ 2019-10-08 14:08 UTC (permalink / raw)
To: Guenter Roeck, Yingjoe Chen
Cc: mark.rutland, alsa-devel, broonie, yong.liang, Jiaxin Yu,
lgirdwood, tzungbi, robh+dt, linux-mediatek, eason.yen, wim,
linux-arm-kernel
Hi Guenter, Yingjoe,
On Sat, 2019-10-05 at 07:46 -0700, Guenter Roeck wrote:
> On 10/4/19 10:59 PM, Yingjoe Chen wrote:
> > On Thu, 2019-10-03 at 06:49 -0700, Guenter Roeck wrote:
> > > On 9/27/19 3:31 AM, Jiaxin Yu wrote:
> >
> > <snip..>
> >
> >
> > > > +static int toprgu_reset_assert(struct reset_controller_dev *rcdev,
> > > > + unsigned long id)
> > > > +{
> > > > + unsigned int tmp;
> > > > + unsigned long flags;
> > > > + struct toprgu_reset *data = container_of(rcdev,
> > > > + struct toprgu_reset, rcdev);
> > > > +
> > > > + spin_lock_irqsave(&data->lock, flags);
> > > > +
> > > > + tmp = __raw_readl(data->toprgu_swrst_base + data->regofs);
> > > > + tmp |= BIT(id);
> > > > + tmp |= WDT_SWSYS_RST_KEY;
> > > > + writel(tmp, data->toprgu_swrst_base + data->regofs);
> > > > +
> > > > + spin_unlock_irqrestore(&data->lock, flags);
> > > > +
> > > > + return 0;
> > > > +}
> > > > +
> > > > +static int toprgu_reset_deassert(struct reset_controller_dev *rcdev,
> > > > + unsigned long id)
> > > > +{
> > > > + unsigned int tmp;
> > > > + unsigned long flags;
> > > > + struct toprgu_reset *data = container_of(rcdev,
> > > > + struct toprgu_reset, rcdev);
> > > > +
> > > > + spin_lock_irqsave(&data->lock, flags);
> > > > +
> > > > + tmp = __raw_readl(data->toprgu_swrst_base + data->regofs);
> > > > + tmp &= ~BIT(id);
> > > > + tmp |= WDT_SWSYS_RST_KEY;
> > > > + writel(tmp, data->toprgu_swrst_base + data->regofs);
> > > > +
> > > > + spin_unlock_irqrestore(&data->lock, flags);
> > > > +
> > > > + return 0;
> > > > +}
> > > > +
> > > > +static int toprgu_reset(struct reset_controller_dev *rcdev,
> > > > + unsigned long id)
> > > > +{
> > > > + int ret;
> > > > +
> > > > + ret = toprgu_reset_assert(rcdev, id);
> > > > + if (ret)
> > > > + return ret;
> > > > +
> > > > + return toprgu_reset_deassert(rcdev, id);
> > >
> > > Unless there is additional synchronization elsewhere, parallel calls
> > > to the -> assert, and ->reset callbacks may result in the reset being
> > > deasserted while at least one caller (the one who called the ->assert
> > > function) believes that it is still asserted.
> > >
> > > [ ... and if there _is_ additional synchronization elsewhere, the
> > > local spinlock would be unnecessary ]
> > >
> >
> > I'm not sure if this count as additional synchronization, but you could
> > get exclusive control to the reset by calling
> > reset_control_get_exclusive so others won't try to reset the component
> > while you are using it.
> >
> > In this case, you still need spinlock because other drivers might trying
> > to reset their components and they share same register.
>
> That isn't what I meant. I referred to synchronization in the reset
> controller core. AFAICS the reset controller core prevents parallel
> calls into the same reset controller driver using atomics.
No, it doesn't. The atomics in struct reset_control prevent parallel
calls on the same, reset control only, for shared reset controls.
Two calls on different reset controls can still run simultaneously on
the same rcdev.
> Unfortunately, it is not well defined if additional synchronization on
> driver level is needed - some drivers implement it, some drivers
> don't,
I think all drivers protect read/modify/write cycles to shared registers
with a spinlock. Those that don't either have separate set/clear
registers or use regmap, otherwise it might be a bug.
> and I don't find a documentation.
I am aware this is a problem.
regards
Philipp
_______________________________________________
Alsa-devel mailing list
Alsa-devel@alsa-project.org
https://mailman.alsa-project.org/mailman/listinfo/alsa-devel
^ permalink raw reply [flat|nested] 16+ messages in thread
* Re: [alsa-devel] [PATCH v2 2/4] watchdog: mtk_wdt: mt8183: Add reset controller
2019-09-27 10:31 ` [alsa-devel] [PATCH v2 2/4] watchdog: mtk_wdt: mt8183: Add reset controller Jiaxin Yu
2019-09-28 17:49 ` Guenter Roeck
2019-10-03 13:49 ` Guenter Roeck
@ 2019-10-05 5:50 ` Yingjoe Chen
2 siblings, 0 replies; 16+ messages in thread
From: Yingjoe Chen @ 2019-10-05 5:50 UTC (permalink / raw)
To: Jiaxin Yu
Cc: mark.rutland, alsa-devel, yong.liang, robh+dt, lgirdwood,
tzungbi, broonie, linux-mediatek, linux-arm-kernel, eason.yen,
wim, linux
On Fri, 2019-09-27 at 18:31 +0800, Jiaxin Yu wrote:
> From: "yong.liang" <yong.liang@mediatek.com>
>
> Provide assert/deassert/reset API in watchdog driver.
> Register reset controller for toprgu device in watchdog probe.
I think we could improve this commit message so it is easier to
understand what is provided by this patch. You could add something like
this:
Besides watchdog, MTK toprgu module also provide sub-system (eg, audio,
camera, codec and connectivity) software reset functionality.
>
> Signed-off-by: yong.liang <yong.liang@mediatek.com>
> ---
> drivers/watchdog/Kconfig | 1 +
> drivers/watchdog/mtk_wdt.c | 110 ++++++++++++++++++++++++++++++++++++-
> 2 files changed, 110 insertions(+), 1 deletion(-)
>
> diff --git a/drivers/watchdog/Kconfig b/drivers/watchdog/Kconfig
> index 2e07caab9db2..629249fe5305 100644
> --- a/drivers/watchdog/Kconfig
> +++ b/drivers/watchdog/Kconfig
> @@ -717,6 +717,7 @@ config MEDIATEK_WATCHDOG
> tristate "Mediatek SoCs watchdog support"
> depends on ARCH_MEDIATEK || COMPILE_TEST
> select WATCHDOG_CORE
> + select RESET_CONTROLLER
> help
> Say Y here to include support for the watchdog timer
> in Mediatek SoCs.
> diff --git a/drivers/watchdog/mtk_wdt.c b/drivers/watchdog/mtk_wdt.c
> index 9c3d0033260d..660fb0e48d8e 100644
> --- a/drivers/watchdog/mtk_wdt.c
> +++ b/drivers/watchdog/mtk_wdt.c
> @@ -20,6 +20,10 @@
> #include <linux/types.h>
> #include <linux/watchdog.h>
> #include <linux/delay.h>
> +#include <linux/reset-controller.h>
> +#include <linux/slab.h>
> +#include <linux/reset.h>
> +#include <linux/of_device.h>
sorting please.
>
> #define WDT_MAX_TIMEOUT 31
> #define WDT_MIN_TIMEOUT 1
> @@ -44,17 +48,113 @@
> #define WDT_SWRST 0x14
> #define WDT_SWRST_KEY 0x1209
>
> +#define WDT_SWSYSRST 0x18U
> +#define WDT_SWSYS_RST_KEY 0x88000000
> +
> #define DRV_NAME "mtk-wdt"
> #define DRV_VERSION "1.0"
>
> static bool nowayout = WATCHDOG_NOWAYOUT;
> static unsigned int timeout;
>
> +struct toprgu_reset {
> + spinlock_t lock; /* Protects reset_controller access */
> + void __iomem *toprgu_swrst_base;
> + int regofs;
> + struct reset_controller_dev rcdev;
> +};
I'm not sure we need a separate struct, especially when you need to
duplicate wdt_base into this struct.
After removing regofs/swrst_base, this struct only contain 2 members.
Maybe you should just merge this into mtk_wdt_dev.
> +
> struct mtk_wdt_dev {
> struct watchdog_device wdt_dev;
> void __iomem *wdt_base;
> + struct toprgu_reset reset_controller;
> + const struct mtk_wdt_compatible *dev_comp;
> +};
> +
> +struct mtk_wdt_compatible {
> + int sw_rst_num;
> +};
> +
> +static int toprgu_reset_assert(struct reset_controller_dev *rcdev,
> + unsigned long id)
> +{
> + unsigned int tmp;
> + unsigned long flags;
> + struct toprgu_reset *data = container_of(rcdev,
> + struct toprgu_reset, rcdev);
> +
> + spin_lock_irqsave(&data->lock, flags);
> +
> + tmp = __raw_readl(data->toprgu_swrst_base + data->regofs);
> + tmp |= BIT(id);
> + tmp |= WDT_SWSYS_RST_KEY;
> + writel(tmp, data->toprgu_swrst_base + data->regofs);
> +
> + spin_unlock_irqrestore(&data->lock, flags);
> +
> + return 0;
> +}
> +
> +static int toprgu_reset_deassert(struct reset_controller_dev *rcdev,
> + unsigned long id)
> +{
> + unsigned int tmp;
> + unsigned long flags;
> + struct toprgu_reset *data = container_of(rcdev,
> + struct toprgu_reset, rcdev);
> +
> + spin_lock_irqsave(&data->lock, flags);
> +
> + tmp = __raw_readl(data->toprgu_swrst_base + data->regofs);
> + tmp &= ~BIT(id);
> + tmp |= WDT_SWSYS_RST_KEY;
> + writel(tmp, data->toprgu_swrst_base + data->regofs);
> +
> + spin_unlock_irqrestore(&data->lock, flags);
> +
> + return 0;
> +}
> +
> +static int toprgu_reset(struct reset_controller_dev *rcdev,
> + unsigned long id)
> +{
> + int ret;
> +
> + ret = toprgu_reset_assert(rcdev, id);
> + if (ret)
> + return ret;
> +
> + return toprgu_reset_deassert(rcdev, id);
> +}
> +
> +static struct reset_control_ops toprgu_reset_ops = {
static const
> + .assert = toprgu_reset_assert,
> + .deassert = toprgu_reset_deassert,
> + .reset = toprgu_reset,
> };
>
> +static void toprgu_register_reset_controller(struct platform_device *pdev,
> + int regofs)
> +{
> + int ret;
> + struct mtk_wdt_dev *mtk_wdt = platform_get_drvdata(pdev);
> +
> + spin_lock_init(&mtk_wdt->reset_controller.lock);
> +
> + mtk_wdt->dev_comp = of_device_get_match_data(&pdev->dev);
> + mtk_wdt->reset_controller.toprgu_swrst_base = mtk_wdt->wdt_base;
> + mtk_wdt->reset_controller.regofs = regofs;
> + mtk_wdt->reset_controller.rcdev.owner = THIS_MODULE;
> + mtk_wdt->reset_controller.rcdev.nr_resets =
> + mtk_wdt->dev_comp->sw_rst_num;
> + mtk_wdt->reset_controller.rcdev.ops = &toprgu_reset_ops;
> + mtk_wdt->reset_controller.rcdev.of_node = pdev->dev.of_node;
> + ret = reset_controller_register(&mtk_wdt->reset_controller.rcdev);
> + if (ret != 0)
> + dev_err(&pdev->dev,
> + "couldn't register wdt reset controller: %d\n", ret);
If this fail, you should return it and make mtk_wdt_probe also return
fail.
> +}
> +
> static int mtk_wdt_restart(struct watchdog_device *wdt_dev,
> unsigned long action, void *data)
> {
> @@ -187,9 +287,12 @@ static int mtk_wdt_probe(struct platform_device *pdev)
> if (unlikely(err))
> return err;
>
> - dev_info(dev, "Watchdog enabled (timeout=%d sec, nowayout=%d)\n",
> + dev_info(&pdev->dev, "Watchdog enabled (timeout=%d sec, nowayout=%d)\n",
> mtk_wdt->wdt_dev.timeout, nowayout);
>
> + mtk_wdt->dev_comp = of_device_get_match_data(&pdev->dev);
> + if (mtk_wdt->dev_comp)
> + toprgu_register_reset_controller(pdev, WDT_SWSYSRST);
Is this register offset WDT_SWSYSRST identical in all chips?
If it is, you should hardcode it in assert/deassert, just like how we
access other watchdog registers.
If not, you should put it in mtk_wdt_compatible.
> return 0;
> }
>
> @@ -217,7 +320,12 @@ static int mtk_wdt_resume(struct device *dev)
> }
> #endif
>
> +static const struct mtk_wdt_compatible mt8183_compat = {
> + .sw_rst_num = 18,
> +};
> +
> static const struct of_device_id mtk_wdt_dt_ids[] = {
> + { .compatible = "mediatek,mt8183-wdt", .data = &mt8183_compat },
> { .compatible = "mediatek,mt6589-wdt" },
sorting please
Joe.C
> { /* sentinel */ }
> };
_______________________________________________
Alsa-devel mailing list
Alsa-devel@alsa-project.org
https://mailman.alsa-project.org/mailman/listinfo/alsa-devel
^ permalink raw reply [flat|nested] 16+ messages in thread