[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAE-0n52CHwYAEwAC0Hthgbamjj2x4K3B2w=kTRw_AFLzVgDF-Q@mail.gmail.com>
Date: Wed, 15 Dec 2021 11:10:34 -0800
From: Stephen Boyd <swboyd@...omium.org>
To: Rob Clark <robdclark@...il.com>, dri-devel@...ts.freedesktop.org
Cc: freedreno@...ts.freedesktop.org, linux-arm-msm@...r.kernel.org,
Rob Clark <robdclark@...omium.org>,
Sean Paul <sean@...rly.run>,
Abhinav Kumar <quic_abhinavk@...cinc.com>,
David Airlie <airlied@...ux.ie>,
Daniel Vetter <daniel@...ll.ch>,
Dmitry Baryshkov <dmitry.baryshkov@...aro.org>,
Bjorn Andersson <bjorn.andersson@...aro.org>,
Jonathan Marek <jonathan@...ek.ca>,
Jessica Zhang <quic_jesszhan@...cinc.com>,
Vladimir Lypak <vladimir.lypak@...il.com>,
Rajeev Nandan <quic_rajeevny@...cinc.com>,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH] drm/msm: Don't use autosuspend for display
Quoting Rob Clark (2021-12-15 09:59:02)
> From: Rob Clark <robdclark@...omium.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.
>
> Signed-off-by: Rob Clark <robdclark@...omium.org>
> ---
Reviewed-by: Stephen Boyd <swboyd@...omium.org>
Powered by blists - more mailing lists