mirror of
https://github.com/AuxXxilium/linux_dsm_epyc7002.git
synced 2025-01-21 21:29:42 +07:00
52500de68f
That's purely for the uapi layer to implement the ALLOW_MODESET flag. Drivers should instead look at the state, e.g. through drm_atomic_crtc_needs_modeset(), which vmwgfx already does. Also remove the confusing comment, since checking allow_modeset is at best a micro optimization. v2: Rebase Reviewed-by: Deepak Rawat <drawat@vmware.com> Signed-off-by: Daniel Vetter <daniel.vetter@ffwll.ch> Cc: VMware Graphics <linux-graphics-maintainer@vmware.com> Cc: Thomas Hellstrom <thellstrom@vmware.com> Link: https://patchwork.freedesktop.org/patch/msgid/20190520223500.6032-1-daniel.vetter@ffwll.ch |
||
---|---|---|
.. | ||
device_include | ||
Kconfig | ||
Makefile | ||
ttm_lock.c | ||
ttm_lock.h | ||
ttm_object.c | ||
ttm_object.h | ||
vmwgfx_binding.c | ||
vmwgfx_binding.h | ||
vmwgfx_blit.c | ||
vmwgfx_bo.c | ||
vmwgfx_cmdbuf_res.c | ||
vmwgfx_cmdbuf.c | ||
vmwgfx_context.c | ||
vmwgfx_cotable.c | ||
vmwgfx_drv.c | ||
vmwgfx_drv.h | ||
vmwgfx_execbuf.c | ||
vmwgfx_fb.c | ||
vmwgfx_fence.c | ||
vmwgfx_fence.h | ||
vmwgfx_fifo.c | ||
vmwgfx_gmr.c | ||
vmwgfx_gmrid_manager.c | ||
vmwgfx_ioctl.c | ||
vmwgfx_irq.c | ||
vmwgfx_kms.c | ||
vmwgfx_kms.h | ||
vmwgfx_ldu.c | ||
vmwgfx_marker.c | ||
vmwgfx_mob.c | ||
vmwgfx_msg.c | ||
vmwgfx_msg.h | ||
vmwgfx_overlay.c | ||
vmwgfx_prime.c | ||
vmwgfx_reg.h | ||
vmwgfx_resource_priv.h | ||
vmwgfx_resource.c | ||
vmwgfx_scrn.c | ||
vmwgfx_shader.c | ||
vmwgfx_simple_resource.c | ||
vmwgfx_so.c | ||
vmwgfx_so.h | ||
vmwgfx_stdu.c | ||
vmwgfx_surface.c | ||
vmwgfx_ttm_buffer.c | ||
vmwgfx_ttm_glue.c | ||
vmwgfx_va.c | ||
vmwgfx_validation.c | ||
vmwgfx_validation.h |