mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Doug Anderson <dianders@chromium.org>
To: dioyc_zhang <dioyc_zhang@compal.corp-partner.google.com>
Cc: neil.armstrong@linaro.org, airlied@gmail.com, daniel@ffwll.ch,
	 sam@ravnborg.org, dri-devel@lists.freedesktop.org,
	 linux-kernel@vger.kernel.org
Subject: Re: [PATCH v1] drm/panel: panel-edp: Adjust T8 timing for AUO B116XAK01.6 and B140XTK02.4
Date: Fri, 17 Jul 2026 10:13:23 -0700	[thread overview]
Message-ID: <CAD=FV=VJ+xycNUZCuoipVOueu5R=WhCSjQLqWDxa9r4T-a9p4g@mail.gmail.com> (raw)
In-Reply-To: <20260717025946.2751081-1-dioyc_zhang@compal.corp-partner.google.com>

Hi,

On Thu, Jul 16, 2026 at 8:00 PM dioyc_zhang
<dioyc_zhang@compal.corp-partner.google.com> wrote:
>
> Screen garbage or flickering can be observed during mode changes (such
> as VT switches) on systems using the AUO B116XAK01.6 and B140XTK02.4 panels.
> This occurs because the backlight is enabled before the video signal
> stabilizes. Waveform measurements show that the panel signal takes around
> 140ms to stabilize after a mode change, meaning the previous 50ms T8
> timing was insufficient.
>
> To resolve this issue, adjust the eDP panel delay entry from
> delay_200_500_e50 to delay_200_500_e200 (increasing T8 from 50ms to 200ms).
> This matches the updated panel specifications from AUO, which now formally
> define T8 as 200ms to mask any display abnormalities during mode changes.

Great description / justification. Increasing delays always stinks,
but sometimes is unavoidable.


> Signed-off-by: dioyc_zhang <dioyc_zhang@compal.corp-partner.google.com>

Any chance you could improve the "Name" part of your Signed-off-by
(and patch authorship, too)? Is "dioyc_zhang" really a name that you
usually use to identify yourself? It seems like it was just git
automatically assigning something since you typed in an email address
but not a name...

-Doug

      reply	other threads:[~2026-07-17 17:13 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-17  2:59 dioyc_zhang
2026-07-17 17:13 ` Doug Anderson [this message]

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='CAD=FV=VJ+xycNUZCuoipVOueu5R=WhCSjQLqWDxa9r4T-a9p4g@mail.gmail.com' \
    --to=dianders@chromium.org \
    --cc=airlied@gmail.com \
    --cc=daniel@ffwll.ch \
    --cc=dioyc_zhang@compal.corp-partner.google.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=neil.armstrong@linaro.org \
    --cc=sam@ravnborg.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