From: Yassine Oudjana <yassine.oudjana@gmail.com>
To: AngeloGioacchino Del Regno
<angelogioacchino.delregno@collabora.com>,
Wim Van Sebroeck <wim@linux-watchdog.org>,
Guenter Roeck <linux@roeck-us.net>,
Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Matthias Brugger <matthias.bgg@gmail.com>,
Philipp Zabel <p.zabel@pengutronix.de>
Cc: Yassine Oudjana <y.oudjana@protonmail.com>,
linux-watchdog@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-mediatek@lists.infradead.org
Subject: Re: [PATCH 2/2] watchdog: mtk_wdt: Add support for MT6735 WDT
Date: Wed, 16 Oct 2024 12:26:26 +0300 [thread overview]
Message-ID: <f9b09f59-a222-4b75-a6ef-c7fb7c2cff9e@gmail.com> (raw)
In-Reply-To: <0398e95e-dbb8-2e41-7b36-12e36b8729f0@collabora.com>
On 02/03/2023 6:15 pm, AngeloGioacchino Del Regno wrote:
> Il 02/03/23 13:40, Yassine Oudjana ha scritto:
>> From: Yassine Oudjana <y.oudjana@protonmail.com>
>>
>> Add support for the watchdog timer/top reset generation unit found on
>> MT6735.
>> Disable WDT_MODE_IRQ_EN in mtk_wdt_restart in order to make TOPRGU assert
>> the SYSRST pin instead of issuing an IRQ. This change may be needed in
>> other
>> SoCs as well.
>>
>> Signed-off-by: Yassine Oudjana <y.oudjana@protonmail.com>
>> ---
>> drivers/watchdog/mtk_wdt.c | 12 ++++++++++++
>> 1 file changed, 12 insertions(+)
>>
>> diff --git a/drivers/watchdog/mtk_wdt.c b/drivers/watchdog/mtk_wdt.c
>> index a9c437598e7e..5a7a7b2b3727 100644
>> --- a/drivers/watchdog/mtk_wdt.c
>> +++ b/drivers/watchdog/mtk_wdt.c
>> @@ -10,6 +10,7 @@
>> */
>> #include <dt-bindings/reset/mt2712-resets.h>
>> +#include <dt-bindings/reset/mediatek,mt6735-wdt.h>
>> #include <dt-bindings/reset/mediatek,mt6795-resets.h>
>> #include <dt-bindings/reset/mt7986-resets.h>
>> #include <dt-bindings/reset/mt8183-resets.h>
>> @@ -82,6 +83,10 @@ static const struct mtk_wdt_data mt2712_data = {
>> .toprgu_sw_rst_num = MT2712_TOPRGU_SW_RST_NUM,
>> };
>> +static const struct mtk_wdt_data mt6735_data = {
>> + .toprgu_sw_rst_num = MT6735_TOPRGU_RST_NUM,
>> +};
>> +
>> static const struct mtk_wdt_data mt6795_data = {
>> .toprgu_sw_rst_num = MT6795_TOPRGU_SW_RST_NUM,
>> };
>> @@ -187,9 +192,15 @@ static int mtk_wdt_restart(struct watchdog_device
>> *wdt_dev,
>> {
>> struct mtk_wdt_dev *mtk_wdt = watchdog_get_drvdata(wdt_dev);
>> void __iomem *wdt_base;
>> + u32 reg;
>> wdt_base = mtk_wdt->wdt_base;
>> + /* Enable reset in order to issue a system reset instead of an
>> IRQ */
>> + reg = readl(wdt_base + WDT_MODE);
>> + reg &= ~WDT_MODE_IRQ_EN;
>> + writel(reg | WDT_MODE_KEY, wdt_base + WDT_MODE);
>
> This is unnecessary and already done in mtk_wdt_start().
> If you think you *require* this snippet, you most likely misconfigured the
> devicetree node for your device :-)
Ok so mtk_wdt_start is never called. I'm still not quite sure how the
watchdog works but it seems to me like it's supposed to be started from
userspace. I also see some drivers calling it in probe.
Say I don't want to use the watchdog (which I don't, all I need from
TOPRGU is the resets, I don't care about the watchdog). Not starting the
watchdog means I can't reset the system because all mtk_wdt_restart will
do is make TOPRGU send me an IRQ that I have no use for. According to
the datasheet, setting WDT_MODE_IRQ_EN configures TOPRGU to send an IRQ
on system reset event (either watchdog timeout or software watchdog
reset) while clearing it makes it actually issue a system reset. What
can I do in this case?
next prev parent reply other threads:[~2024-10-16 9:26 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-02 12:40 [PATCH 0/2] MediaTek MT6735 TOPRGU/WDT support Yassine Oudjana
2023-03-02 12:40 ` [PATCH 1/2] dt-bindings: reset: Add binding for MediaTek MT6735 TOPRGU/WDT Yassine Oudjana
2023-03-02 15:15 ` AngeloGioacchino Del Regno
2023-03-08 10:55 ` Krzysztof Kozlowski
2023-04-16 15:55 ` Guenter Roeck
2023-03-02 12:40 ` [PATCH 2/2] watchdog: mtk_wdt: Add support for MT6735 WDT Yassine Oudjana
2023-03-02 15:15 ` AngeloGioacchino Del Regno
2024-10-16 9:26 ` Yassine Oudjana [this message]
2024-10-16 9:56 ` AngeloGioacchino Del Regno
2024-10-16 12:51 ` Guenter Roeck
2024-10-17 6:43 ` yassine.oudjana
2024-10-17 14:09 ` Guenter Roeck
2024-10-17 15:16 ` AngeloGioacchino Del Regno
2024-10-17 15:39 ` Guenter Roeck
2024-10-21 12:35 ` AngeloGioacchino Del Regno
2024-10-18 7:10 ` Yassine Oudjana
2023-03-08 11:47 ` Guenter Roeck
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=f9b09f59-a222-4b75-a6ef-c7fb7c2cff9e@gmail.com \
--to=yassine.oudjana@gmail.com \
--cc=angelogioacchino.delregno@collabora.com \
--cc=devicetree@vger.kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=linux-watchdog@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=matthias.bgg@gmail.com \
--cc=p.zabel@pengutronix.de \
--cc=robh+dt@kernel.org \
--cc=wim@linux-watchdog.org \
--cc=y.oudjana@protonmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).