From: Sam Ravnborg <sam@ravnborg.org>
To: Douglas Anderson <dianders@chromium.org>
Cc: Thierry Reding <thierry.reding@gmail.com>,
robdclark@chromium.org, David Airlie <airlied@linux.ie>,
dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org,
Rob Herring <robh+dt@kernel.org>
Subject: Re: [PATCH v4 2/5] drm: panel: simple: Defer unprepare delay till next prepare to shorten it
Date: Sun, 29 Nov 2020 23:11:32 +0100 [thread overview]
Message-ID: <20201129221132.GI1162850@ravnborg.org> (raw)
In-Reply-To: <20201109170018.v4.2.I06a95d83e7fa1bd919c8edd63dacacb5436e495a@changeid>
Hi Douglas,
On Mon, Nov 09, 2020 at 05:00:56PM -0800, Douglas Anderson wrote:
> It is believed that all of the current users of the "unprepare" delay
> don't actually need to wait the amount of time specified directly in
> the unprepare phase. The purpose of the delay that's specified is to
> allow the panel to fully power off so that we don't try to power it
> back on before it's managed to full power down.
>
> Let's use this observation to avoid the fixed delay that we currently
> have. Instead of delaying, we'll note the current time when the
> unprepare happens. If someone then tries to prepare the panel later
> and not enough time has passed, we'll do the delay before starting the
> prepare phase.
>
> Signed-off-by: Douglas Anderson <dianders@chromium.org>
Applied to drm-misc-next.
Sam
next prev parent reply other threads:[~2020-11-29 22:12 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-10 1:00 [PATCH v4 1/5] drm: panel: simple: Fixup the struct panel_desc kernel doc Douglas Anderson
2020-11-10 1:00 ` [PATCH v4 2/5] drm: panel: simple: Defer unprepare delay till next prepare to shorten it Douglas Anderson
2020-11-29 22:11 ` Sam Ravnborg [this message]
2020-11-10 1:00 ` [PATCH v4 3/5] drm: panel: simple: Allow specifying the delay from prepare to enable Douglas Anderson
2020-11-29 22:11 ` Sam Ravnborg
2020-11-10 1:00 ` [PATCH v4 4/5] drm: panel: simple: Add BOE NV110WTM-N61 Douglas Anderson
2020-11-10 2:32 ` Doug Anderson
2020-11-29 22:12 ` Sam Ravnborg
2020-11-10 1:00 ` [PATCH v4 5/5] dt-bindings: dt-bindings: display: " Douglas Anderson
2020-11-23 17:24 ` [PATCH v4 1/5] drm: panel: simple: Fixup the struct panel_desc kernel doc Doug Anderson
2020-11-29 22:10 ` Sam Ravnborg
2020-12-01 21:00 ` Doug Anderson
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20201129221132.GI1162850@ravnborg.org \
--to=sam@ravnborg.org \
--cc=airlied@linux.ie \
--cc=dianders@chromium.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robdclark@chromium.org \
--cc=robh+dt@kernel.org \
--cc=thierry.reding@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).