drm/doc: Document drm_helper_resume_force_mode
Stumbled over while reviewing all occurences in the DRM doc talking about suspend/resume. Reviewed-by: Alex Deucher <alexander.deucher@amd.com> Signed-off-by: Daniel Vetter <daniel.vetter@ffwll.ch>
This commit is contained in:
@ -1151,8 +1151,11 @@ int max_width, max_height;</synopsis>
|
|||||||
This operation is called with the mode config lock held.
|
This operation is called with the mode config lock held.
|
||||||
</para>
|
</para>
|
||||||
<note><para>
|
<note><para>
|
||||||
FIXME: How should set_config interact with DPMS? If the CRTC is
|
Note that the drm core has no notion of restoring the mode setting
|
||||||
suspended, should it be resumed?
|
state after resume, since all resume handling is in the full
|
||||||
|
responsibility of the driver. The common mode setting helper library
|
||||||
|
though provides a helper which can be used for this:
|
||||||
|
<function>drm_helper_resume_force_mode</function>.
|
||||||
</para></note>
|
</para></note>
|
||||||
</sect4>
|
</sect4>
|
||||||
<sect4>
|
<sect4>
|
||||||
|
@ -943,6 +943,15 @@ int drm_helper_mode_fill_fb_struct(struct drm_framebuffer *fb,
|
|||||||
}
|
}
|
||||||
EXPORT_SYMBOL(drm_helper_mode_fill_fb_struct);
|
EXPORT_SYMBOL(drm_helper_mode_fill_fb_struct);
|
||||||
|
|
||||||
|
/**
|
||||||
|
* drm_helper_resume_force_mode - force-restore mode setting configuration
|
||||||
|
* @dev: drm_device which should be restored
|
||||||
|
*
|
||||||
|
* Drivers which use the mode setting helpers can use this function to
|
||||||
|
* force-restore the mode setting configuration e.g. on resume or when something
|
||||||
|
* else might have trampled over the hw state (like some overzealous old BIOSen
|
||||||
|
* tended to do).
|
||||||
|
*/
|
||||||
int drm_helper_resume_force_mode(struct drm_device *dev)
|
int drm_helper_resume_force_mode(struct drm_device *dev)
|
||||||
{
|
{
|
||||||
struct drm_crtc *crtc;
|
struct drm_crtc *crtc;
|
||||||
|
Reference in New Issue
Block a user