Lines Matching +full:everything +full:- +full:else
10 Subsystem-wide refactorings
14 ---------------------------------------------
24 --------------------------------------------------
32 non-converted driver (again virtual HW drivers for KVM are still all
42 ---------------------------------------------------------
48 avoid confusion - the other helpers in that file are all deprecated legacy
54 ----------------------------------------------------
57 nonblocking commits, and every driver had to hand-roll them. This is fixed
67 -----------------------
72 a bit too severe. So there's some follow-up work to adjust the function
79 drivers explicitly so that the legacy-on-atomic functions can use them.
94 Get rid of dev->struct_mutex from GEM drivers
95 ---------------------------------------------
97 ``dev->struct_mutex`` is the Big DRM Lock from legacy days and infested
98 everything. Nowadays in modern drivers the only bit where it's mandatory is
107 For drivers that need ``struct_mutex`` it should be replaced with a driver-
111 performance-critical drivers it might also be better to go with a more
112 fine-grained per-buffer object and per-context lockings scheme. Currently only the
118 ----------------------------------------------------------------------------
124 those drivers back to using drm-formwatted specific log messages.
127 sure your work will be merged - not everyone agrees that the DRM dmesg macros
133 ----------------------------------------------------
137 drm_mode_config_helper_suspend/resume(). Also there's still open-coded version
143 -----------------------------------------------------------
147 - amdgpu which has special logic to decide whether to call
150 - armada which isn't atomic and doesn't call
153 - i915 which calls drm_fb_helper_initial_config() in a worker
161 ------------------------
163 A lot of drivers forward gem mmap calls to dma-buf mmap for imported buffers.
164 And also a lot of them forward dma-buf mmap to the gem mmap implementations.
170 ---------------------------
180 everything after it has done the write-protect/mkwrite trickery:
182 - In the drm_fbdev_fb_mmap helper, if we need defio, change the
183 default page prots to write-protected with something like this::
185 vma->vm_page_prot = pgprot_wrprotect(vma->vm_page_prot);
187 - Set the mkwrite and fsync callbacks with similar implementions to the core
192 - Track the dirty pages in a separate structure (bitfield with one bit per page
200 ---------------
210 ---------------------------
220 ---------------------------------------------------------
235 ---------------------------------
245 ----------------------------------------------------------------
248 is risky and has been known to cause div-by-zero bugs. Fortunately, drm core
254 https://lists.freedesktop.org/archives/dri-devel/2019-January/205186.html for
263 -----------------------------
273 -------------------
275 - drm_fb_helper_restore_fbdev_mode_unlocked() should call restore_fbdev_mode()
278 kms_fbcon_fbt@psr-suspend.
280 - The max connector argument for drm_fb_helper_init() and
283 - The helper doesn't keep an array of connectors anymore so these can be
291 ----------------------------
296 headers needed (and fixing up any missing pre-declarations in the headers).
303 ------------------------
326 make sure to not call such paths, or trylock everything. Really tricky.
331 it shows up. Everything else probably needs to be delayed to some worker or
332 something else which happens later on. Otherwise it just kills the box
335 * There's also proposal for a simplied DRM console instead of the full-blown
342 ----------------------------
346 - The drm_info_list ->show() function doesn't even bother to cast to the drm
349 - We probably want to have some support for debugfs files on crtc/connectors and
352 ->show() functions should obviously give you a pointer to the right object.
354 - The drm_info_list stuff is centered on drm_minor instead of drm_device. For
357 - The drm_driver->debugfs_init hooks we have is just an artifact of the old
362 this (together with the drm_minor->drm_device move) would allow us to remove
365 - Drop the return code and error checking from all debugfs functions. Greg KH is
371 ------------
375 - Make ->funcs and ->helper_private vtables optional. There's a bunch of empty
380 - Cleanup up the various ->destroy callbacks. A lot of them just wrapt the
389 ----------------------
393 Make KMS tests in i-g-t generic
394 -------------------------------
397 including tons of testcases for corner-cases in the modesetting API. It would
398 be awesome if those tests (at least the ones not relying on Intel-specific GEM
401 Basic work to run i-g-t tests on non-i915 is done, what's now missing is mass-
404 the non-i915 specific modeset tests.
407 ---------------------------------
416 ---------------------
432 ---------------------
442 ----
444 - Our early/late pm callbacks could be removed in favour of using
446 https://dri.freedesktop.org/docs/drm/driver-api/device_link.html
455 - [v6,8/8] drm/client: Hack: Add bootsplash example
458 - [RFC PATCH v2 00/13] Kernel based bootsplash