diff options
| author | Pekka Paalanen <pekka.paalanen@collabora.com> | 2025-04-14 08:56:56 +0000 |
|---|---|---|
| committer | Simon Ser <contact@emersion.fr> | 2025-04-30 23:35:00 +0200 |
| commit | 9b33df36b45136d301241920d13a0a3ecc77b8f9 (patch) | |
| tree | d40e907e3afd65f0dbc22f2e7e2097f133df7bce | |
| parent | b389df0f6b5a2e0655e9f101af97d75e35fb874c (diff) | |
drm/doc: document front-buffer rendering
Explain how to perform front-buffer rendering.
v2: apply Pekka's rewrite
Signed-off-by: Pekka Paalanen <pekka.paalanen@collabora.com>
Signed-off-by: Simon Ser <contact@emersion.fr>
Reviewed-by: Simon Ser <contact@emersion.fr>
Link: https://lore.kernel.org/r/20250414085652.43904-1-contact@emersion.fr
| -rw-r--r-- | drivers/gpu/drm/drm_blend.c | 6 |
1 files changed, 6 insertions, 0 deletions
diff --git a/drivers/gpu/drm/drm_blend.c b/drivers/gpu/drm/drm_blend.c index 6e74de833466..6852d73c931c 100644 --- a/drivers/gpu/drm/drm_blend.c +++ b/drivers/gpu/drm/drm_blend.c @@ -75,6 +75,12 @@ * the currently visible vertical area of the &drm_crtc. * FB_ID: * Mode object ID of the &drm_framebuffer this plane should scan out. + * + * When a KMS client is performing front-buffer rendering, it should set + * FB_ID to the same front-buffer FB on each atomic commit. This implies + * to the driver that it needs to re-read the same FB again. Otherwise + * drivers which do not employ continuously repeated scanout cycles might + * not update the screen. * CRTC_ID: * Mode object ID of the &drm_crtc this plane should be connected to. * |