[PATCH] drm/msm: Don't use autosuspend for display

Rob Clark robdclark at gmail.com
Wed Dec 15 20:13:52 UTC 2021


On Wed, Dec 15, 2021 at 11:10 AM Stephen Boyd <swboyd at chromium.org> wrote:
>
> Quoting Rob Clark (2021-12-15 09:59:02)
> > From: Rob Clark <robdclark at chromium.org>
> >
> > No functional change, as we only actually enable autosuspend for the GPU
> > device.  But lets not encourage thinking that autosuspend is a good idea
> > for anything display related.
>
> I'd prefer to see a small blurb about why it's not a good idea to use
> autosuspend for display things. Then this commit can be dug out of the
> history and someone new can quickly understand the reasoning behind it.
> Just saying it's not a good idea doesn't really help.

The issue is that we have multiple different devices at play, and
potentially specific requirements about power sequencing when lighting
up or shutting down the display.. autosuspend would just turn that
into a giant race condition.  I'll squash something about this into
the commit msg

BR,
-R

> >
> > Signed-off-by: Rob Clark <robdclark at chromium.org>
> > ---
>
> Reviewed-by: Stephen Boyd <swboyd at chromium.org>


More information about the dri-devel mailing list