watchdog: wdat_wdt: map registers that fall inside ACPI NVS
PATCH 1/1 watchdog: wdat_wdt: map registers that fall inside ACPI NVS
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.
--- drivers/watchdog/wdat_wdt.c | 31 ++++++++++++++++++++++++++++++- 1 file changed, 30 insertions(+), 1 deletion(-)
drivers/watchdog/wdat_wdt.c +30 -1
@@ -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;
Signature · 1 line
2.53.0
[email protected]
AI reviewThank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider: - [Medium] Calling `devm_ioremap_resource()` triggers an unconditional `dev_err()` when it fails with…
Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Medium] Calling devm_ioremap_resource() triggers an unconditional dev_err() when it fails with -EBUSY, causing confusing and spurious errors in the kernel log on systems with ACPI NVS. --
--- Patch [1]: [PATCH] watchdog: wdat_wdt: map registers that fall inside ACPI NVS --- commit fe186a236b35b9dc11c6a76632ffa54de7cc01ba
Author: Renê de Souza Pinto <[email protected]>
watchdog: wdat_wdt: map registers that fall inside ACPI NVS
This commit fixes an issue where the WDAT watchdog fails to probe on systems where its registers reside in ACPI NVS memory (like the OnLogic Karbon 524) by falling back to devm_memremap() when devm_ioremap_resource() returns -EBUSY.
Quoted 4 lines
drivers/watchdog/wdat_wdt.c +0
-0
[ ... ]
Quoted 4 lines
drivers/watchdog/wdat_wdt.c +0
-0@@ -309,6 +311,33 @@ static struct watchdog_ops wdat_wdt_ops = { .set_timeout = wdat_wdt_set_timeout, };
drivers/watchdog/wdat_wdt.c static struct watchdog_ops wdat_wdt_ops = { · line 323
Quoted 10 lines
drivers/watchdog/wdat_wdt.c +10
-0+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;
[Severity: Medium]
Since devm_ioremap_resource() internally calls dev_err() when it fails, will this unconditional call log a spurious error before the driver has a chance to execute the expected ACPI NVS fallback?
Could this be avoided by checking region_intersects() for IORES_DESC_ACPI_NV_STORAGE before attempting the reservation, rather than relying on devm_ioremap_resource() to fail first?
Quoted 17 lines
drivers/watchdog/wdat_wdt.c +17
-0+ +/* 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; +} +
Signature · 1 line
Sashiko AI review · https://sashiko.dev/#/patchset/[email protected]?part=1
PATCH v2 1/1 watchdog: wdat_wdt: map registers that fall inside ACPI NVS
In reply to Renê de Souza PintoSome 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
Check whether the region falls inside ACPI NVS before requesting it and, if so, map it without reservation.
--- drivers/watchdog/wdat_wdt.c | 27 ++++++++++++++++++++++++++- 1 file changed, 26 insertions(+), 1 deletion(-)
drivers/watchdog/wdat_wdt.c +26 -1
@@ -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,29 @@ 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 *addr; + +/* Map memory region without reserving it if it falls inside ACPI NVS */ +if (region_intersects (res->start, size,IORESOURCE_MEM , +IORES_DESC_ACPI_NV_STORAGE ) ==REGION_INTERSECTS ) { +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; + } + +return devm_ioremap_resource (dev, res); +} +static int wdat_wdt_probe (struct platform_device *pdev) {struct device *dev = &pdev->dev;
@@ -362,7 +387,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;
Signature · 1 line
2.53.0
Quoted 7 lines · Renê de Souza Pinto
Some firmwares describe WDAT registers inside memory ranges marked as ACPI NVS in the E820 map, failing with
-EBUSYduring 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):
Quoted 7 lines
wdat_wdtwdat_wdt: error-EBUSY: can't request region for resource [mem0x63df7a98]wdat_wdtwdat_wdt: probe with driverwdat_wdtfailed with error -16Check whether the region falls inside ACPI NVS before requesting it and, if so, map it without reservation.
Signed-off-by Renê de Souza Pinto <[email protected]>
Applied.
Thanks,
Guenter