Lines Matching full:there

18 implementation (there's lots of outdated locking leftovers in various
31 There is a conversion guide for atomic and all you need is a GPU for a
58 now, but there's still a pile of existing drivers that easily could be
72 a bit too severe. So there's some follow-up work to adjust the function
86   implement the userspace ABI. And then there's the optional hooks for the
89   ``_helper_funcs`` since they are not part of the core ABI. There's a
104 and there's a ``gem_free_object_unlocked`` callback for any drivers which are
137 drm_mode_config_helper_suspend/resume(). Also there's still open-coded version
165 There's drm_gem_prime_mmap() for this now, but still needs to be rolled out.
267 in the future. If there is any debug code using drm_display_mode.hsync, convert
276   not the _force variant so it can bail out if there is a master. But first
314 * There's a massive confusion of different panic handlers. DRM fbdev emulation
320   returns true if there's a panic going on for real, and fix up all the
335 * There's also proposal for a simplied DRM console instead of the full-blown
344 There's a bunch of issues with it:
350   maybe other kms objects directly in core. There's even drm_print support in
351   the funcs for these objects to dump kms state, so it's all there. And then the
375 - Make ->funcs and ->helper_private vtables optional. There's a bunch of empty
382   end, for which we could add drm_*_cleanup_kfree(). And then there's the (for
434 AMD DC is the display driver for AMD devices starting with Vega. There has been
435 a bunch of progress cleaning it up but there's still plenty of work to be done.
451 There is support in place now for writing internal DRM clients making it