Lines Matching +full:enable +full:- +full:cdm +full:- +full:check
11 ----------
26 Subsystem-wide refactorings
30 ---------------------------------------------
42 --------------------------------------------------
50 non-converted driver (again virtual HW drivers for KVM are still all
62 ---------------------------------------------------------
68 avoid confusion - the other helpers in that file are all deprecated legacy
76 ----------------------------------
81 - drm_plane_helper_funcs->atomic_check gets called for enabled or disabled
85 into the drm_plane_funcs->atomic_duplicate_state functions.
87 - Once that's done, helpers could stop calling ->atomic_check for disabled
90 - Then we could go through all the drivers and remove the more-or-less confused
91 checks for plane_state->fb and plane_state->crtc.
98 ----------------------------------------------------
101 nonblocking commits, and every driver had to hand-roll them. This is fixed
113 -----------------------
118 a bit too severe. So there's some follow-up work to adjust the function
125 drivers explicitly so that the legacy-on-atomic functions can use them.
142 Get rid of dev->struct_mutex from GEM drivers
143 ---------------------------------------------
145 ``dev->struct_mutex`` is the Big DRM Lock from legacy days and infested
155 For drivers that need ``struct_mutex`` it should be replaced with a driver-
159 performance-critical drivers it might also be better to go with a more
160 fine-grained per-buffer object and per-context lockings scheme. Currently only
168 ------------------------------------------------------------
174 those drivers back to using drm-formatted specific log messages.
177 sure your work will be merged - not everyone agrees that the DRM dmesg macros
185 ----------------------------------------------------
189 drm_mode_config_helper_suspend/resume(). Also there's still open-coded version
197 ------------------------------------------------
201 expects the framebuffer in system memory (or system-like memory).
208 -----------------------------------------------------------------
211 Various hold-ups:
213 - Need to switch over to the generic dirty tracking code using
216 - Need to switch to drm_fbdev_generic_setup(), otherwise a lot of the custom fb
219 - Many drivers wrap drm_gem_fb_create() only to check for valid formats. For
220 atomic drivers we could check for valid formats by calling
222 supports the format. For non-atomic that's not possible since like the format
225 - Many drivers subclass drm_framebuffer, we'd need a embedding compatible
234 ------------------------
236 A lot of drivers forward gem mmap calls to dma-buf mmap for imported buffers.
237 And also a lot of them forward dma-buf mmap to the gem mmap implementations.
245 ---------------------------
255 everything after it has done the write-protect/mkwrite trickery:
257 - In the drm_fbdev_fb_mmap helper, if we need defio, change the
258 default page prots to write-protected with something like this::
260 vma->vm_page_prot = pgprot_wrprotect(vma->vm_page_prot);
262 - Set the mkwrite and fsync callbacks with similar implementions to the core
267 - Track the dirty pages in a separate structure (bitfield with one bit per page
277 ---------------
289 ---------------------------
301 ---------------------------------------------------------
318 ---------------------------------
322 text these should even be called coherent DMA memory helpers (so maybe CDM, but
331 -----------------------------------
333 - For most connectors it's a no-op to call drm_connector_register/unregister
337 - For dp drivers it's a bit more a mess, since we need the connector to be
344 Remove load/unload callbacks from all non-DRIVER_LEGACY drivers
345 ---------------------------------------------------------------
351 - Rework drivers to no longer use the load/unload callbacks, directly coding the
354 - Once all non-DRIVER_LEGACY drivers are converted, disallow the load/unload
362 ---------------------------------------------------------------
376 --------------------------------------------
388 - audio (amdgpu, intel, gma500, radeon)
389 - brightness, contrast, etc (armada, nouveau) - overlay only (?)
390 - broadcast rgb (gma500, intel)
391 - colorkey (armada, nouveau, rcar) - overlay only (?)
392 - dither (amdgpu, nouveau, radeon) - varies across drivers
393 - underscan family (amdgpu, radeon, nouveau)
396 - colorspace (sti)
397 - tv format names, enhancements (gma500, intel)
398 - tv overscan, margins, etc. (gma500, intel)
399 - zorder (omapdrm) - same as zpos (?)
407 -------------------------------
414 additional states is rather non-intuitive and error prone.
422 .. code-block:: c
428 .. code-block:: c
437 Additionally many drivers currently access the object->state pointer
441 the current commit we're trying to process. Also non-blocking commits
443 the object->state pointers without holding the locks that protect them.
457 ------------------------
489 * There's also proposal for a simplied DRM console instead of the full-blown
498 ----------------------------
502 - The drm_info_list ->show() function doesn't even bother to cast to the drm
505 - We probably want to have some support for debugfs files on crtc/connectors and
508 ->show() functions should obviously give you a pointer to the right object.
510 - The drm_info_list stuff is centered on drm_minor instead of drm_device. For
513 - The drm_driver->debugfs_init hooks we have is just an artifact of the old
518 this (together with the drm_minor->drm_device move) would allow us to remove
521 - Drop the return code and error checking from all debugfs functions. Greg KH is
529 ------------
533 - Make ->funcs and ->helper_private vtables optional. There's a bunch of empty
535 that all the users in helpers and drivers do correctly check for a NULL
538 - Cleanup up the various ->destroy callbacks. A lot of them just wrapt the
545 Remove automatic page mapping from dma-buf importing
546 ----------------------------------------------------
548 When importing dma-bufs, the dma-buf and PRIME frameworks automatically map
556 buffer-sharing code. Fixing this is a bit more involved, since the import/export
569 Enable trinity for DRM
570 ----------------------
576 Make KMS tests in i-g-t generic
577 -------------------------------
580 including tons of testcases for corner-cases in the modesetting API. It would
581 be awesome if those tests (at least the ones not relying on Intel-specific GEM
584 Basic work to run i-g-t tests on non-i915 is done, what's now missing is mass-
587 the non-i915 specific modeset tests.
592 ---------------------------------
603 ---------------------
605 Backlight drivers have a triple enable/disable state, which is a bit overkill.
621 ---------------------
637 - [v6,8/8] drm/client: Hack: Add bootsplash example
640 - [RFC PATCH v2 00/13] Kernel based bootsplash
651 ----------------------------
654 become obsolete, but some still provides good(-enough) framebuffers. The
660 existing hardware. The new driver's call-back functions are filled from
663 More complex fbdev drivers can be refactored step-by-step into a DRM
672 - [1] https://gitlab.freedesktop.org/tzimmermann/linux/tree/fbconv
673 …- [2] https://gitlab.freedesktop.org/tzimmermann/linux/blob/fbconv/drivers/gpu/drm/drm_fbconv_help…