From: Neil Armstrong <neil.armstrong@linaro.org>
To: david@ixit.cz, Sumit Semwal <sumit.semwal@linaro.org>,
Casey Connolly <casey.connolly@linaro.org>,
Jessica Zhang <jesszhan0024@gmail.com>,
Maarten Lankhorst <maarten.lankhorst@linux.intel.com>,
Maxime Ripard <mripard@kernel.org>,
Thomas Zimmermann <tzimmermann@suse.de>,
David Airlie <airlied@gmail.com>, Simona Vetter <simona@ffwll.ch>,
Dmitry Baryshkov <lumag@kernel.org>,
Marijn Suijten <marijn.suijten@somainline.org>,
Vinod Koul <vkoul@kernel.org>
Cc: dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org,
phone-devel@vger.kernel.org
Subject: Re: [PATCH 1/2] drm/panel: lg-sw43408: do not assert reset across unprepare
Date: Mon, 10 Aug 2026 11:52:21 +0200 [thread overview]
Message-ID: <66864dd5-0ab4-48d9-9404-70f839db320a@linaro.org> (raw)
In-Reply-To: <20260809-fix-blueline-panel-v1-1-e7f3a6beb1fa@ixit.cz>
On 8/9/26 02:04, David Heidelberg via B4 Relay wrote:
> From: David Heidelberg <david@ixit.cz>
>
> Asserting the reset GPIO in unprepare() and leaving it asserted puts
> the DDIC into a state it never recovers from: after the following
> prepare() the panel answers all DCS commands, reports display-on with
> clean self-diagnostics, and its configuration registers read back
> identical to a working panel, but it never lights up again.
>
> On the Pixel 3, vddi is shared with the touchscreen controller and
> remains powered while the panel is off, so with this driver the DDIC
> sits in reset with its logic rail up for the whole blank period - a
> state the vendor stack never creates: the vendor firmware only toggles
> reset as part of a full power-on sequence, and the vendor OS never
> power-cycles the panel at all (LP mode is used instead).
>
> Leave reset alone in unprepare(); prepare() performs the regular reset
> sequence anyway.
>
> Without this, the Pixel 3 display never comes back after the first
> blank/unblank cycle.
>
> Since there isn't any other panel or device using this DDIC, this
> approach seems resoanble to address the issue.
>
> Fixes: 069a6c0e94f9 ("drm: panel: Add LG sw43408 panel driver")
> Signed-off-by: David Heidelberg <david@ixit.cz>
> ---
> drivers/gpu/drm/panel/panel-lg-sw43408.c | 10 ++++++++--
> 1 file changed, 8 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/gpu/drm/panel/panel-lg-sw43408.c b/drivers/gpu/drm/panel/panel-lg-sw43408.c
> index 293826c5006b9..0bf8e08f10b9c 100644
> --- a/drivers/gpu/drm/panel/panel-lg-sw43408.c
> +++ b/drivers/gpu/drm/panel/panel-lg-sw43408.c
> @@ -50,18 +50,24 @@ static int sw43408_unprepare(struct drm_panel *panel)
> int ret;
>
> mipi_dsi_dcs_set_display_off_multi(&ctx);
>
> mipi_dsi_dcs_enter_sleep_mode_multi(&ctx);
>
> mipi_dsi_msleep(&ctx, 100);
>
> - gpiod_set_value(sw43408->reset_gpio, 1);
> -
> + /*
> + * Keep reset deasserted: vddi may stay powered (it is shared with
> + * the touchscreen on Pixel 3) and holding the DDIC in reset while
> + * its logic rail is up puts it into a state that no init sequence
> + * recovers from - the panel keeps answering DCS commands and
> + * reports display-on, but never lights up again. The vendor stack
> + * only ever toggles reset as part of a powered-up init sequence.
> + */
> ret = regulator_bulk_disable(ARRAY_SIZE(sw43408_supplies), sw43408->supplies);
Asserting the reset then shutting down half the rails up may force the DDIC to enter
a special low power mode with a bad sequence and then would not come out.
But anyway reset has a sense only if all rails are up and we want to get a proper
initial state, if somehow we want to handle those special low power mode to speed
up suspend and resume we will need to understand how to get in and get out.
Reviewed-by: Neil Armstrong <neil.armstrong@linaro.org>
Thanks,
Neil
>
> return ret ? : ctx.accum_err;
> }
>
> static int sw43408_program(struct drm_panel *panel)
> {
> struct sw43408_panel *sw43408 = to_panel_info(panel);
>
next prev parent reply other threads:[~2026-08-10 9:52 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-09 0:04 [PATCH 0/2] Pixel 3 display fixes David Heidelberg via B4 Relay
2026-08-09 0:04 ` [PATCH 1/2] drm/panel: lg-sw43408: do not assert reset across unprepare David Heidelberg via B4 Relay
2026-08-10 9:52 ` Neil Armstrong [this message]
2026-08-09 0:04 ` [PATCH 2/2] drm/panel: lg-sw43408: use the full DCS brightness range David Heidelberg via B4 Relay
2026-08-10 9:47 ` Neil Armstrong
2026-08-09 0:15 ` [PATCH 0/2] Pixel 3 display fixes David Heidelberg
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=66864dd5-0ab4-48d9-9404-70f839db320a@linaro.org \
--to=neil.armstrong@linaro.org \
--cc=airlied@gmail.com \
--cc=casey.connolly@linaro.org \
--cc=david@ixit.cz \
--cc=dri-devel@lists.freedesktop.org \
--cc=jesszhan0024@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lumag@kernel.org \
--cc=maarten.lankhorst@linux.intel.com \
--cc=marijn.suijten@somainline.org \
--cc=mripard@kernel.org \
--cc=phone-devel@vger.kernel.org \
--cc=simona@ffwll.ch \
--cc=sumit.semwal@linaro.org \
--cc=tzimmermann@suse.de \
--cc=vkoul@kernel.org \
/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®