From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
To: Elad Nachman <enachman@marvell.com>,
wim@linux-watchdog.org, linux@roeck-us.net, robh+dt@kernel.org,
krzysztof.kozlowski+dt@linaro.org, conor+dt@kernel.org,
gregory.clement@bootlin.com, chris.packham@alliedtelesis.co.nz,
andrew@lunn.ch, fu.wei@linaro.org, Suravee.Suthikulpanit@amd.com,
al.stone@linaro.org, timur@codeaurora.org,
linux-watchdog@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Cc: cyuval@marvell.com
Subject: Re: [PATCH 3/3] watchdog: sbsa_gwdt: add support for Marvell ac5
Date: Thu, 14 Dec 2023 16:16:55 +0100 [thread overview]
Message-ID: <09cf3280-9959-4475-ae0d-03b750f64825@linaro.org> (raw)
In-Reply-To: <20231214150414.1849058-4-enachman@marvell.com>
On 14/12/2023 16:04, Elad Nachman wrote:
> From: Elad Nachman <enachman@marvell.com>
>
> Add support for Marvell ac5/x variant of the ARM
> sbsa global watchdog. This watchdog deviates from
> the standard driver by the following items:
>
> 1. Registers reside in secure register section.
> hence access is only possible via SMC calls to ATF.
>
> 2. There are couple more registers which reside in
> other register areas, which needs to be configured
> in order for the watchdog to properly generate
> reset through the SOC.
>
> The new Marvell compatibility string differentiates between
> the original sbsa mode of operation and the Marvell mode of
> operation.
>
> Signed-off-by: Elad Nachman <enachman@marvell.com>
> ---
...
> gwdt = devm_kzalloc(dev, sizeof(*gwdt), GFP_KERNEL);
> if (!gwdt)
> return -ENOMEM;
> platform_set_drvdata(pdev, gwdt);
>
> - cf_base = devm_platform_ioremap_resource(pdev, 0);
> - if (IS_ERR(cf_base))
> - return PTR_ERR(cf_base);
> -
> - rf_base = devm_platform_ioremap_resource(pdev, 1);
> - if (IS_ERR(rf_base))
> - return PTR_ERR(rf_base);
> + if (of_device_is_compatible(np, "marvell,ac5-wd")) {
No, use match data. That's its purpose, don't put comaptibles inside code.
> + marvell = true;
> + gwdt->soc_reg_ops = &smc_reg_ops;
> + res = platform_get_resource(pdev, IORESOURCE_MEM, 0);
> + if (IS_ERR(res))
> + return PTR_ERR(res);
> + cf_base = res->start;
Why do you use entirely different code?
> +
> + res = platform_get_resource(pdev, IORESOURCE_MEM, 1);
> + if (IS_ERR(res))
> + return PTR_ERR(res);
> + rf_base = res->start;
> +
> + res = platform_get_resource(pdev, IORESOURCE_MEM, 2);
> + if (IS_ERR(res))
> + return PTR_ERR(res);
> + cpu_ctrl_base = res->start;
> + mng_base = devm_platform_ioremap_resource(pdev, 3);
> + if (IS_ERR(mng_base))
> + return PTR_ERR(mng_base);
> + rst_ctrl_base = devm_platform_ioremap_resource(pdev, 4);
> + if (IS_ERR(rst_ctrl_base))
> + return PTR_ERR(rst_ctrl_base);
> + } else {
> + gwdt->soc_reg_ops = &direct_reg_ops;
> + cf_base = devm_platform_ioremap_resource(pdev, 0);
> + if (IS_ERR(cf_base))
> + return PTR_ERR(cf_base);
Why? This is shared.
> +
> + rf_base = devm_platform_ioremap_resource(pdev, 1);
> + if (IS_ERR(rf_base))
> + return PTR_ERR(rf_base);
Ditto
> + }
>
> /*
> * Get the frequency of system counter from the cp15 interface of ARM
> @@ -299,7 +482,7 @@ static int sbsa_gwdt_probe(struct platform_device *pdev)
> else
> wdd->max_hw_heartbeat_ms = GENMASK_ULL(47, 0) / gwdt->clk * 1000;
>
> - status = readl(cf_base + SBSA_GWDT_WCS);
> + status = gwdt->soc_reg_ops->reg_read32(cf_base + SBSA_GWDT_WCS);
> if (status & SBSA_GWDT_WCS_WS1) {
> dev_warn(dev, "System reset by WDT.\n");
> wdd->bootstatus |= WDIOF_CARDRESET;
> @@ -317,7 +500,7 @@ static int sbsa_gwdt_probe(struct platform_device *pdev)
> * In case there is a pending ws0 interrupt, just ping
> * the watchdog before registering the interrupt routine
> */
> - writel(0, rf_base + SBSA_GWDT_WRR);
> + gwdt->soc_reg_ops->reg_write32(0, rf_base + SBSA_GWDT_WRR);
> if (devm_request_irq(dev, irq, sbsa_gwdt_interrupt, 0,
> pdev->name, gwdt)) {
> action = 0;
> @@ -347,7 +530,28 @@ static int sbsa_gwdt_probe(struct platform_device *pdev)
> ret = devm_watchdog_register_device(dev, wdd);
> if (ret)
> return ret;
> -
> + /*
> + * Marvell AC5/X/IM: need to configure the watchdog
> + * HW to trigger reset on WS1 (Watchdog Signal 1):
> + *
> + * 1. Configure the watchdog signal enable (routing)
> + * according to configuration
> + * 2. Unmask the wd_rst input signal to the reset unit
> + */
> + if (marvell) {
> + gwdt->soc_reg_ops->reg_write32(reset, cpu_ctrl_base +
> + SBSA_GWDT_MARVELL_CPU_WD_RST_EN_REG);
> + id = readl(mng_base + SBSA_GWDT_MARVELL_MNG_ID_REG) &
> + SBSA_GWDT_MARVELL_ID_MASK;
> +
> + if (id == SBSA_GWDT_MARVELL_AC5_ID)
> + val = SBSA_GWDT_MARVELL_AC5_RST_UNIT_WD_BIT;
> + else
> + val = SBSA_GWDT_MARVELL_IRONMAN_RST_UNIT_WD_BIT;
> +
> + writel(readl(rst_ctrl_base + SBSA_GWDT_MARVELL_RST_CTRL_REG) & ~val,
> + rst_ctrl_base + SBSA_GWDT_MARVELL_RST_CTRL_REG);
> + }
> dev_info(dev, "Initialized with %ds timeout @ %u Hz, action=%d.%s\n",
> wdd->timeout, gwdt->clk, action,
> status & SBSA_GWDT_WCS_EN ? " [enabled]" : "");
> @@ -383,6 +587,7 @@ static const struct dev_pm_ops sbsa_gwdt_pm_ops = {
>
> static const struct of_device_id sbsa_gwdt_of_match[] = {
> { .compatible = "arm,sbsa-gwdt", },
> + { .compatible = "marvell,ac5-wd", },
> {},
> };
> MODULE_DEVICE_TABLE(of, sbsa_gwdt_of_match);
Best regards,
Krzysztof
next prev parent reply other threads:[~2023-12-14 15:16 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-14 15:04 [PATCH 0/3] watchdog: sbsa_gwdt: add support for Marvell ac5 Elad Nachman
2023-12-14 15:04 ` [PATCH 1/3] dt-bindings: watchdog: add Marvell AC5 watchdog Elad Nachman
2023-12-14 15:13 ` Krzysztof Kozlowski
2023-12-14 15:04 ` [PATCH 2/3] arm64: dts: ac5: add watchdog nodes Elad Nachman
2023-12-14 15:15 ` Krzysztof Kozlowski
2023-12-14 15:04 ` [PATCH 3/3] watchdog: sbsa_gwdt: add support for Marvell ac5 Elad Nachman
2023-12-14 15:16 ` Krzysztof Kozlowski [this message]
2023-12-15 1:08 ` kernel test robot
2023-12-15 18:01 ` Rob Herring
2023-12-15 19:12 ` Guenter Roeck
2023-12-15 22:35 ` kernel test robot
2023-12-17 3:08 ` kernel test robot
2023-12-20 14:03 ` Rob Herring
2023-12-15 4:21 ` [PATCH 0/3] " Chris Packham
2023-12-15 17:48 ` Rob Herring
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=09cf3280-9959-4475-ae0d-03b750f64825@linaro.org \
--to=krzysztof.kozlowski@linaro.org \
--cc=Suravee.Suthikulpanit@amd.com \
--cc=al.stone@linaro.org \
--cc=andrew@lunn.ch \
--cc=chris.packham@alliedtelesis.co.nz \
--cc=conor+dt@kernel.org \
--cc=cyuval@marvell.com \
--cc=devicetree@vger.kernel.org \
--cc=enachman@marvell.com \
--cc=fu.wei@linaro.org \
--cc=gregory.clement@bootlin.com \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-watchdog@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=robh+dt@kernel.org \
--cc=timur@codeaurora.org \
--cc=wim@linux-watchdog.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox