From: Douglas Anderson <dianders@chromium.org>
To: dri-devel@lists.freedesktop.org, Maxime Ripard <mripard@kernel.org>
Cc: Linus Walleij <linus.walleij@linaro.org>,
Chris Morgan <macromorgan@hotmail.com>,
Neil Armstrong <neil.armstrong@linaro.org>,
Yuran Pereira <yuran.pereira@hotmail.com>,
Douglas Anderson <dianders@chromium.org>,
AngeloGioacchino Del Regno
<angelogioacchino.delregno@collabora.com>,
Daniel Vetter <daniel@ffwll.ch>, David Airlie <airlied@gmail.com>,
Jerry Han <hanxu5@huaqin.corp-partner.google.com>,
Jessica Zhang <quic_jesszhan@quicinc.com>,
Jonathan Corbet <corbet@lwn.net>,
Maarten Lankhorst <maarten.lankhorst@linux.intel.com>,
Matthias Brugger <matthias.bgg@gmail.com>,
Robert Chiras <robert.chiras@nxp.com>,
Stefan Mavrodiev <stefan@olimex.com>,
Thomas Zimmermann <tzimmermann@suse.de>,
linux-arm-kernel@lists.infradead.org, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-mediatek@lists.infradead.org
Subject: [PATCH v3 00/24] drm/panel: Remove most store/double-check of prepared/enabled state
Date: Tue, 4 Jun 2024 17:22:46 -0700 [thread overview]
Message-ID: <20240605002401.2848541-1-dianders@chromium.org> (raw)
As talked about in commit d2aacaf07395 ("drm/panel: Check for already
prepared/enabled in drm_panel"), we want to remove needless code from
panel drivers that was storing and double-checking the
prepared/enabled state. Even if someone was relying on the
double-check before, that double-check is now in the core and not
needed in individual drivers.
This series attempts to do just that. While the original grep, AKA:
git grep 'if.*>prepared' -- drivers/gpu/drm/panel
git grep 'if.*>enabled' -- drivers/gpu/drm/panel
...still produces a few hits after my series, they are _mostly_ all
gone. The ones that are left are less trivial to fix.
One of the main reasons that many panels probably needed to store and
double-check their prepared/enabled appears to have been to handle
shutdown and/or remove. Panels drivers often wanted to force the power
off for panels in these cases and this was a good reason for the
double-check.
In response to my V1 series [1] we had much discussion of what to
do. The conclusion was that as long as DRM modeset drivers properly
called drm_atomic_helper_shutdown() that we should be able to remove
the explicit shutdown/remove handling in the panel drivers. Most of
the patches to improve DRM modeset drivers [2] [3] [4] have now
landed.
In contrast to my V1 series, I broke the V2 series up a lot
more. Since a few of the panel drivers in V1 already landed, we had
fewer total drivers and so we could devote a patch to each panel.
Also, since we were now relying on DRM modeset drivers I felt like we
should split the patches for each panel into two: one that's
definitely safe and one that could be reverted if we found a
problematic DRM modeset driver that we couldn't fix.
Many of the patches in the V2 series [5] landed, so this V3 series is
the patches that are left plus one new bonus patch. At this point, we
may want to just land the patches that are left since it seems like
nobody is going to test/review them and they've all been Acked by
Linus and Maxime.
NOTE: this touches _a lot_ of drivers, is repetitive, and is not
really possible to generate automatically. That means it's entirely
possible that my eyes glazed over and I did something wrong. Please
double-check me and don't assume that I got everything perfect, though
I did my best. I have at least confirmed that "allmodconfig" for arm64
doesn't fall on its face with this series. I haven't done a ton of
other testing.
[1] https://lore.kernel.org/r/20230804140605.RFC.4.I930069a32baab6faf46d6b234f89613b5cec0f14@changeid
[2] https://lore.kernel.org/r/20230901234015.566018-1-dianders@chromium.org
[3] https://lore.kernel.org/r/20230901234202.566951-1-dianders@chromium.org
[4] https://lore.kernel.org/r/20230921192749.1542462-1-dianders@chromium.org
[5] https://lore.kernel.org/r/20240503213441.177109-1-dianders@chromium.org/
Changes in v3:
- drm/panel: Avoid warnings w/ panel-simple/panel-edp at shutdown
Changes in v2:
- Only handle 1 panel per patch.
- Split removal of prepared/enabled from handling of remove/shutdown.
Douglas Anderson (24):
drm/panel: boe-himax8279d: Stop tracking prepared/enabled
drm/panel: boe-himax8279d: Don't call unprepare+disable at
shutdown/remove
drm/panel: khadas-ts050: Stop tracking prepared/enabled
drm/panel: khadas-ts050: Don't call unprepare+disable at
shutdown/remove
drm/panel: olimex-lcd-olinuxino: Stop tracking prepared/enabled
drm/panel: olimex-lcd-olinuxino: Don't call unprepare+disable at
remove
drm/panel: osd-osd101t2587-53ts: Stop tracking prepared/enabled
drm/panel: osd-osd101t2587-53ts: Don't call unprepare+disable at
shutdown/remove
drm/panel: tdo-tl070wsh30: Stop tracking prepared
drm/panel: tdo-tl070wsh30: Don't call unprepare+disable at
shutdown/remove
drm/panel: jdi-lt070me05000: Stop tracking prepared/enabled
drm/panel: jdi-lt070me05000: Don't call disable at shutdown/remove
drm/panel: panasonic-vvx10f034n00: Stop tracking prepared/enabled
drm/panel: panasonic-vvx10f034n00: Don't call disable at
shutdown/remove
drm/panel: seiko-43wvf1g: Stop tracking prepared/enabled
drm/panel: seiko-43wvf1g: Don't call disable at shutdown/remove
drm/panel: sharp-lq101r1sx01: Stop tracking prepared/enabled
drm/panel: sharp-lq101r1sx01: Don't call disable at shutdown/remove
drm/panel: sharp-ls043t1le01: Stop tracking prepared
drm/panel: sharp-ls043t1le01: Don't call disable at shutdown/remove
drm/panel: raydium-rm67191: Stop tracking enabled
drm/panel: raydium-rm67191: Don't call unprepare+disable at shutdown
drm/panel: Update TODO list item for cleaning up prepared/enabled
tracking
drm/panel: Avoid warnings w/ panel-simple/panel-edp at shutdown
Documentation/gpu/todo.rst | 47 +++---
drivers/gpu/drm/drm_panel.c | 12 ++
drivers/gpu/drm/panel/panel-boe-himax8279d.c | 40 -----
.../gpu/drm/panel/panel-drm-shutdown-check.h | 151 ++++++++++++++++++
drivers/gpu/drm/panel/panel-edp.c | 19 +--
.../gpu/drm/panel/panel-jdi-lt070me05000.c | 35 ----
drivers/gpu/drm/panel/panel-khadas-ts050.c | 39 -----
.../drm/panel/panel-olimex-lcd-olinuxino.c | 44 -----
.../drm/panel/panel-osd-osd101t2587-53ts.c | 41 +----
.../drm/panel/panel-panasonic-vvx10f034n00.c | 47 +-----
drivers/gpu/drm/panel/panel-raydium-rm67191.c | 26 ---
drivers/gpu/drm/panel/panel-seiko-43wvf1g.c | 49 ------
.../gpu/drm/panel/panel-sharp-lq101r1sx01.c | 63 +-------
.../gpu/drm/panel/panel-sharp-ls043t1le01.c | 24 ---
drivers/gpu/drm/panel/panel-simple.c | 19 +--
drivers/gpu/drm/panel/panel-tdo-tl070wsh30.c | 23 ---
16 files changed, 199 insertions(+), 480 deletions(-)
create mode 100644 drivers/gpu/drm/panel/panel-drm-shutdown-check.h
--
2.45.1.288.g0e0cd299f1-goog
next reply other threads:[~2024-06-05 0:24 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-05 0:22 Douglas Anderson [this message]
2024-06-05 0:22 ` [PATCH v3 01/24] drm/panel: boe-himax8279d: Stop tracking prepared/enabled Douglas Anderson
2024-06-05 0:22 ` [PATCH v3 02/24] drm/panel: boe-himax8279d: Don't call unprepare+disable at shutdown/remove Douglas Anderson
2024-06-05 0:22 ` [PATCH v3 03/24] drm/panel: khadas-ts050: Stop tracking prepared/enabled Douglas Anderson
2024-06-05 0:22 ` [PATCH v3 04/24] drm/panel: khadas-ts050: Don't call unprepare+disable at shutdown/remove Douglas Anderson
2024-06-05 0:22 ` [PATCH v3 05/24] drm/panel: olimex-lcd-olinuxino: Stop tracking prepared/enabled Douglas Anderson
2024-06-05 0:22 ` [PATCH v3 06/24] drm/panel: olimex-lcd-olinuxino: Don't call unprepare+disable at remove Douglas Anderson
2024-06-05 0:22 ` [PATCH v3 07/24] drm/panel: osd-osd101t2587-53ts: Stop tracking prepared/enabled Douglas Anderson
2024-06-05 0:22 ` [PATCH v3 08/24] drm/panel: osd-osd101t2587-53ts: Don't call unprepare+disable at shutdown/remove Douglas Anderson
2024-06-05 0:22 ` [PATCH v3 09/24] drm/panel: tdo-tl070wsh30: Stop tracking prepared Douglas Anderson
2024-06-05 0:22 ` [PATCH v3 10/24] drm/panel: tdo-tl070wsh30: Don't call unprepare+disable at shutdown/remove Douglas Anderson
2024-06-05 0:22 ` [PATCH v3 11/24] drm/panel: jdi-lt070me05000: Stop tracking prepared/enabled Douglas Anderson
2024-06-05 0:22 ` [PATCH v3 12/24] drm/panel: jdi-lt070me05000: Don't call disable at shutdown/remove Douglas Anderson
2024-06-05 0:22 ` [PATCH v3 13/24] drm/panel: panasonic-vvx10f034n00: Stop tracking prepared/enabled Douglas Anderson
2024-06-05 0:23 ` [PATCH v3 14/24] drm/panel: panasonic-vvx10f034n00: Don't call disable at shutdown/remove Douglas Anderson
2024-06-05 0:23 ` [PATCH v3 15/24] drm/panel: seiko-43wvf1g: Stop tracking prepared/enabled Douglas Anderson
2024-06-05 0:23 ` [PATCH v3 16/24] drm/panel: seiko-43wvf1g: Don't call disable at shutdown/remove Douglas Anderson
2024-06-05 0:23 ` [PATCH v3 17/24] drm/panel: sharp-lq101r1sx01: Stop tracking prepared/enabled Douglas Anderson
2024-06-05 0:23 ` [PATCH v3 18/24] drm/panel: sharp-lq101r1sx01: Don't call disable at shutdown/remove Douglas Anderson
2024-06-05 0:23 ` [PATCH v3 19/24] drm/panel: sharp-ls043t1le01: Stop tracking prepared Douglas Anderson
2024-06-05 0:23 ` [PATCH v3 20/24] drm/panel: sharp-ls043t1le01: Don't call disable at shutdown/remove Douglas Anderson
2024-06-05 0:23 ` [PATCH v3 21/24] drm/panel: raydium-rm67191: Stop tracking enabled Douglas Anderson
2024-06-05 0:23 ` [PATCH v3 22/24] drm/panel: raydium-rm67191: Don't call unprepare+disable at shutdown Douglas Anderson
2024-06-05 0:23 ` [PATCH v3 23/24] drm/panel: Update TODO list item for cleaning up prepared/enabled tracking Douglas Anderson
2024-06-05 0:23 ` [PATCH v3 24/24] drm/panel: Avoid warnings w/ panel-simple/panel-edp at shutdown Douglas Anderson
2024-06-11 7:56 ` [PATCH v3 00/24] drm/panel: Remove most store/double-check of prepared/enabled state Neil Armstrong
2024-06-11 8:02 ` (subset) " Neil Armstrong
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=20240605002401.2848541-1-dianders@chromium.org \
--to=dianders@chromium.org \
--cc=airlied@gmail.com \
--cc=angelogioacchino.delregno@collabora.com \
--cc=corbet@lwn.net \
--cc=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=hanxu5@huaqin.corp-partner.google.com \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=maarten.lankhorst@linux.intel.com \
--cc=macromorgan@hotmail.com \
--cc=matthias.bgg@gmail.com \
--cc=mripard@kernel.org \
--cc=neil.armstrong@linaro.org \
--cc=quic_jesszhan@quicinc.com \
--cc=robert.chiras@nxp.com \
--cc=stefan@olimex.com \
--cc=tzimmermann@suse.de \
--cc=yuran.pereira@hotmail.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
all inboxes | Powered by JetHome®