From: patdiviyam@gmail.com
To: dri-devel@lists.freedesktop.org
Cc: tzimmermann@suse.de, deller@gmx.de, linux-fbdev@vger.kernel.org,
DiviyamPathak <patdiviyam@gmail.com>
Subject: [PATCH] fbdev: xilinxfb: request memory region before mapping framebuffer
Date: Tue, 16 Dec 2025 04:23:05 +0530 [thread overview]
Message-ID: <20251215225305.3820098-1-patdiviyam@gmail.com> (raw)
From: DiviyamPathak <patdiviyam@gmail.com>
The xilinxfb driver maps a physical framebuffer address with ioremap()
without first reserving the memory region. This can conflict with other
drivers accessing the same resource.
Request the memory region with devm_request_mem_region() before mapping
the framebuffer and use managed mappings for proper lifetime handling.
This addresses the fbdev TODO about requesting memory regions and avoids
potential resource conflicts.
Signed-off-by: DiviyamPathak <patdiviyam@gmail.com>
---
drivers/video/fbdev/xilinxfb.c | 30 +++++++++++++++++-------------
1 file changed, 17 insertions(+), 13 deletions(-)
diff --git a/drivers/video/fbdev/xilinxfb.c b/drivers/video/fbdev/xilinxfb.c
index 0a6e05cd155a..f18437490de8 100644
--- a/drivers/video/fbdev/xilinxfb.c
+++ b/drivers/video/fbdev/xilinxfb.c
@@ -280,19 +280,27 @@ static int xilinxfb_assign(struct platform_device *pdev,
/* Allocate the framebuffer memory */
if (pdata->fb_phys) {
drvdata->fb_phys = pdata->fb_phys;
- drvdata->fb_virt = ioremap(pdata->fb_phys, fbsize);
+ /* Request the memory region before mapping */
+ if (!devm_request_mem_region(dev, pdata->fb_phys, fbsize,
+ DRIVER_NAME)) {
+ dev_err(dev, "Cannot request framebuffer memory region\n");
+ return -EBUSY;
+ }
+ drvdata->fb_virt = devm_ioremap(dev, pdata->fb_phys, fbsize);
+ if (!drvdata->fb_virt) {
+ dev_err(dev, "Could not map framebuffer memory\n");
+ return -ENOMEM;
+ }
} else {
drvdata->fb_alloced = 1;
drvdata->fb_virt = dma_alloc_coherent(dev, PAGE_ALIGN(fbsize),
- &drvdata->fb_phys,
- GFP_KERNEL);
- }
-
- if (!drvdata->fb_virt) {
- dev_err(dev, "Could not allocate frame buffer memory\n");
- return -ENOMEM;
+ &drvdata->fb_phys,
+ GFP_KERNEL);
+ if (!drvdata->fb_virt) {
+ dev_err(dev, "Could not allocate frame buffer memory\n");
+ return -ENOMEM;
+ }
}
-
/* Clear (turn to black) the framebuffer */
memset_io((void __iomem *)drvdata->fb_virt, 0, fbsize);
@@ -362,8 +370,6 @@ static int xilinxfb_assign(struct platform_device *pdev,
if (drvdata->fb_alloced)
dma_free_coherent(dev, PAGE_ALIGN(fbsize), drvdata->fb_virt,
drvdata->fb_phys);
- else
- iounmap(drvdata->fb_virt);
/* Turn off the display */
xilinx_fb_out32(drvdata, REG_CTRL, 0);
@@ -386,8 +392,6 @@ static void xilinxfb_release(struct device *dev)
if (drvdata->fb_alloced)
dma_free_coherent(dev, PAGE_ALIGN(drvdata->info.fix.smem_len),
drvdata->fb_virt, drvdata->fb_phys);
- else
- iounmap(drvdata->fb_virt);
/* Turn off the display */
xilinx_fb_out32(drvdata, REG_CTRL, 0);
--
2.43.0
next reply other threads:[~2025-12-15 22:53 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-15 22:53 patdiviyam [this message]
2025-12-30 9:57 ` [PATCH] fbdev: xilinxfb: request memory region before mapping framebuffer Helge Deller
[not found] ` <CAM19b+s73Fo6Ej85qk72UPn12VQ_iFAYpHv7K=wOapb0-+1XBA@mail.gmail.com>
2025-12-31 1:12 ` Diviyam Pat
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=20251215225305.3820098-1-patdiviyam@gmail.com \
--to=patdiviyam@gmail.com \
--cc=deller@gmx.de \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-fbdev@vger.kernel.org \
--cc=tzimmermann@suse.de \
/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