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 5/5] drm: Add TODO item for requesting memory regions Date: Mon, 24 Jan 2022 13:36:59 +0100 [thread overview] Message-ID: <20220124123659.4692-6-tzimmermann@suse.de> (raw) In-Reply-To: <20220124123659.4692-1-tzimmermann@suse.de> Add a TODO item about requesting memory regions for each driver. The current DRM drivers don't do this consistently. Signed-off-by: Thomas Zimmermann <tzimmermann@suse.de> --- Documentation/gpu/todo.rst | 15 +++++++++++++++ 1 file changed, 15 insertions(+) diff --git a/Documentation/gpu/todo.rst b/Documentation/gpu/todo.rst index da138dd39883..1b2372ef4131 100644 --- a/Documentation/gpu/todo.rst +++ b/Documentation/gpu/todo.rst @@ -467,6 +467,21 @@ Contact: Thomas Zimmermann <tzimmermann@suse.de> Level: Intermediate +Request memory regions in all drivers +------------------------------------- + +Go through all drivers and add code to request the memory regions that the +driver uses. This requires adding calls to request_mem_region(), +pci_request_region() or similar functions. Use helpers for managed cleanup +where possible. + +Drivers are pretty bad at doing this and there used to be conflicts among +DRM and fbdev drivers. Still, it's the correct thing to do. + +Contact: Thomas Zimmermann <tzimmermann@suse.de> + +Level: Starter + Core refactorings ================= -- 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 5/5] drm: Add TODO item for requesting memory regions Date: Mon, 24 Jan 2022 13:36:59 +0100 [thread overview] Message-ID: <20220124123659.4692-6-tzimmermann@suse.de> (raw) In-Reply-To: <20220124123659.4692-1-tzimmermann@suse.de> Add a TODO item about requesting memory regions for each driver. The current DRM drivers don't do this consistently. Signed-off-by: Thomas Zimmermann <tzimmermann@suse.de> --- Documentation/gpu/todo.rst | 15 +++++++++++++++ 1 file changed, 15 insertions(+) diff --git a/Documentation/gpu/todo.rst b/Documentation/gpu/todo.rst index da138dd39883..1b2372ef4131 100644 --- a/Documentation/gpu/todo.rst +++ b/Documentation/gpu/todo.rst @@ -467,6 +467,21 @@ Contact: Thomas Zimmermann <tzimmermann@suse.de> Level: Intermediate +Request memory regions in all drivers +------------------------------------- + +Go through all drivers and add code to request the memory regions that the +driver uses. This requires adding calls to request_mem_region(), +pci_request_region() or similar functions. Use helpers for managed cleanup +where possible. + +Drivers are pretty bad at doing this and there used to be conflicts among +DRM and fbdev drivers. Still, it's the correct thing to do. + +Contact: Thomas Zimmermann <tzimmermann@suse.de> + +Level: Starter + Core refactorings ================= -- 2.34.1
next prev parent reply other threads:[~2022-01-24 12:37 UTC|newest] Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-01-24 12:36 [PATCH 0/5] sysfb: Fix memory-region management Thomas Zimmermann 2022-01-24 12:36 ` 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 ` Thomas Zimmermann [this message] 2022-01-24 12:36 ` [PATCH 5/5] drm: Add TODO item for requesting memory regions 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 ` [PATCH 5/5] drm: Add TODO item for requesting memory regions Thomas Zimmermann 2022-01-25 9:12 ` Thomas Zimmermann
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-6-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.