From: Chris Morgan <macroalpha82@gmail.com>
To: "Guido Günther" <guido.gunther@puri.sm>
Cc: Frank Oltmanns <frank@oltmanns.dev>,
Ondrej Jirman <megous@megous.com>,
Purism Kernel Team <kernel@puri.sm>,
Samuel Holland <samuel@sholland.org>,
Sam Ravnborg <sam@ravnborg.org>,
open list <linux-kernel@vger.kernel.org>,
"open list:DRM PANEL DRIVERS" <dri-devel@lists.freedesktop.org>,
Thierry Reding <thierry.reding@gmail.com>,
Ondrej Jirman <megi@xff.cz>,
phone-devel@vger.kernel.org
Subject: Re: [PATCH 1/1] drm/panel: st7703: Pick different reset sequence
Date: Wed, 18 Oct 2023 09:59:51 -0500 [thread overview]
Message-ID: <652ff2e8.050a0220.2e2de.4666@mx.google.com> (raw)
In-Reply-To: <ZSvf0HIA3GaZlbac@qwark.sigxcpu.org>
On Sun, Oct 15, 2023 at 02:49:20PM +0200, Guido Günther wrote:
> Hi,
> On Sat, Feb 11, 2023 at 06:17:48PM +0100, Frank Oltmanns wrote:
> > From: Ondrej Jirman <megi@xff.cz>
> >
> > Switching to a different reset sequence, enabling IOVCC before enabling
> > VCC.
> >
> > There also needs to be a delay after enabling the supplies and before
> > deasserting the reset. The datasheet specifies 1ms after the supplies
> > reach the required voltage. Use 10-20ms to also give the power supplies
> > some time to reach the required voltage, too.
> >
> > This fixes intermittent panel initialization failures and screen
> > corruption during resume from sleep on panel xingbangda,xbd599 (e.g.
> > used in PinePhone).
>
> Thanks, applied to drm-misc-next.
> Cheers,
> -- Guido
Thank you. Probably too late, but this fixes problems I have with a
different ST7703 based panel.
Tested-by: Chris Morgan <macromorgan@hotmail.com>
>
> >
> > Signed-off-by: Ondrej Jirman <megi@xff.cz>
> > Signed-off-by: Frank Oltmanns <frank@oltmanns.dev>
> > Reported-by: Samuel Holland <samuel@sholland.org>
> > ---
> > drivers/gpu/drm/panel/panel-sitronix-st7703.c | 25 ++++++++++---------
> > 1 file changed, 13 insertions(+), 12 deletions(-)
> >
> > diff --git a/drivers/gpu/drm/panel/panel-sitronix-st7703.c b/drivers/gpu/drm/panel/panel-sitronix-st7703.c
> > index 6747ca237ced..45695aa51f62 100644
> > --- a/drivers/gpu/drm/panel/panel-sitronix-st7703.c
> > +++ b/drivers/gpu/drm/panel/panel-sitronix-st7703.c
> > @@ -411,29 +411,30 @@ static int st7703_prepare(struct drm_panel *panel)
> > return 0;
> >
> > dev_dbg(ctx->dev, "Resetting the panel\n");
> > - ret = regulator_enable(ctx->vcc);
> > + gpiod_set_value_cansleep(ctx->reset_gpio, 1);
> > +
> > + ret = regulator_enable(ctx->iovcc);
> > if (ret < 0) {
> > - dev_err(ctx->dev, "Failed to enable vcc supply: %d\n", ret);
> > + dev_err(ctx->dev, "Failed to enable iovcc supply: %d\n", ret);
> > return ret;
> > }
> > - ret = regulator_enable(ctx->iovcc);
> > +
> > + ret = regulator_enable(ctx->vcc);
> > if (ret < 0) {
> > - dev_err(ctx->dev, "Failed to enable iovcc supply: %d\n", ret);
> > - goto disable_vcc;
> > + dev_err(ctx->dev, "Failed to enable vcc supply: %d\n", ret);
> > + regulator_disable(ctx->iovcc);
> > + return ret;
> > }
> >
> > - gpiod_set_value_cansleep(ctx->reset_gpio, 1);
> > - usleep_range(20, 40);
> > + /* Give power supplies time to stabilize before deasserting reset. */
> > + usleep_range(10000, 20000);
> > +
> > gpiod_set_value_cansleep(ctx->reset_gpio, 0);
> > - msleep(20);
> > + usleep_range(15000, 20000);
> >
> > ctx->prepared = true;
> >
> > return 0;
> > -
> > -disable_vcc:
> > - regulator_disable(ctx->vcc);
> > - return ret;
> > }
> >
> > static const u32 mantix_bus_formats[] = {
> > --
> > 2.39.1
> >
next prev parent reply other threads:[~2023-10-18 14:59 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-11 17:17 [PATCH 0/1] drm/panel: st7703: Fix initialization failures on Xingbangda XBD599 Frank Oltmanns
2023-02-11 17:17 ` [PATCH 1/1] drm/panel: st7703: Pick different reset sequence Frank Oltmanns
2023-10-15 10:59 ` Guido Günther
2023-10-15 12:49 ` Guido Günther
2023-10-18 14:59 ` Chris Morgan [this message]
2023-02-12 11:21 ` [PATCH 0/1] drm/panel: st7703: Fix initialization failures on Xingbangda XBD599 Guido Günther
2023-02-12 12:09 ` Frank Oltmanns
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=652ff2e8.050a0220.2e2de.4666@mx.google.com \
--to=macroalpha82@gmail.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=frank@oltmanns.dev \
--cc=guido.gunther@puri.sm \
--cc=kernel@puri.sm \
--cc=linux-kernel@vger.kernel.org \
--cc=megi@xff.cz \
--cc=megous@megous.com \
--cc=phone-devel@vger.kernel.org \
--cc=sam@ravnborg.org \
--cc=samuel@sholland.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