• Nicholas Kazlauskas's avatar
    drm/amd/display: Fix update type mismatches in atomic check · 6836d239
    Nicholas Kazlauskas authored
    [Why]
    Whenever a stream or plane is added or removed from the context the
    pointer will change from old to new. We set lock and validation
    needed in these cases. But not all of these cases match update_type
    from dm_determine_update_type_for_commit - an example being overlay
    plane updates.
    
    There are warnings for a few of these cases that should be fixed.
    
    [How]
    We can closer align to DC (and lock_and_validation_needed) by
    comparing stream and plane pointers.
    
    Since the old stream/old plane state is never freed until sometime
    after the commit tail work finishes we are guaranteed to never get
    back the same block of memory when we remove and create a stream or
    plane state in the same commit.
    Signed-off-by: default avatarNicholas Kazlauskas <nicholas.kazlauskas@amd.com>
    Reviewed-by: default avatarLeo Li <sunpeng.li@amd.com>
    Signed-off-by: default avatarAlex Deucher <alexander.deucher@amd.com>
    6836d239
amdgpu_dm.c 171 KB