From: Thomas Zimmermann <tzimmermann@suse.de>
To: Hardik Phalet <hardik.phalet@pm.me>,
Ferenc Bakonyi <fero@drama.obuda.kando.hu>,
Helge Deller <deller@gmx.de>
Cc: Shuah Khan <skhan@linuxfoundation.org>,
Brigham Campbell <me@brighamcampbell.com>,
linux-nvidia@lists.surfsouth.com, linux-fbdev@vger.kernel.org,
dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] fbdev/hga: Request memory region before ioremap
Date: Tue, 10 Mar 2026 12:49:33 +0100 [thread overview]
Message-ID: <ec635591-c861-4aa8-a259-718690ddaa4e@suse.de> (raw)
In-Reply-To: <20260310113810.789575-1-hardik.phalet@pm.me>
Hi
Am 10.03.26 um 12:38 schrieb Hardik Phalet:
> The driver calls ioremap() on the HGA video memory at 0xb0000 without
> first reserving the physical address range. This leaves the kernel
> resource tree incomplete and can cause silent conflicts with other
> drivers claiming the same range.
>
> Add a devm_request_mem_region() call before ioremap() in
> hga_card_detect() to reserve the memory region.
>
> Signed-off-by: Hardik Phalet <hardik.phalet@pm.me>
> ---
> Changes in v2:
> - Used devm_request_mem_region instead of request_mem_region, based on a
> review comment by Thomas [1].
>
> v1: https://lore.kernel.org/all/20260310064124.602848-1-hardik.phalet@pm.me/
> [1]: https://lore.kernel.org/all/5f9749ba-18a8-4b6b-a6e7-a011a3871bfb@suse.de/
>
> drivers/video/fbdev/hgafb.c | 9 +++++++--
> 1 file changed, 7 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/video/fbdev/hgafb.c b/drivers/video/fbdev/hgafb.c
> index 14418aa3791a..fffd34141f8d 100644
> --- a/drivers/video/fbdev/hgafb.c
> +++ b/drivers/video/fbdev/hgafb.c
> @@ -276,7 +276,7 @@ static void hga_blank(int blank_mode)
> spin_unlock_irqrestore(&hga_reg_lock, flags);
> }
>
> -static int hga_card_detect(void)
> +static int hga_card_detect(struct platform_device *pdev)
> {
> int count = 0;
> void __iomem *p, *q;
> @@ -284,6 +284,11 @@ static int hga_card_detect(void)
>
> hga_vram_len = 0x08000;
>
> + if (!devm_request_mem_region(&pdev->dev, 0xb0000, hga_vram_len, "hgafb")) {
> + pr_err("hgafb: cannot reserve video memory at 0xb0000\n");
dev_err() with pdev->dev please.
The rest looks good.
Best regards
Thomas
> + return -EBUSY;
> + }
> +
> hga_vram = ioremap(0xb0000, hga_vram_len);
> if (!hga_vram)
> return -ENOMEM;
> @@ -568,7 +573,7 @@ static int hgafb_probe(struct platform_device *pdev)
> struct fb_info *info;
> int ret;
>
> - ret = hga_card_detect();
> + ret = hga_card_detect(pdev);
> if (ret)
> return ret;
>
--
--
Thomas Zimmermann
Graphics Driver Developer
SUSE Software Solutions Germany GmbH
Frankenstr. 146, 90461 Nürnberg, Germany, www.suse.com
GF: Jochen Jaser, Andrew McDonald, Werner Knoblich, (HRB 36809, AG Nürnberg)
prev parent reply other threads:[~2026-03-10 11:49 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-10 11:38 [PATCH v2] fbdev/hga: Request memory region before ioremap Hardik Phalet
2026-03-10 11:49 ` Thomas Zimmermann [this message]
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=ec635591-c861-4aa8-a259-718690ddaa4e@suse.de \
--to=tzimmermann@suse.de \
--cc=deller@gmx.de \
--cc=dri-devel@lists.freedesktop.org \
--cc=fero@drama.obuda.kando.hu \
--cc=hardik.phalet@pm.me \
--cc=linux-fbdev@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nvidia@lists.surfsouth.com \
--cc=me@brighamcampbell.com \
--cc=skhan@linuxfoundation.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