From: Thomas Zimmermann <tzimmermann@suse.de> To: zackr@vmware.com, javierm@redhat.com, maarten.lankhorst@linux.intel.com, mripard@kernel.org, airlied@linux.ie, daniel@ffwll.ch, deller@gmx.de, hdegoede@redhat.com Cc: dri-devel@lists.freedesktop.org, linux-fbdev@vger.kernel.org, Thomas Zimmermann <tzimmermann@suse.de> Subject: [PATCH 0/5] sysfb: Fix memory-region management Date: Mon, 24 Jan 2022 13:36:54 +0100 [thread overview] Message-ID: <20220124123659.4692-1-tzimmermann@suse.de> (raw) Request framebuffer memory in simpledrm and simplefb. Do a hot-unplug operation when removing fbdev firmware drivers. After being unloaded by a hardware driver, simplefb leaves behind the firmware framebuffer's platform device. This prevents other drivers from acquiring the memory as reported at [1]. Patch 1 changes the removal code of remove_conflicting_framebuffers() to remove the underlying device and the rsp memory region. Patches 2 to 4 update sysfb and its drivers. The sysfb code does no longer mark the framebuffer memory with IORESOURCE_BUSY. Instead, the device drivers acquire the memory when they probe the device. Patch 5 adds a todo item to acquire memory regions in all DRM drivers. Tested with simpledrm and simplefb. [1] https://lore.kernel.org/dri-devel/20220117180359.18114-1-zack@kde.org/ Javier Martinez Canillas (1): drivers/firmware: Don't mark as busy the simple-framebuffer IO resource Thomas Zimmermann (4): fbdev: Hot-unplug firmware fb devices on forced removal drm/simpledrm: Request memory region in driver fbdev/simplefb: Request memory region in driver drm: Add TODO item for requesting memory regions Documentation/gpu/todo.rst | 15 ++++++++ drivers/firmware/sysfb_simplefb.c | 2 +- drivers/gpu/drm/tiny/simpledrm.c | 20 ++++++++--- drivers/video/fbdev/core/fbmem.c | 29 +++++++++++++-- drivers/video/fbdev/simplefb.c | 59 ++++++++++++++++++++++--------- include/linux/fb.h | 1 + 6 files changed, 100 insertions(+), 26 deletions(-) base-commit: 0bb81b5d6db5f689b67f9d8b35323235c45e890f -- 2.34.1
WARNING: multiple messages have this Message-ID (diff)
From: Thomas Zimmermann <tzimmermann@suse.de> To: zackr@vmware.com, javierm@redhat.com, maarten.lankhorst@linux.intel.com, mripard@kernel.org, airlied@linux.ie, daniel@ffwll.ch, deller@gmx.de, hdegoede@redhat.com Cc: linux-fbdev@vger.kernel.org, Thomas Zimmermann <tzimmermann@suse.de>, dri-devel@lists.freedesktop.org Subject: [PATCH 0/5] sysfb: Fix memory-region management Date: Mon, 24 Jan 2022 13:36:54 +0100 [thread overview] Message-ID: <20220124123659.4692-1-tzimmermann@suse.de> (raw) Request framebuffer memory in simpledrm and simplefb. Do a hot-unplug operation when removing fbdev firmware drivers. After being unloaded by a hardware driver, simplefb leaves behind the firmware framebuffer's platform device. This prevents other drivers from acquiring the memory as reported at [1]. Patch 1 changes the removal code of remove_conflicting_framebuffers() to remove the underlying device and the rsp memory region. Patches 2 to 4 update sysfb and its drivers. The sysfb code does no longer mark the framebuffer memory with IORESOURCE_BUSY. Instead, the device drivers acquire the memory when they probe the device. Patch 5 adds a todo item to acquire memory regions in all DRM drivers. Tested with simpledrm and simplefb. [1] https://lore.kernel.org/dri-devel/20220117180359.18114-1-zack@kde.org/ Javier Martinez Canillas (1): drivers/firmware: Don't mark as busy the simple-framebuffer IO resource Thomas Zimmermann (4): fbdev: Hot-unplug firmware fb devices on forced removal drm/simpledrm: Request memory region in driver fbdev/simplefb: Request memory region in driver drm: Add TODO item for requesting memory regions Documentation/gpu/todo.rst | 15 ++++++++ drivers/firmware/sysfb_simplefb.c | 2 +- drivers/gpu/drm/tiny/simpledrm.c | 20 ++++++++--- drivers/video/fbdev/core/fbmem.c | 29 +++++++++++++-- drivers/video/fbdev/simplefb.c | 59 ++++++++++++++++++++++--------- include/linux/fb.h | 1 + 6 files changed, 100 insertions(+), 26 deletions(-) base-commit: 0bb81b5d6db5f689b67f9d8b35323235c45e890f -- 2.34.1
next reply other threads:[~2022-01-24 12:37 UTC|newest] Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-01-24 12:36 Thomas Zimmermann [this message] 2022-01-24 12:36 ` [PATCH 0/5] sysfb: Fix memory-region management Thomas Zimmermann 2022-01-24 12:36 ` [PATCH 1/5] fbdev: Hot-unplug firmware fb devices on forced removal Thomas Zimmermann 2022-01-24 12:36 ` Thomas Zimmermann 2022-01-24 13:52 ` Javier Martinez Canillas 2022-01-24 13:52 ` Javier Martinez Canillas 2022-01-24 13:56 ` Javier Martinez Canillas 2022-01-24 13:56 ` Javier Martinez Canillas 2022-01-24 14:19 ` Thomas Zimmermann 2022-01-24 14:19 ` Thomas Zimmermann 2022-01-24 14:31 ` Javier Martinez Canillas 2022-01-24 14:31 ` Javier Martinez Canillas 2022-01-24 15:59 ` Zack Rusin 2022-01-24 15:59 ` Zack Rusin 2022-01-24 12:36 ` [PATCH 2/5] drivers/firmware: Don't mark as busy the simple-framebuffer IO resource Thomas Zimmermann 2022-01-24 12:36 ` Thomas Zimmermann 2022-01-24 15:59 ` Zack Rusin 2022-01-24 15:59 ` Zack Rusin 2022-01-24 12:36 ` [PATCH 3/5] drm/simpledrm: Request memory region in driver Thomas Zimmermann 2022-01-24 12:36 ` Thomas Zimmermann 2022-01-24 14:00 ` Javier Martinez Canillas 2022-01-24 14:00 ` Javier Martinez Canillas 2022-01-24 14:23 ` Jocelyn Falempe 2022-01-25 8:31 ` Thomas Zimmermann 2022-01-24 12:36 ` [PATCH 4/5] fbdev/simplefb: " Thomas Zimmermann 2022-01-24 12:36 ` Thomas Zimmermann 2022-01-24 14:24 ` Javier Martinez Canillas 2022-01-24 14:24 ` Javier Martinez Canillas 2022-01-24 12:36 ` [PATCH 5/5] drm: Add TODO item for requesting memory regions Thomas Zimmermann 2022-01-24 12:36 ` Thomas Zimmermann 2022-01-24 14:25 ` Javier Martinez Canillas 2022-01-24 14:25 ` Javier Martinez Canillas 2022-01-25 9:12 [PATCH 0/5] sysfb: Fix memory-region management Thomas Zimmermann 2022-01-25 9:12 ` Thomas Zimmermann 2022-01-25 9:13 ` Thomas Zimmermann 2022-01-25 9:13 ` Thomas Zimmermann 2022-01-25 15:34 ` Hans de Goede 2022-01-25 15:34 ` Hans de Goede
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=20220124123659.4692-1-tzimmermann@suse.de \ --to=tzimmermann@suse.de \ --cc=airlied@linux.ie \ --cc=daniel@ffwll.ch \ --cc=deller@gmx.de \ --cc=dri-devel@lists.freedesktop.org \ --cc=hdegoede@redhat.com \ --cc=javierm@redhat.com \ --cc=linux-fbdev@vger.kernel.org \ --cc=maarten.lankhorst@linux.intel.com \ --cc=mripard@kernel.org \ --cc=zackr@vmware.com \ /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: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.