Lines Matching full:drivers

5 Drivers must initialize the mode setting core by calling
69 drivers. Besides that they make it unnecessarily more complicated for userspace
74 drivers, and in many cases not powerful enough to express the real restrictions.
140 the CRTC and any encoders. Often for drivers with bridges there's no code left
141 at the encoder level. Atomic drivers can leave out all the encoder callbacks to
159 .. kernel-doc:: drivers/gpu/drm/drm_mode_config.c
191 .. kernel-doc:: drivers/gpu/drm/drm_mode_object.c
246   simplifying conversion of existing drivers. But auditing drivers for
262   objects with userspace-visible and settable state. For internal state drivers
276 exposed to drivers, instead the right locks should be automatically acquired by
288 .. kernel-doc:: drivers/gpu/drm/drm_atomic.c
297 .. kernel-doc:: drivers/gpu/drm/drm_atomic.c
303 .. kernel-doc:: drivers/gpu/drm/drm_atomic_uapi.c
306 .. kernel-doc:: drivers/gpu/drm/drm_atomic_uapi.c
312 .. kernel-doc:: drivers/gpu/drm/drm_crtc.c
321 .. kernel-doc:: drivers/gpu/drm/drm_crtc.c
327 .. kernel-doc:: drivers/gpu/drm/drm_color_mgmt.c
336 .. kernel-doc:: drivers/gpu/drm/drm_framebuffer.c
345 .. kernel-doc:: drivers/gpu/drm/drm_framebuffer.c
360 .. kernel-doc:: drivers/gpu/drm/drm_fourcc.c
368 .. kernel-doc:: drivers/gpu/drm/drm_dumb_buffers.c
374 .. kernel-doc:: drivers/gpu/drm/drm_plane.c
383 .. kernel-doc:: drivers/gpu/drm/drm_plane.c
389 .. kernel-doc:: drivers/gpu/drm/drm_blend.c
395 .. kernel-doc:: drivers/gpu/drm/drm_damage_helper.c
404 .. kernel-doc:: drivers/gpu/drm/drm_panic.c
413 .. kernel-doc:: drivers/gpu/drm/drm_panic.c
422 .. kernel-doc:: drivers/gpu/drm/drm_modes.c
428 .. kernel-doc:: drivers/gpu/drm/drm_connector.c
437 .. kernel-doc:: drivers/gpu/drm/drm_connector.c
443 .. kernel-doc:: drivers/gpu/drm/drm_writeback.c
449 .. kernel-doc:: drivers/gpu/drm/drm_writeback.c
455 .. kernel-doc:: drivers/gpu/drm/drm_encoder.c
464 .. kernel-doc:: drivers/gpu/drm/drm_encoder.c
470 .. kernel-doc:: drivers/gpu/drm/drm_modeset_lock.c
476 .. kernel-doc:: drivers/gpu/drm/drm_modeset_lock.c
488 KMS drivers might need to add extra properties to support new features. Each
504   associated state structure. That includes anything drivers might want
524 .. kernel-doc:: drivers/gpu/drm/drm_property.c
530 .. kernel-doc:: drivers/gpu/drm/drm_property.c
538 .. kernel-doc:: drivers/gpu/drm/drm_connector.c
544 .. kernel-doc:: drivers/gpu/drm/drm_connector.c
550 .. kernel-doc:: drivers/gpu/drm/drm_connector.c
556 .. kernel-doc:: drivers/gpu/drm/drm_crtc.c
562 .. kernel-doc:: drivers/gpu/drm/drm_plane.c
570 .. kernel-doc:: drivers/gpu/drm/drm_blend.c
578 .. kernel-doc:: drivers/gpu/drm/drm_plane.c
584 .. kernel-doc:: drivers/gpu/drm/drm_color_mgmt.c
590 .. kernel-doc:: drivers/gpu/drm/drm_connector.c
596 .. kernel-doc:: drivers/gpu/drm/drm_atomic_uapi.c
603 .. kernel-doc:: drivers/gpu/drm/drm_connector.c
609 .. kernel-doc:: drivers/gpu/drm/drm_plane.c
616 modules/drivers. Because this table is very unwieldy, do not add any new
626 .. kernel-doc:: drivers/gpu/drm/drm_vblank.c
635 .. kernel-doc:: drivers/gpu/drm/drm_vblank.c
641 .. kernel-doc:: drivers/gpu/drm/drm_vblank_work.c
650 .. kernel-doc:: drivers/gpu/drm/drm_vblank_work.c