From: Ahmad Fatoum <a.fatoum@pengutronix.de>
To: barebox@lists.infradead.org
Cc: Ahmad Fatoum <a.fatoum@pengutronix.de>
Subject: [PATCH v2] driver: have dev_platform_ioremap_resource return error pointer
Date: Tue, 22 Apr 2025 09:22:58 +0200 [thread overview]
Message-ID: <20250422072258.179188-1-a.fatoum@pengutronix.de> (raw)
From: Ahmad Fatoum <a.fatoum@barebox.org>
devm_request_mem_region doesn't return NULL on error on Linux and thus
it should neither in barebox. Fix this.
Signed-off-by: Ahmad Fatoum <a.fatoum@pengutronix.de>
---
v1 -> v2:
- clarify IS_ERR(resource::start) (Sascha)
---
drivers/base/driver.c | 11 ++++++++++-
include/linux/device.h | 2 +-
2 files changed, 11 insertions(+), 2 deletions(-)
diff --git a/drivers/base/driver.c b/drivers/base/driver.c
index edba037fa2dd..85cec7efab46 100644
--- a/drivers/base/driver.c
+++ b/drivers/base/driver.c
@@ -549,7 +549,14 @@ void __iomem *dev_platform_get_and_ioremap_resource(struct device *dev,
res = dev_request_mem_resource(dev, num);
if (IS_ERR(res))
return IOMEM_ERR_PTR(PTR_ERR(res));
- else if (WARN_ON(IS_ERR_VALUE(res->start)))
+
+ /* As everything is mapped 1:1 by default, drivers on unlucky
+ * platforms can end up successfully requesting memory, but
+ * getting a base address that looks like an error pointer.
+ * Let's warn loudly about this case, as these drivers
+ * should be using dev_request_mem_resource instead.
+ */
+ if (WARN_ON(IS_ERR_VALUE(res->start)))
return IOMEM_ERR_PTR(-EINVAL);
if (out_res)
@@ -587,6 +594,8 @@ void __iomem *dev_request_mem_region(struct device *dev, int num)
struct resource *res;
res = dev_request_mem_resource(dev, num);
+ if (!IS_ERR(res) && WARN_ON(IS_ERR_VALUE(res->start)))
+ return IOMEM_ERR_PTR(res->start);
if (IS_ERR(res))
return ERR_CAST(res);
diff --git a/include/linux/device.h b/include/linux/device.h
index 66294910abb3..661d8b24730e 100644
--- a/include/linux/device.h
+++ b/include/linux/device.h
@@ -39,7 +39,7 @@ static inline void __iomem *dev_platform_ioremap_resource(struct device *dev,
* so we don't need to do anything besides requesting the regions
* and can leave the memory attributes unchanged.
*/
- return dev_request_mem_region_err_null(dev, resource);
+ return dev_request_mem_region(dev, resource);
}
static inline void __iomem *devm_ioremap(struct device *dev,
--
2.39.5
next reply other threads:[~2025-04-22 8:32 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-22 7:22 Ahmad Fatoum [this message]
2025-04-22 9:31 ` Sascha Hauer
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=20250422072258.179188-1-a.fatoum@pengutronix.de \
--to=a.fatoum@pengutronix.de \
--cc=barebox@lists.infradead.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