mirror of https://lore.kernel.org/lkml/
 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: Sat, 25 Jul 2026 20:11:09 +0800	[thread overview]
Message-ID: <051ca77a-4308-4084-b9c1-5bbe4ea39f9c@gmail.com> (raw)
In-Reply-To: <CAD=FV=UmtBnHuOc6oFeKAPrZSeAcx1EcjMdfm+FDV7uZgxa=zw@mail.gmail.com>

Hi there,


On 7/24/26 23:24, Doug Anderson wrote:
> This is not sorted properly. 0x0af2 does not belong between 0x0b1e and 0x0b34.
>
> ...I could fix that when applying, but I also have a question: do you
> have access to the datasheet of this panel, or are you just guessing
> the right timing by looking at the nearby panels? I assume you have
> this panel yourself for testing and confirm it seems to work OK.


The datasheet is taken from Panelook. I have to mention that enable delay
is not directly available in the datasheet, only (T4+T5+T6+T8)-min is
given.

I'm not really familiar with eDP panels, so I'm not sure if using
'prepare_to_enable' instead of 'enable' will break anything on devices
without HPD enabled. However, appearently (T4+T5+T6+T8)-min is greater
than (T6-min + max(T7-max, T8-min)), so I believe that setting 'enable'
to (T4+T5+T6+T8)-min is conservative enough.

Is it proper to switch to 'delay_200_500_p2e80' (use 'prepare_to_enable'
instead)? If so, I would change it and also the panel entry sorting.


  reply	other threads:[~2026-07-25 12:11 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-24 11:55 Weiji Wang
2026-07-24 15:24 ` Doug Anderson
2026-07-25 12:11   ` Weiji Wang [this message]
2026-07-25 16:29     ` Doug Anderson
2026-07-25 20:58       ` Weiji Wang
2026-07-25 23:48         ` Doug Anderson
2026-07-27 19:55           ` Weiji Wang

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=051ca77a-4308-4084-b9c1-5bbe4ea39f9c@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 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®