From: "Renê de Souza Pinto" <rene@renesp.com.br>
To: Wim Van Sebroeck <wim@linux-watchdog.org>,
Guenter Roeck <linux@roeck-us.net>,
linux-watchdog@vger.kernel.org (open list:WATCHDOG DEVICE
DRIVERS), linux-kernel@vger.kernel.org (open list)
Cc: "Renê de Souza Pinto" <rene@renesp.com.br>
Subject: [PATCH] watchdog: wdat_wdt: map registers that fall inside ACPI NVS
Date: Tue, 4 Aug 2026 11:23:37 +0200 [thread overview]
Message-ID: <20260804092337.3556947-1-rene@renesp.com.br> (raw)
Some firmwares describe WDAT registers inside memory ranges marked as
ACPI NVS in the E820 map, failing with -EBUSY during probe, leaving the
hardware watchdog unserviced and triggering periodic system resets.
This issue was observed on a OnLogic Karbon 524 device (when watchdog is
enabled in BIOS):
wdat_wdt wdat_wdt: error -EBUSY: can't request region for resource [mem 0x63df7a98]
wdat_wdt wdat_wdt: probe with driver wdat_wdt failed with error -16
This commit fixes this issue by falling back to devm_memremap() when
devm_ioremap_resource() fails with -EBUSY on an ACPI NVS region.
Signed-off-by: Renê de Souza Pinto <rene@renesp.com.br>
---
drivers/watchdog/wdat_wdt.c | 31 ++++++++++++++++++++++++++++++-
1 file changed, 30 insertions(+), 1 deletion(-)
diff --git a/drivers/watchdog/wdat_wdt.c b/drivers/watchdog/wdat_wdt.c
index dd3c2d69c9df..a56224cf8d22 100644
--- a/drivers/watchdog/wdat_wdt.c
+++ b/drivers/watchdog/wdat_wdt.c
@@ -7,7 +7,9 @@
*/
#include <linux/acpi.h>
+#include <linux/io.h>
#include <linux/ioport.h>
+#include <linux/mm.h>
#include <linux/module.h>
#include <linux/platform_device.h>
#include <linux/pm.h>
@@ -309,6 +311,33 @@ static struct watchdog_ops wdat_wdt_ops = {
.set_timeout = wdat_wdt_set_timeout,
};
+static void __iomem *wdat_wdt_map_mem(struct device *dev, struct resource *res)
+{
+ resource_size_t size = resource_size(res);
+ void __iomem *reg;
+ void *addr;
+
+ /* Try standard reservation + ioremap first */
+ reg = devm_ioremap_resource(dev, res);
+ if (!IS_ERR(reg) || PTR_ERR(reg) != -EBUSY)
+ return reg;
+
+ /* If busy, check if conflict is due to ACPI NVS memory */
+ if (region_intersects(res->start, size, IORESOURCE_MEM,
+ IORES_DESC_ACPI_NV_STORAGE) != REGION_INTERSECTS)
+ return reg; /* Real conflict, return -EBUSY */
+
+ dev_warn(dev, "%pR is inside ACPI NVS, mapping without reservation\n", res);
+
+ addr = devm_memremap(dev, res->start, size, MEMREMAP_WB);
+ if (IS_ERR(addr)) {
+ dev_err(dev, "failed to map resource %pR\n", res);
+ return IOMEM_ERR_PTR(PTR_ERR(addr));
+ }
+
+ return (void __iomem __force *)addr;
+}
+
static int wdat_wdt_probe(struct platform_device *pdev)
{
struct device *dev = &pdev->dev;
@@ -362,7 +391,7 @@ static int wdat_wdt_probe(struct platform_device *pdev)
res = &pdev->resource[i];
if (resource_type(res) == IORESOURCE_MEM) {
- reg = devm_ioremap_resource(dev, res);
+ reg = wdat_wdt_map_mem(dev, res);
if (IS_ERR(reg)) {
ret = PTR_ERR(reg);
goto out_put_table;
--
2.53.0
next reply other threads:[~2026-08-04 9:29 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-04 9:23 Renê de Souza Pinto [this message]
2026-08-04 9:40 ` [PATCH] watchdog: wdat_wdt: map registers that fall inside ACPI NVS sashiko-bot
2026-08-04 10:39 ` [PATCH v2] " Renê de Souza Pinto
2026-08-06 21:27 ` 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=20260804092337.3556947-1-rene@renesp.com.br \
--to=rene@renesp.com.br \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-watchdog@vger.kernel.org \
--cc=linux@roeck-us.net \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.