linux-m68k.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
* Re: [RFC/RFT PATCH] fbdev: q40fb: request memory region
       [not found] <20251120180233.763975-1-hsukrut3@gmail.com>
@ 2025-11-21 10:03 ` Geert Uytterhoeven
  2025-11-21 10:17   ` Helge Deller
  0 siblings, 1 reply; 2+ messages in thread
From: Geert Uytterhoeven @ 2025-11-21 10:03 UTC (permalink / raw)
  To: Sukrut Heroorkar
  Cc: Helge Deller, open list:FRAMEBUFFER LAYER,
	open list:FRAMEBUFFER LAYER, open list, shuah, david.hunter.linux,
	linux-m68k

Hi Sukrut,

CC linux-m68k

On Thu, 20 Nov 2025 at 19:03, Sukrut Heroorkar <hsukrut3@gmail.com> wrote:
> The q40fb driver uses a fixed physical address but never reserves
> the corresponding I/O region. Reserve the range  as suggested in
> Documentation/gpu/todo.rst ("Request memory regions in all fbdev drivers").
>
> If the memory cannot be reserved, fail probe with -EBUSY to avoid
> conflicting with another user of the same address.
>
> Signed-off-by: Sukrut Heroorkar <hsukrut3@gmail.com>

Thanks for your patch!

> ---
> Testing: This patch is sent as RFT since Q40 hardware is unavilable and
> QEMU does not emulated a Q40 platform. The change is therefore compile-tested
> only.

I would suggest not to apply this, unless it is tested on real
hardware.  It wouldn't be the first time an innocent-looking change like
this breaks a system. See e.g.
https://lore.kernel.org/all/Y5I2oQexHNdlIbsQ@shell.armlinux.org.uk

> --- a/drivers/video/fbdev/q40fb.c
> +++ b/drivers/video/fbdev/q40fb.c
> @@ -101,6 +101,13 @@ static int q40fb_probe(struct platform_device *dev)
>         info->par = NULL;
>         info->screen_base = (char *) q40fb_fix.smem_start;
>
> +       if (!request_mem_region(q40fb_fix.smem_start, q40fb_fix.smem_len,
> +                               "q40fb")) {
> +               dev_err(&dev->dev, "cannot reserve video memory at 0x%lx\n",
> +                       q40fb_fix.smem_start);
> +               return -EBUSY;
> +       }
> +
>         if (fb_alloc_cmap(&info->cmap, 256, 0) < 0) {
>                 framebuffer_release(info);
>                 return -ENOMEM;

Gr{oetje,eeting}s,

                        Geert


--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org

In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
                                -- Linus Torvalds

^ permalink raw reply	[flat|nested] 2+ messages in thread

* Re: [RFC/RFT PATCH] fbdev: q40fb: request memory region
  2025-11-21 10:03 ` [RFC/RFT PATCH] fbdev: q40fb: request memory region Geert Uytterhoeven
@ 2025-11-21 10:17   ` Helge Deller
  0 siblings, 0 replies; 2+ messages in thread
From: Helge Deller @ 2025-11-21 10:17 UTC (permalink / raw)
  To: Geert Uytterhoeven, Sukrut Heroorkar
  Cc: open list:FRAMEBUFFER LAYER, open list:FRAMEBUFFER LAYER, shuah,
	david.hunter.linux, linux-m68k

Hi Geert & Sukrut,

On 11/21/25 11:03, Geert Uytterhoeven wrote:
> On Thu, 20 Nov 2025 at 19:03, Sukrut Heroorkar <hsukrut3@gmail.com> wrote:
>> The q40fb driver uses a fixed physical address but never reserves
>> the corresponding I/O region. Reserve the range  as suggested in
>> Documentation/gpu/todo.rst ("Request memory regions in all fbdev drivers").
>>
>> If the memory cannot be reserved, fail probe with -EBUSY to avoid
>> conflicting with another user of the same address.
>>
>> Signed-off-by: Sukrut Heroorkar <hsukrut3@gmail.com>
> 
> Thanks for your patch!
> 
>> ---
>> Testing: This patch is sent as RFT since Q40 hardware is unavilable and
>> QEMU does not emulated a Q40 platform. The change is therefore compile-tested
>> only.
> 
> I would suggest not to apply this, unless it is tested on real
> hardware.  It wouldn't be the first time an innocent-looking change like
> this breaks a system. See e.g.
> https://lore.kernel.org/all/Y5I2oQexHNdlIbsQ@shell.armlinux.org.uk

Geert, that's actually my thought as well, so I'm happy you wrote down
your opinion here!

By any chance, do you (or someone on this list) know of someone who has
that card and might be able to test it?

Helge


>> --- a/drivers/video/fbdev/q40fb.c
>> +++ b/drivers/video/fbdev/q40fb.c
>> @@ -101,6 +101,13 @@ static int q40fb_probe(struct platform_device *dev)
>>          info->par = NULL;
>>          info->screen_base = (char *) q40fb_fix.smem_start;
>>
>> +       if (!request_mem_region(q40fb_fix.smem_start, q40fb_fix.smem_len,
>> +                               "q40fb")) {
>> +               dev_err(&dev->dev, "cannot reserve video memory at 0x%lx\n",
>> +                       q40fb_fix.smem_start);
>> +               return -EBUSY;
>> +       }
>> +
>>          if (fb_alloc_cmap(&info->cmap, 256, 0) < 0) {
>>                  framebuffer_release(info);
>>                  return -ENOMEM;

^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2025-11-21 10:17 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
     [not found] <20251120180233.763975-1-hsukrut3@gmail.com>
2025-11-21 10:03 ` [RFC/RFT PATCH] fbdev: q40fb: request memory region Geert Uytterhoeven
2025-11-21 10:17   ` Helge Deller

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).