All of lore.kernel.org
 help / color / mirror / Atom feed
From: Weiji Wang <nebclllo0444@gmail.com>
To: Doug Anderson <dianders@chromium.org>
Cc: dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] drm/panel-edp: Add BOE NE140QDM-NX2
Date: Sun, 26 Jul 2026 04:58:22 +0800	[thread overview]
Message-ID: <9f2d7be0-e93e-480e-bcb1-6bc494f42640@gmail.com> (raw)
In-Reply-To: <CAD=FV=VVjZRst=SCY0SCuwynzcG4vpjJ3ZAiRR=q+2ry-rt9CQ@mail.gmail.com>

Hi,


On 7/26/26 00:29, Doug Anderson wrote:
> Right that using the "enable" delay is more conservative, but it does
> sound as if "prepare_to_enable" is more correct in this case if you
> are provided "(T4+T5+T6+T8)-min".
>
> I re-looked at the one panel using "delay_200_500_p2e80"
> (NV116WHM-T01), since I still have access to that datasheet. There, I
> see:
>
> T4+T5+T6+T8 > 80ms
> 0ms < T7 <= 50ms
> 50ms < T8
>
> In other words, T7-max is 50 and T8-min is 50.
>
> Based on that, I believe it would be more correct for this panel to
> use "delay_200_500_e50_p2e80". I'll try to send a patch for that,
> which would get rid of the need for "delay_200_500_p2e80".
>
> Does that match your panel, too?
>
> -Doug


Yes, the constraints of T4+T5+T6+T8, T7 and T8 is exactly same as mine.
However, my copy of datasheet did not mention min/max value of T6, and it
feels like assuming T6-min=0 if setting 'enable' to 50ms, or
max(T7-max, T8-min). Is that proper?

Sorry to inconvenience you due to my inexperience in LCD panels.


  reply	other threads:[~2026-07-25 20:58 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-24 11:55 [PATCH] drm/panel-edp: Add BOE NE140QDM-NX2 Weiji Wang
2026-07-24 15:24 ` Doug Anderson
2026-07-25 12:11   ` Weiji Wang
2026-07-25 16:29     ` Doug Anderson
2026-07-25 20:58       ` Weiji Wang [this message]
2026-07-25 23:48         ` 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=9f2d7be0-e93e-480e-bcb1-6bc494f42640@gmail.com \
    --to=nebclllo0444@gmail.com \
    --cc=dianders@chromium.org \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=linux-kernel@vger.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.