drm, kdb, kms: Add an enter argument to mode_set_base_atomic() API
Some devices such as the radeon chips receive information from user space which needs to be saved when executing an atomic mode set operation, else the user space would have to be queried again for the information. This patch extends the mode_set_base_atomic() call to pass an argument to indicate if this is an entry or an exit from an atomic kernel mode set change. Individual drm drivers can properly save and restore state accordingly. Signed-off-by: Jason Wessel <jason.wessel@windriver.com> CC: Jesse Barnes <jbarnes@virtuousgeek.org> CC: David Airlie <airlied@linux.ie> CC: dri-devel@lists.freedesktop.org Signed-off-by: Dave Airlie <airlied@redhat.com>
This commit is contained in:
committed by
Dave Airlie
parent
be64c2bb47
commit
413d45d362
@@ -263,7 +263,8 @@ int drm_fb_helper_debug_enter(struct fb_info *info)
|
||||
funcs->mode_set_base_atomic(mode_set->crtc,
|
||||
mode_set->fb,
|
||||
mode_set->x,
|
||||
mode_set->y);
|
||||
mode_set->y,
|
||||
1);
|
||||
|
||||
}
|
||||
}
|
||||
@@ -309,7 +310,7 @@ int drm_fb_helper_debug_leave(struct fb_info *info)
|
||||
}
|
||||
|
||||
funcs->mode_set_base_atomic(mode_set->crtc, fb, crtc->x,
|
||||
crtc->y);
|
||||
crtc->y, 0);
|
||||
}
|
||||
|
||||
return 0;
|
||||
|
Reference in New Issue
Block a user