diff options
| author | Lyude Paul <lyude@redhat.com> | 2026-07-20 17:36:17 -0400 |
|---|---|---|
| committer | Lyude Paul <lyude@redhat.com> | 2026-07-27 12:40:16 -0400 |
| commit | 8d092b0523cac5999db9e25e95c08f90560e2806 (patch) | |
| tree | af5924868ba6ed7a3f6bb4795f526601a994295e /tools/perf/scripts/python | |
| parent | a7e8cf887ada1173641042b67ee4bc571417957e (diff) | |
drm/nouveau/kms/nv50-: Introduce nv50_wndw_default_state()
While we don't currently read-in the hardware state of planes, now that
we're about to start exposing blend properties for all planes that can
support alpha channels: We need to make sure that the initial atomic state
for a wndw always starts off with a supported value in pixel_blend_mode.
The easiest way to do this is to introduce a nv50_wndw_default_state()
function, and use it in nv50_display_read_hw_state() - and use that
function to enforce a valid value for pixel_blend_mode during driver
startup.
Signed-off-by: Lyude Paul <lyude@redhat.com>
Reviewed-by: Dave Airlie <airlied@redhat.com>
Fixes: 860e748bddcc ("drm: ensure blend mode supported if pixel format with alpha exposed")
Link: https://patch.msgid.link/20260720215058.398210-3-lyude@redhat.com
Diffstat (limited to 'tools/perf/scripts/python')
0 files changed, 0 insertions, 0 deletions
